221–230 of 520 posts
Earlier quoted context omitted.
How about the idea that Node has been a hack from day one?
Node was a very interesting thing back when it started. It was a hack, but a nice kind of hack. You could write some efficient servers with it. But then the community that formed around it, with it the project went berserk.
Earlier quoted context omitted.
The term "nazi" is not simply mildly offensive, there are likely legal implications if you want to serve users in Germany.
I doubt they did it out of a desire to better serve users in Germany.
Because probably every country has some words they don't like.
Earlier quoted context omitted.
Because each thing has a constant price in learning effort that is familiarizing yourself with its idiosyncrasies, which you have to pay even if you're experienced in the domain. When tools constantly get replaced instead of improved, you keep paying that price all the time.
It’s a drop-in replacement CLI tool. Let’s not be dramatic.
Earlier quoted context omitted.
I have recently taken over an Angular project (with a C# backend, thankfully) at my job. It took two hours to get it to even compile correctly because some dependencies were apparently outdated in package.json and it just ran on the other dev's machine by accident. I don't understand why I need over 100 dependencies for a simple Angular Single Page App that pulls JSON from the backend and pushes JSON back. Meanwhile,…
Three developers on my team spent the last 4 years pushing for angular. Four years ago, I was 50/50 on it vs react, so whatever, but if my team's really for it, let's do it. Fast forward to angular 2, and we're down to two developers who are still for it. Fast forward to today, I'm down to one angular dev who's still for it, and two of the original three have left for react jobs. Meanwhile, I'm left with a bunch of a…
The caret syntax for auto-upgrading to the next minor version is the open door to a world of bullshit.
Earlier quoted context omitted.
They're referencing the Bible: https://www.biblegateway.com/passage/?search=Ecclesiastes+3&...
I’m pretty sure they’re referencing the Byrds song and not the Bible directly: https://m.youtube.com/watch?feature=youtu.be&v=pKP4cfU28vM
Btw. for those who don't know: Yarn (which is an alternative to npm) uses a global cache [1] on your machine which speeds things up, but probably also protects you from immediate problems in cases like the one currently on progress (because you would probably have a local copy of e.g. require-from-string available). [1] https://yarnpkg.com/lang/en/docs/cli/cache/
Already counting down the days before yarn is considered old and broken and people are recommending switching to the next hot package manager/bundler...
Do you also insist that Chrome and Firefox shouldn't exist because IE does the job adequately?
Yikes, what is it about node/npm/javascript that makes it feel like a house of cards?
I think the (short) answer is "node, npm, and javascript".
The longer answer has something to do with the automatic installation of dependencies, and the common use of shell scripts downloaded directly off the internet and executed using the developer's or sysadmin's user account.
I used to use CPAN all the time. CPAN would check dependencies for you, but if you didn't have them already you'd get a warning and you'd have to install them yourself. It forced you to be aware of what you're installing, and it applied some pressure on CPAN authors to not go too crazy with dependencies (since they were just as annoyed by the installation process as everyone else.)
These days I use NuGet a lot. It does the dependency installation for you, but it asks for permission first. The dialogs could be better about letting you learn about the dependencies before saying they're ok. (In general, NuGet's dialogs could be a lot better about package details.)
Earlier quoted context omitted.
Already counting down the days before yarn is considered old and broken and people are recommending switching to the next hot package manager/bundler...
yarn is one of those things coming out of the JS world that is actually really well made. yarn, typescript, react; say what you want about js fatigue, these are rock-solid, well-tested projects that are really good at what they do. A major reason for the high toolchurn in that ecosystem is how many of those tools are not designed from the ground up, don't quite solve the things they ought to, or solve them in really…
I wish webpack was on that list.