It’s almost 100% compatible with node but faster. A lot faster. So no need to learn anything but few cli commands. For example bun run dev instead of npm run dev.
I’m trying to get my work to switch to bun but we have packages in a private AWS codeartifact repo. Does it support this? I tried to use it with our npmrc file but it couldn’t install those packages.
IMO, deno’s approach was bad as it was reinventing the wheel, so one had to relearn. And then they brought package.json which they said they wouldn’t. This again got people to unlearn and relearn things.
Bun, on the other hand, acts like what Typescript is to Javascript. It’s just feels like superset of Node, instead of completely different tool.
Makes sense. Deno was created by the same person that created node. They’re both going to be terrible, especially when they ignore everything ever discovered in software engineering about writing good code, good frameworks, good languages, etc.
gotcha. I don’t think bun is created by the same person that created node. deno is, and has just as bad a design as node as a result. it honestly baffling that people trust someone to write a language who failed so badly to write a language that they set back the entire world for decades to come.
Oh no. Another thing to learn.
It’s almost 100% compatible with node but faster. A lot faster. So no need to learn anything but few cli commands. For example
bun run devinstead ofnpm run dev.Edit: website
Alias npm bun level compatibility?
It does seem so!
I’m trying to get my work to switch to bun but we have packages in a private AWS codeartifact repo. Does it support this? I tried to use it with our npmrc file but it couldn’t install those packages.
This answers my question https://bun.sh/docs/install/registries
This is the first I’ve heard of this. Might be worth checking out.
you probably don’t need to learn it, Deno was a massive upgrade over Node and it didn’t matter, not convinced this will be any different.
IMO, deno’s approach was bad as it was reinventing the wheel, so one had to relearn. And then they brought package.json which they said they wouldn’t. This again got people to unlearn and relearn things.
Bun, on the other hand, acts like what Typescript is to Javascript. It’s just feels like superset of Node, instead of completely different tool.
I expect Bun will get more success than Deno.
Makes sense. Deno was created by the same person that created node. They’re both going to be terrible, especially when they ignore everything ever discovered in software engineering about writing good code, good frameworks, good languages, etc.
deno was also created by one of the guys who created node.
huh? that’s what I said.
sorry, brainfart. I read “bun is created as the same who created node” 🤦🏻♂️
gotcha. I don’t think bun is created by the same person that created node. deno is, and has just as bad a design as node as a result. it honestly baffling that people trust someone to write a language who failed so badly to write a language that they set back the entire world for decades to come.
idk I think people can learn from their mistakes and evolve. especially if they accept collaboration and RFCs.
I haven’t worked much with deno, so I can’t tell. But I earn my living with Node and it’s ok. I still hate js more than node itself.
idk I think people can learn from their mistakes and evolve. especially if they accept collaboration and RFCs.
I haven’t worked much with deno, so I can’t tell. But I earn my living with Node and it’s ok. I dislike js way more than node itself.
I guess all the hate is around module resolution and package management.
God my thoughts exactly. Probably super cool, but still I just can’t keep up
Compatible with node
This will be last 🥲