-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
yarn v4 #1618
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tony
force-pushed
the
berry
branch
2 times, most recently
from
October 9, 2021 14:45
f3ce1e0
to
d2002be
Compare
tony
force-pushed
the
master
branch
2 times, most recently
from
December 21, 2021 01:41
2c20ddc
to
7c81777
Compare
tony
force-pushed
the
master
branch
5 times, most recently
from
July 20, 2022 11:56
48bf407
to
33c1e70
Compare
tony
force-pushed
the
master
branch
2 times, most recently
from
July 31, 2022 20:57
5777f9b
to
95a7f17
Compare
tony
force-pushed
the
berry
branch
2 times, most recently
from
September 5, 2022 15:10
26c7502
to
110ff46
Compare
tony
added a commit
that referenced
this pull request
Sep 5, 2022
Even though we may not ultimately use it: - It seems to be a project in the midst of a philosophical problem. - Why give it another name, unless losing track of where it came from - It seems to decouple architecture (yay) but I'm concerned with not adopting an incremental approach to make yarn v1 better. Why not decouple yarn v1. Slowly improve that one. - 99% of the options berry has make no sense to me. Overwhelmed by choices. Every configuration option is listed, with no help given to making the bread and butter scenarios prominent. My guess is the settings are to fill niche caches and specialized project layouts. What would help: Show practical examples of what type of projects these configuration settings are for. If it's not fitting the scenario - don't even mention it. - Not a fan of how YN0000 shows everywhere. yarnpkg/berry#2517 since Feb 25, 2021 This may have a practical use case for it, e.g. when certain operations run in parallel. But this shows even when an operation isn't parallel. Eek. - The underlying feeling I have is berry is optimizing for the maintainers, and the user is an afterthought. This is direct opposite to what yarn is about. Yarn is about hiding complexity, user convenience and happiness, and performance. As odd as that may sound - it's important to strike a balance of a good product and a good developer experience. - I still see a lot of potential and benefit in berry As an open source maintainer The architecture is there, it just needs to get polished to show what matters to the user, to convey its value.
tony
added a commit
that referenced
this pull request
Sep 5, 2022
Even though we may not ultimately use it: - It seems to be a project in the midst of a philosophical problem. - Why give it another name, unless losing track of where it came from - It seems to decouple architecture (yay) but I'm concerned with not adopting an incremental approach to make yarn v1 better. Why not decouple yarn v1. Slowly improve that one. - 99% of the options berry has make no sense to me. Overwhelmed by choices. Every configuration option is listed, with no help given to making the bread and butter scenarios prominent. My guess is the settings are to fill niche caches and specialized project layouts. What would help: Show practical examples of what type of projects these configuration settings are for. If it's not fitting the scenario - don't even mention it. - Not a fan of how YN0000 shows everywhere. yarnpkg/berry#2517 since Feb 25, 2021 This may have a practical use case for it, e.g. when certain operations run in parallel. But this shows even when an operation isn't parallel. Eek. - The underlying feeling I have is berry is optimizing for the maintainers, and the user is an afterthought. This is direct opposite to what yarn is about. Yarn is about hiding complexity, user convenience and happiness, and performance. As odd as that may sound - it's important to strike a balance of a good product and a good developer experience. - I still see a lot of potential and benefit in berry As an open source maintainer The architecture is there, it just needs to get polished to show what matters to the user, to convey its value.
tony
added a commit
that referenced
this pull request
Sep 5, 2022
Even though we may not ultimately use it: - It seems to be a project in the midst of a philosophical problem. - Why give it another name, unless losing track of where it came from - It seems to decouple architecture (yay) but I'm concerned with not adopting an incremental approach to make yarn v1 better. Why not decouple yarn v1. Slowly improve that one. - 99% of the options berry has make no sense to me. Overwhelmed by choices. Every configuration option is listed, with no help given to making the bread and butter scenarios prominent. My guess is the settings are to fill niché cases and specialized project layouts. What would help: Show practical examples of what type of projects these configuration settings are for. If it's not fitting the scenario - don't even mention it. - Not a fan of how YN0000 shows everywhere. yarnpkg/berry#2517 since Feb 25, 2021 This may have a practical use case for it, e.g. when certain operations run in parallel. But this shows even when an operation isn't parallel. Eek. - The underlying feeling I have is berry is optimizing for the maintainers, and the user is an afterthought. This is direct opposite to what yarn is about. Yarn is about hiding complexity, user convenience and happiness, and performance. As odd as that may sound - it's important to strike a balance of a good product and a good developer experience. - I still see a lot of potential and benefit in berry As an open source maintainer The architecture is there, it just needs to get polished to show what matters to the user, to convey its value.
tony
force-pushed
the
master
branch
3 times, most recently
from
August 5, 2023 17:36
9bfb7c3
to
abf46cd
Compare
tony
force-pushed
the
berry
branch
2 times, most recently
from
November 14, 2023 23:03
16c7bbc
to
842f519
Compare
tony
force-pushed
the
berry
branch
6 times, most recently
from
November 19, 2023 17:18
47dad0d
to
f452039
Compare
yarn set version 4.0.2 See also: - https://yarnpkg.com/getting-started/migration - https://yarnpkg.com/blog/release/4.0#installing-yarn Squashed: yarn set version berry (3.0 -> 3.1+) to fix ERR_STREAM_PREMATURE_CLOSE In our case this bumped to 3.2.3 See also: yarnpkg/berry#3597
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See also: