4 ms·
> worse than I thought it would be, bordering on useless. I'm all ears! Will revise it later today Not sure about you, but I really do hate Babel, Prettify, t
by Hexagon56k 3y ago
> worse than I thought it would be, bordering on useless.
I'm all ears! Will revise it later today
Not sure about you, but I really do hate Babel, Prettify, tsc, uglify and all that. I think it's awesome that they are integrated in Deno and Bun, and starting to get integrated into Node.
We all know that Node has a massive ecosystem, job opportunities and all that, do I really need to list that as features? I don't think any company would read this and think "Woah, let's ditch node!"
Should I list "better compatibility with existing Node modules" as a feature for Bun?
- report-to-trees 3y agoI think the problem with what you have now is that the feature comparison values "built in" above any other qualities. Obviously would require a much bigger article but I think the only way this is useful is if there is a comparison of tools in each runtime and "built in" is simply a pro in that comparison.
- Hexagon56k 3y agoHow about something like "<green check> (Built in)", "<green check>(Native Ecosystem)", "<yellow check> (Third party), "<red cross>" as a fix which avoids loads of text?
- report-to-trees 3y agoIn my opinion that would be much more helpful than what was there before, it still gives preference to built in tools above all other criteria but you at least avoid the false impression that tools provided by the ecosystem don't exist.
- Hexagon56k 3y agoDone!