Live data from Hacker News

Things I Regret About Node.js [video]

youtube.com

31–40 of 502 posts

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

#31
post #25

The first post in this issue has a summary of some performance problems with node.js: https://github.com/ry/deno/issues/162 Though, it's posted in a confrontational way so the conversation deteriorates.

No, that thread is everything that is wrong with open source.

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

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

#34

"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…

i'm not sure what you mean by "outlandish statements and attitudes".

when he said "this project is done now" my takeaway was that he didn't anticipate the popularity of node. and "so wrong" was him acknowledging that he was very obviously mistaken.

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

#35

The first post in this issue has a summary of some performance problems with node.js: https://github.com/ry/deno/issues/162 Though, it's posted in a confrontational way so the conversation deteriorates.

OP was incredibly immature and the resulting discussion was worthless.

> I do not need any help from you thanks. This is aimed towards Ryan

Yikes.

Also, calling everything a horrible miscarriage is not a discussion.

Pointing out the problems with something is easy. Anyone can do it. What's hard is evaluating problems in relation to the trade-offs that were made. Only amateurs think everything is "horrible" as if there are never trade-offs.

I agree with my sibling: it's only good example of worthless Github issue "conversation".

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

#36

The first post in this issue has a summary of some performance problems with node.js: https://github.com/ry/deno/issues/162 Though, it's posted in a confrontational way so the conversation deteriorates.

OP was incredibly immature and the resulting discussion was worthless. > I do not need any help from you thanks. This is aimed towards Ryan Yikes. Also, calling everything a horrible miscarriage is not a discussion. Pointing out the problems with something is easy. Anyone can do it. What's hard is evaluating problems in relation to the trade-offs that were made. Only amateurs think everything is "horrible" as if ther…

OK, that's fair. I'll edit my comment.

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

#38
post #29
post #11

Earlier quoted context omitted.

thanks for answering. but thanks to the parent comment i learned about a new (albiet widely recognized) author. thats useful because we all come to hn to learn things. i suspect most downvoters probably dont even understand the reference and just see a joke qua joke. boo.

I don't know how entertaining they are for adults, but I enjoyed reading Boy and Going Solo when I was younger.

I encountered them probably in my 40s, but did find them enjoyable.

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

#39

Interesting that he had promises in node that early. Maybe if he kept them, the community wouldn’t had standardized on two space indents Edit: so two space indents weren’t a consequence of “callback hell” ?

i could see nested callbacks favoring two spaces, but overall it's not a style unique to javascript.

for example, a lot of ruby i've seen (admittedly it's been a while) used two spaces, and i don't recall it being any more prone to deeply nested code than other languages.

that said js code tends to be rendered in a variety of other places like browser dev tools, which may influence this as well.

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

#40
post #25

Earlier quoted context omitted.

No, that thread is everything that is wrong with open source.

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.
Post reply on HN