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

Things I Regret About Node.js [video]

youtube.com

Post reply on HN
Print view View original

41–50 of 502 posts

Re: Things I Regret About Node.js [video]

#41

Post by freditup »

dylrich wrote: post #26
sametmax wrote: post #24

Earlier quoted context omitted.

My head can't wrap itself around: import { test } from " https://unpkg.com/deno_testing@0.0.5/testing.ts" There is so many issues with that I don't even no where to begin.

His arguments for it seemed reasonable - would love to hear your criticisms

Not OP, but a couple guesses off the top of my head:

* It becomes a more painful process to upgrade dependencies (have to find/replace across your codebase).

* Many versions of the same library get pulled in. If you depend on package@1.5.3 and a dependency of yours depends on package@1.5.4, that's twice the dependency size as compared to both just using 1.5.4. This matters more in the case of web app bundle size though than running local programs.

Re: Things I Regret About Node.js [video]

#42

Post by sonofaplum »

VeejayRampay wrote: post #28

"And then there were people adding modules. I thought to myself, this projet is done now. So wrong." Seriously why are we as a community still entertaining those outlandish statements and attitudes? If you heard that sentence as a non-tech person, you'd swear modules is a computer virus or something, that it's so inherently bad that it's not even worth discussing. Props to Ryan for his amazing work, but come on let's…

Thats not what he meant. He was not saying "People are adding modules, modules are bad, this project is ruined, [modules are] so wrong." He was saying, "People are creating modules, people are building on top of my work, this project is COMPLETE. [I was] so wrong."

Re: Things I Regret About Node.js [video]

#43

Post by davidy123 »

Touche wrote: post #40
davidy123 wrote: post #31

Earlier quoted context omitted.

I don't think your comment is clear at all. Do you mean the "community" or (arbitrary) toolsets of open source?

The community. Specifically that someone thought it was appropriate to post an issue shitting on someone's old project in that person's new project's issue tracker.

The original post could have been constructive. It's at least a good possibility that a new thing can be developed based on criticism of an old thing, and some of the author's points were just building on what Dahl said, so it could have been a useful discussion. I don't agree with another comment in this thread that it's easy to (succinctly and with depth) point out what's wrong. The person who initially responded to the issue could have included these possibilities rather than playing full-on cop. These systems are still largely organic. But the original poster's replies are hostile and in light of the "radio silence" request mentioned later in the thread, it wasn't ultimately a good post.

Re: Things I Regret About Node.js [video]

#44

Post by Demiurge »

Touche wrote: post #40
davidy123 wrote: post #31

Earlier quoted context omitted.

I don't think your comment is clear at all. Do you mean the "community" or (arbitrary) toolsets of open source?

The community. Specifically that someone thought it was appropriate to post an issue shitting on someone's old project in that person's new project's issue tracker.

It's also kind of pathological when someone focuses on just one technical aspect of software, like performance, or security, completely unable to reason within a large context of people doing things for other people.

Re: Things I Regret About Node.js [video]

#45

Post by t-sauer »

freditup wrote: post #41
dylrich wrote: post #26

Earlier quoted context omitted.

His arguments for it seemed reasonable - would love to hear your criticisms

Not OP, but a couple guesses off the top of my head: * It becomes a more painful process to upgrade dependencies (have to find/replace across your codebase). * Many versions of the same library get pulled in. If you depend on package@1.5.3 and a dependency of yours depends on package@1.5.4, that's twice the dependency size as compared to both just using 1.5.4. This matters more in the case of web app bundle size thou…

You could have an entry file for your dependencies (let's say dependencies.ts) and reexport everything from there. When you have to update, you only have to upgrade it in the entry file and you can avoid multiple versions.

Re: Things I Regret About Node.js [video]

#46

Post by rb808 »

Interesting that he's unsure about Go. Would be nice to hear about why.

One huge strength about Node (&Deno) is having the same language and tools on the front end and back end. Its a huge benefit to have a team on one language, even if it might not be the optimal choice. I'm not sure if that is the problem he had with Go though.

Re: Things I Regret About Node.js [video]

#48

Post by ahmetkun »

sebringj wrote: post #30

Why I admire Ryan is "I shouldn't just complain without giving a solution..." and he gave a solution, more than once. I have done this on a no-one-cares scale but it really is better to do yourself when you can. Also, Ryan has some sharp sarcastic wit which is pretty fun to watch on this talk.

You can see the same sarcastic wit in this talk too: https://www.youtube.com/watch?v=jo_B4LTHi3I

It's still my favorite tech talk, very fun to watch.

Post reply on HN