Modern Node.js Patterns
kashw1n.com
Modern Node.js Patterns
1–10 of 448 posts
Re: Modern Node.js Patterns
#2About time! The whole dragging the feet on ESM adoption is insane. The npm are still stuck on commonjs is quite a lot. In some way glad jsr came along.
Re: Modern Node.js Patterns
#3Yet more architecture astronaut behavior by people who really should just be focusing on ifs, fors, arrays, and functions.
Re: Modern Node.js Patterns
#4Yet more architecture astronaut behavior by people who really should just be focusing on ifs, fors, arrays, and functions.
Architecture astronaut is a term I hadn't heard but can appreciate. However I fail to see that here. It's a fair overview of newish Node features... Haven't touched Node in a few years so kinda useful.
Re: Modern Node.js Patterns
#5Thank you for this. Very helpful as I was just starting to dig into node for first time in a few years.
Re: Modern Node.js Patterns
#6Yet more architecture astronaut behavior by people who really should just be focusing on ifs, fors, arrays, and functions.
One of the core things Node.js got right was streams. (Anyone remember substack’s presentation “Thinking in streams”?) It’s good to see them continue to push that forward.
Re: Modern Node.js Patterns
#7Yet more architecture astronaut behavior by people who really should just be focusing on ifs, fors, arrays, and functions.
Architecture astronaut is a term I hadn't heard but can appreciate. However I fail to see that here. It's a fair overview of newish Node features... Haven't touched Node in a few years so kinda useful.
It's a good one with some history and growing public knowledge now. I'd encourage a deep dive, it goes all the way back to at least CPP and small talk.
While I can see some arguments for "we need good tools like Node so that we can more easily write actual applications that solve actual business problems", this seems to me to be the opposite.
All I should ever have to do to import a bunch of functions from a file is
"import * from './path'"
anything more than that is a solution in search of a problem
Re: Modern Node.js Patterns
#8Yet more architecture astronaut behavior by people who really should just be focusing on ifs, fors, arrays, and functions.
what? This is an overview of modern features provided in a programming language runtime. Are you saying the author shouldn’t be wasting their time writing about them and should be writing for loops instead? Or are you saying the core devs of a language runtime shouldn’t be focused on architecture and should instead be writing for loops?
Re: Modern Node.js Patterns
#9Yet more architecture astronaut behavior by people who really should just be focusing on ifs, fors, arrays, and functions.
One of the core things Node.js got right was streams. (Anyone remember substack’s presentation “Thinking in streams”?) It’s good to see them continue to push that forward.
Why? Why is a stream better than an array? Why is the concept of a realtime loop and for looping through a buffer not sufficient?
Re: Modern Node.js Patterns
#10This is great. I learned several things reading this that I can immediately apply to my small personal projects.
1. Node has built in test support now: looks like I can drop jest!
2. Node has built in watch support now: looks like I can drop nodemon!