4 ms·
So after node, the ion, then the merge, then deno, now bun. JS started to get a bit sane, but I guess we are going back to fragmenting and madness pretty soon.
by BiteCode_dev 4y ago
So after node, the ion, then the merge, then deno, now bun.
JS started to get a bit sane, but I guess we are going back to fragmenting and madness pretty soon.
- andrew_ 4y agoNot really. Know your history first. Node split to io.js due to team disagreements and fragmentation. io.js made an immense amount of progress, adopted semver, and had all the momentum. At the time, Node was stagnant. The choice to merge was rational and good. Deno is a separate project, and while has a node compat mode, is meant to be a TS-first ecosystem with many different rules and methodologies. Bun is an experiment to see if it's possible to build node greenfield today. Only the brave will use it in prod, and only the wild mustangs of management will allow it. Try not to give into FUD. The JS universe is fine.