Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Everything You Wanted to Know About Yarn Package Manager

atatus.com

Post reply on HN
Print view View original

21–28 of 28 posts

Re: Everything You Wanted to Know About Yarn Package Manager

#21

Post by throwanem »

sotojuan wrote: post #10
agnivade wrote: post #4

Why can't all of this be patched in npm ? Why do we have to create a new tool every time ? It makes no sense and honestly makes me want to tear my hairs.

I don't get why people say this. You're acting like the npm team is desperate for contributions and fixes and the Yarn people are like "No! We'll make our OWN tool!". It's the literal opposite. npm hasn't been open to contributions or fixes for years.

Really? https://github.com/npm/npm/pulls?q=is%3Apr+is%3Aclosed would seem to suggest otherwise. Should I be looking elsewhere? Is there something I'm not seeing here?

Re: Everything You Wanted to Know About Yarn Package Manager

#22

Post by sotojuan »

wnevets wrote: post #14
sotojuan wrote: post #12

Earlier quoted context omitted.

What do you expect when Yarn has been out for less than a couple of weeks and this person isn't involved with the project in any way?

to not write an article proclaiming its everything?

Such is the problem with the majority of programming blog posts.

Re: Everything You Wanted to Know About Yarn Package Manager

#24

Post by agnivade »

throwanem wrote: post #20
Touche wrote: post #7

Earlier quoted context omitted.

A lot of people say this and I'll repeat the answer: go look at npm's source code and tell me you'd like to "patch in" a large change such as the one Yarn takes on. No seriously, go look at their source code. In particular go look at the caching code, one of the big things that Yarn fixes. You think their time would have been better spent hacking on that?

Maybe? It'll be interesting to see how many bugs turn up in Yarn that've already been fixed in npm. Until we can perform that kind of comparison, I'm not sure it is possible to know whether building a new package manager from scratch was more worthwhile than improving the one that everyone already uses.

Exactly my point. I am not totally against reinventing the wheel. Sometimes its fun and sometimes interesting results do come out of it. I am especially looking at the servo project.

But considering the amount of collaboration effort it took to build this (fb said they collaborated with multiple companies in different timezones), wouldn't it be better to spend a little more time understanding npm's codebase and get it patched ? Maybe I'm wrong, but yea just a thought.

Re: Everything You Wanted to Know About Yarn Package Manager

#25

Post by doublerebel »

throwanem wrote: post #21
sotojuan wrote: post #10

Earlier quoted context omitted.

I don't get why people say this. You're acting like the npm team is desperate for contributions and fixes and the Yarn people are like "No! We'll make our OWN tool!". It's the literal opposite. npm hasn't been open to contributions or fixes for years.

Really? https://github.com/npm/npm/pulls?q=is%3Apr+is%3Aclosed would seem to suggest otherwise. Should I be looking elsewhere? Is there something I'm not seeing here?

I've contributed multiple issues and PRs which have been completely ignored. It seems from the outside that their focus on monetizing causes their API to be purposefully opaque and subject to change. It's been disappointing and certainly turns me off from ever purchasing private repo hosting from npm itself.

For reference:

https://github.com/npm/npm/issues/12085

https://github.com/npm/npm/issues/8319

https://github.com/npm/couch-login/pull/13

I have a deep understanding of how it works now, and therefore more to contribute, but what's the point? I just keep running my own npm(s) instead and contribute to packages that appreciate it.

Re: Everything You Wanted to Know About Yarn Package Manager

#26

Post by throwanem »

doublerebel wrote: post #25
throwanem wrote: post #21

Earlier quoted context omitted.

Really? https://github.com/npm/npm/pulls?q=is%3Apr+is%3Aclosed would seem to suggest otherwise. Should I be looking elsewhere? Is there something I'm not seeing here?

I've contributed multiple issues and PRs which have been completely ignored. It seems from the outside that their focus on monetizing causes their API to be purposefully opaque and subject to change. It's been disappointing and certainly turns me off from ever purchasing private repo hosting from npm itself. For reference: https://github.com/npm/npm/issues/12085 https://github.com/npm/npm/issues/8319 https://github.c…

A strong statement, to be sure, for which one would hope to see equally strong evidence. But two out of those three issues have unfulfilled requests for followup. I'm not sure quite what you mean them to show.

Re: Everything You Wanted to Know About Yarn Package Manager

#27

Post by Touche »

agnivade wrote: post #24
throwanem wrote: post #20

Earlier quoted context omitted.

Maybe? It'll be interesting to see how many bugs turn up in Yarn that've already been fixed in npm. Until we can perform that kind of comparison, I'm not sure it is possible to know whether building a new package manager from scratch was more worthwhile than improving the one that everyone already uses.

Exactly my point. I am not totally against reinventing the wheel. Sometimes its fun and sometimes interesting results do come out of it. I am especially looking at the servo project. But considering the amount of collaboration effort it took to build this (fb said they collaborated with multiple companies in different timezones), wouldn't it be better to spend a little more time understanding npm's codebase and get i…

> But considering the amount of collaboration effort it took to build this (fb said they collaborated with multiple companies in different timezones), wouldn't it be better to spend a little more time understanding npm's codebase and get it patched ?

Better for you? You know that open source work is free labor, right? Why should they prefer to spend weeks trying to understand undocumented, opaque and "clever" code (much of which has never been refactored) when they can start from scratch with a codebase of their own design?

What I'm asking is, what is the value to them? Or to you (assuming you ever do open source)? Unless you are getting paid for your OS work, you're under no obligation to do things any way other than what works for you.

Re: Everything You Wanted to Know About Yarn Package Manager

#28

Post by gotofritz »

sotojuan wrote: post #12
gotofritz wrote: post #2

- promises "everything you wanted to know about yarn" - has barely any content

What do you expect when Yarn has been out for less than a couple of weeks and this person isn't involved with the project in any way?

I expect the title to be something along the lines of "First thoughts on Yarn"
Post reply on HN