What does HackerNews think of node?
Node.js JavaScript runtime :sparkles::turtle::rocket::sparkles:
Why is Bun fast?
... Zig's low-level control over memory and lack of hidden control flow makes it much simpler to write fast software. ...
Is your sense also that this is the root cause of Bun's outstanding speed? Node.js is written in C++ (although not primarily) which also requires low-level control over memory.Is there something about C++ that makes it less well-suited than Zig for what Bun does?
Or is the problem with Node.js that it relies too much on JavaScript rather than C++ in hot paths?[2]
[1] https://bun.sh/
This _just landed today_. You can get it by building from master:
```
# there is more details in building.md
git clone https://github.com/nodejs/node
cd node
# may need to pass --openssl-no-asm
./configure
make -j12
./out/Release/node --experimental-fetch
```
Otherwise - wait a bit for the next v17 release to land per the normal release cycle :)
And from there you can use GitHub Codespace to "develop in a cloud-hosted, customizable environment" to run and debug.
Would you (or anyone else reading this) be interested in exploring what that would look like for Node.js?
(If you do, feel free to reach me at my email in https://github.com/nodejs/node under benjamingr)
I think it would be interesting - one solution could be a loader (ESM) that only lets you load other "unprivileged" files by default - then importing things like `child_process` or `fs` could require more privilege. A little like how apps work.
> A programmatic way to tell if the publisher of a module has 2FA enabled.
I will bring this up. Personally I think I understand the objection of the reply below about this information being risky. That's something NPM likely can/should solve and not Node.js.
For what it's worth GitHub orgs can already tell who has or doesn't have 2FA. Node.js itself for example enforces GitHub 2FA for all the organization. I assume GitLab has a similar feature.
https://github.com/nodejs/node
It's only notable if any substantial portion of the community forks.
The "previous" fork, Io.js, was key moment for Node. Because that was about fundamental technical questions of choosing between stability versus innovation.
This appears to be yet another tweet-fight about CoC's. I can't imagine the community actually fracturing over this, but if it did then I would be fine with that. Let there be one set of conferences for the Douglas Crockford's of the world to discuss code, and another set of conferences for people to discuss Douglas Crockford.
This is aggravated in the JS world which is extremely Github-centric.
NodeJS: 730 open issues, 4323 closed issues, 324 open pull requests, 7201 closed pull requests: https://github.com/nodejs/node
Ansible: 1863 open issues, 9204 closed issues, 1084 pull requests, 11762 closed pull requests: https://github.com/ansible/ansible/issues