Why people use Deno and Bun over Node? I think it's neat that there are competitors for JS runtimes, but I really don't understand what advantages I'd get by swapping to one of these over Node. Bun has no REPL and worse JS engine, Deno is just Node with a restrictive, annoying permission system and no sqlite. Both claim better performance, but that only seems true in cherrypicked benchmarks, and in my tests (granted…
I switched to Deno because it is the only option out of the 3 that allow monorepo workflow without building .d.ts files. Bun and Node both do type stripping or compiling of TS, but it only works for the entry package of the running script, not any of the linked dependencies from the same repo. There are still things I dislike about Deno, but it really does make package development a lot simpler. JSR is a great upgrad…
I am worried about Bun
361–368 of 368 posts
Re: I am worried about Bun
#362Earlier quoted context omitted.
> Basically the prime bet that they made (that one needs extremely expensive hardware to have useful AI) has already failed. I thought the prime bet was that the winning lab who reaches takeoff through recursive self improvement will make a galactic superintelligence. Not saying I believe this but the people running the labs do. Under this scenario if you are a few months behind at the pivotal time you might as well…
I don't think this race to superintelligence idea should be taken too seriously. It is great for headlines and get peoples imaginations up. It is mostly a marketing gag. I look at superintelligence this way: software engineering used to be considered amoung the most mentally demanding jobs one can have. And in this field more and more people give up large parts of their job and become approximately product managers t…
Re: I am worried about Bun
#363Earlier quoted context omitted.
Isn't that mostly just enums? Is there anything else that doesn't run as valid JS if you strip the types (and maybe some other extra keywords)out? Genuine question, in my head there's not much, but TS has a few weird corners I maybe haven't used
enums and decorators mainly. There are also subtleties such as having the ts file extension in imports. Also imports aren't transpiled in cjs so you need to need es modules. I'm using it in my projects with no issues.
Outside of that I’ve barely seen them used in typescript, they’re not really idiomatic in react projects
Re: I am worried about Bun
#364Earlier quoted context omitted.
1. At least 99% of all species that ever lived on Earth are now extinct. I.e., that's life. 2. "But for a beautiful moment in time we created a lot of value for shareholders."
Failure for those species though.
At least you could go out with the accomplishment of having out-competed some other species along the way.
Re: I am worried about Bun
#365Re: I am worried about Bun
#366Why people use Deno and Bun over Node? I think it's neat that there are competitors for JS runtimes, but I really don't understand what advantages I'd get by swapping to one of these over Node. Bun has no REPL and worse JS engine, Deno is just Node with a restrictive, annoying permission system and no sqlite. Both claim better performance, but that only seems true in cherrypicked benchmarks, and in my tests (granted…
Re: I am worried about Bun
#367All these complaints about Claude code are mostly resolved if you pay for your usage with direct API pay as you go. It’s not cheap but nearly all the complaints I see about Claude code are due to the fact the subscription plans seem unsustainable from a cost perspective.
Re: I am worried about Bun
#368I wonder why Anthropic chose to spend money on Bun when they could have easily spend that resource on Go which is fairly easy to use and fast. I'm sure their SWEs could easily everything things in Go. Anyone have insight on why?