It's kind of a piece of shit still. I was hoping it would actually work with the 1.0 release, but it's still a buggy mess held together with spit and duct tape.
i dont use js but why are js devs so excited over js runtimes? everyone seems to hate node and want deno/bun to replace it but what is the difference its just the runtime not the language??
devs are using js for utilities nowadays its normal to find a bunch of stuff that requires node installed
node is fucking slow
you said it yourself, utilities are built with JS and just by changing the runtime you'll see significant performance improvements. I'll give you two examples: text formatters and LSPs, which are supposed to be really fucking fast, and they're not if they run on top of nodejs, but they become fast and smooth once switched to deno, and now - at least in theory - they''ll be even faster when running on top of bun
Bun simplifies the tool chain thanks to built in package manager and bundler and perhaps most importantly native Typescript support so there’s no need to transpire anymore - in that sense you could call it a different language
Adults in the room moved to Linux when Vista was the new shit. Now Windows is only good for playing fork knife, chinese gambling games, and other crap for kids
It's kind of a piece of shit still. I was hoping it would actually work with the 1.0 release, but it's still a buggy mess held together with spit and duct tape.
>More than 1,200 issues on GitHub, with dozens appearing every hour. >“package installer” has no way to install packages from private repos >Only true source for help is on fucking Discord server >“Ready for production” >Numerous blockers mentioned in zero-reply or “won’t fix” issues from MORE THAN YEAR AGO will make migration an extremely slow process for people who actually need to get work done.
What the fuck were these homosexual devs thinking with 1.0? It’s is just an alpha release.
Its gains are in its core library namely reading/writing files and anything under the Bun namespace, and its websockets server is quite fast which is powered by uWebsockets(written in C++ btw). Also it's package installation capabilities are really fast compared to the competition. So your existing project may work well but it will not gain much unless you rewrite your stuff to use Bun's namespace and utilities.
>once they implement support for nextjs
it already supports nextjs, i tried running my nextjs app on it and it just werked without having to touch anything, just run bun run dev instead of npm run dev
>No Windows support
retarded toy. sticking with Node.js and TypeScript
Bot
>Windows
lol..
cope seethe & dilate
>cope seethe & dilate
Why you say that to me for shitting on the winblowstard, when you shit on him yourself?
Because this is a shitposting spam thread. He didn't actually read your post.
Eh? Why do you need to run JavaScript on Windows anyway?
i dont use js but why are js devs so excited over js runtimes? everyone seems to hate node and want deno/bun to replace it but what is the difference its just the runtime not the language??
devs are using js for utilities nowadays its normal to find a bunch of stuff that requires node installed
cs and esm modules both just werking is actually huge
the js server-side module system is a clusterfuck
performance is nice too i guess
node is fucking slow
you said it yourself, utilities are built with JS and just by changing the runtime you'll see significant performance improvements. I'll give you two examples: text formatters and LSPs, which are supposed to be really fucking fast, and they're not if they run on top of nodejs, but they become fast and smooth once switched to deno, and now - at least in theory - they''ll be even faster when running on top of bun
Bun simplifies the tool chain thanks to built in package manager and bundler and perhaps most importantly native Typescript support so there’s no need to transpire anymore - in that sense you could call it a different language
>no Windows support
it should stay that way
Adults in the room moved to Linux when Vista was the new shit. Now Windows is only good for playing fork knife, chinese gambling games, and other crap for kids
blame webkit for no windows support. They just refuse to test on windows. As expected of walled garden applel iToddler
>>No Windows support
https://bun.sh/blog/bun-v1.0#bun-more-thing
Dropped
wintoddlers will always be second-class citizens in the software engineering world
windows is a consumer platform
It's kind of a piece of shit still. I was hoping it would actually work with the 1.0 release, but it's still a buggy mess held together with spit and duct tape.
>More than 1,200 issues on GitHub, with dozens appearing every hour.
>“package installer” has no way to install packages from private repos
>Only true source for help is on fucking Discord server
>“Ready for production”
>Numerous blockers mentioned in zero-reply or “won’t fix” issues from MORE THAN YEAR AGO will make migration an extremely slow process for people who actually need to get work done.
What the fuck were these homosexual devs thinking with 1.0? It’s is just an alpha release.
>What the fuck were these homosexual devs thinking with 1.0? It’s is just an alpha release.
Well yeah, it's 1.0.0-alpha
Yet, from their website: “Today, Bun is stable and production-ready.”
doesn't work on my code yet
post again when 2.0 is out
bros, I just use it to run current projects the way they would run with npm...
I try to convince myself that its faster, but I did time the startup, it's literally the same as npm run start
Its gains are in its core library namely reading/writing files and anything under the Bun namespace, and its websockets server is quite fast which is powered by uWebsockets(written in C++ btw). Also it's package installation capabilities are really fast compared to the competition. So your existing project may work well but it will not gain much unless you rewrite your stuff to use Bun's namespace and utilities.
>it will not gain much unless you rewrite
yeah, not doing any rewriting.. once they implement support for nextjs on their own, i might use it
>once they implement support for nextjs
it already supports nextjs, i tried running my nextjs app on it and it just werked without having to touch anything, just run bun run dev instead of npm run dev
>run bun run dev instead of npm run dev
yes, but, it is the same speed as npm run
I think he meant vercel actually doing the rewrite for him on nextjs internals
i just like it for the typescript support. even of there were no speed gains
Seems like something a tranny would use
>new dumb nagger cattle thing that won't be around in a year
I'll stick with Action Scripting.
comfy
Why he seems so happy?