Very smart. You can't lose all your customers for vibe-coding a migration to Rust if you are already written in Rust ;)
Show HN: Nub – A Bun-like all-in-one toolkit for Node.js
11–20 of 85 posts
Re: Show HN: Nub – A Bun-like all-in-one toolkit for Node.js
#12Very smart. You can't lose all your customers for vibe-coding a migration to Rust if you are already written in Rust ;)
They'll get bought out by OpenAI and convert the project to Zig
Re: Show HN: Nub – A Bun-like all-in-one toolkit for Node.js
#13I saw this on twitter and loved it, such a good move on your part Colin. Hope the project picks up tons of steam!
Re: Show HN: Nub – A Bun-like all-in-one toolkit for Node.js
#14Respect for embracing existing tech instead of rewriting a worse version of it. Wonder where we would be today if all alternative-building effort went to Node instead (with proper leadership).
Re: Show HN: Nub – A Bun-like all-in-one toolkit for Node.js
#15Love the idea, learning a lot of interesting things about node hooks by reading docs and some code
Re: Show HN: Nub – A Bun-like all-in-one toolkit for Node.js
#16Nice. Can we get `nub --compile` up in there like Bun has?
Re: Show HN: Nub – A Bun-like all-in-one toolkit for Node.js
#17Nice. Can we get `nub --compile` up in there like Bun has?
Coming very soon!
Re: Show HN: Nub – A Bun-like all-in-one toolkit for Node.js
#18Re: Show HN: Nub – A Bun-like all-in-one toolkit for Node.js
#19Respect for embracing existing tech instead of rewriting a worse version of it. Wonder where we would be today if all alternative-building effort went to Node instead (with proper leadership).
Fundamentally you can't fix a lot of things with this approach.
Simple example: Node is the only serious OSS software I know of that has no way to document its config (in the config file itself). It's moronic! The Node people just adopted JSON without a thought, and then refused to consider any alternatives (even "JSON with comments").
When an organization digs into bad decisions, the only way to fix them is to start something new. The entire JS ecosystem will never have documentation on its config as long as everyone keeps building on top of Node.
(And there are many other issues like this in the Node ecosystem; the utter absurdity of not being able to document config is just my personal pet peeve.)
Re: Show HN: Nub – A Bun-like all-in-one toolkit for Node.js
#20I’m surprised to see this using a `--require` hook (rather than `--import`). Maybe something’s changed significantly since I was looking into building some similar functionality… but it makes me wonder about nuances in nub’s ESM support.
(When I was investigating this it was very early in Node’s `--import` story, but there were several edge cases with the more common ESM-to-CJS approaches that I wanted to address. Most were probably exceedingly niche concerns, but I’d expect top-level await to affect a meaningful subset of users.)