11–20 of 198 posts
Yes, I know there's probably better options than Rust for building APIs, but I wanted to learn it, so why not?
It's weird their promotional video repeats "you can do without installing dependencies", if I want headless browser testing is that wrong to install a project that offers that? Why would I want everything reimplemented in this massive binary? Why would Bun be anymore in touch with nuances of all these different technologies then individual projects dedicated to their own speciality? JS Runtime, Package Manager, Test…
It's funny because the top article on HN is about a malicious rust crate package, and people keep making comparisons to js/npm and how both language suffer from frequent security issues because they have weak std libs.
It's weird their promotional video repeats "you can do without installing dependencies", if I want headless browser testing is that wrong to install a project that offers that? Why would I want everything reimplemented in this massive binary? Why would Bun be anymore in touch with nuances of all these different technologies then individual projects dedicated to their own speciality? JS Runtime, Package Manager, Test…
This blog post / changelog is extremely long. Around 50 metres long on mobile.
How is this even possible?
I know we're all using AI, but Bun seems like the one singular project where there's just been a crazy increase in the amount of output, a 10x on the 10x.
How are they doing this?
Earlier quoted context omitted.
Its strange how flip floppy the JS ecosystem is, because go back literally 1-3 years or so and the BIGGEST complaint was the lack of a standard library and having to use a package for everything. But now that Bun is actually doing it its somehow bad? Its also still open source, so those implementations you mention need dedicated teams can still get the attention they need by the community if needed. I'm on the side t…
I agree and I also wish Node did more. Otoh should a standard lib give you absolutely everything? Probably not. There needs to be a line somewhere. Right now Bun’s policy on this seems to be "whatever Jarred feels like should be in there".
This is the main draw. Everything he implemented was fast and minimalist and he usually implements a standardized api (web apis, esbuild bundler api).
The opinionated stuff is usually very common sense.
Most of the libraries OC mentions are things you would just like to be as fast as possible above all else.
It's weird their promotional video repeats "you can do without installing dependencies", if I want headless browser testing is that wrong to install a project that offers that? Why would I want everything reimplemented in this massive binary? Why would Bun be anymore in touch with nuances of all these different technologies then individual projects dedicated to their own speciality? JS Runtime, Package Manager, Test…
Its strange how flip floppy the JS ecosystem is, because go back literally 1-3 years or so and the BIGGEST complaint was the lack of a standard library and having to use a package for everything. But now that Bun is actually doing it its somehow bad? Its also still open source, so those implementations you mention need dedicated teams can still get the attention they need by the community if needed. I'm on the side t…
I feel like nobody complained that you needed to install a dependency to do headless browser testing for example.
It's weird their promotional video repeats "you can do without installing dependencies", if I want headless browser testing is that wrong to install a project that offers that? Why would I want everything reimplemented in this massive binary? Why would Bun be anymore in touch with nuances of all these different technologies then individual projects dedicated to their own speciality? JS Runtime, Package Manager, Test…
A couple years ago a common complaint was that the JavaScript ecosystem relied too heavily on dependencies for everything. Remember the left-pad incident where the developer deleted the popular dependency out of protest for reasons I can even remember? Or when colors.js was sabotaged to break everything that depended on it? The node-ipc package was sabotaged to delete files on developer’s machines. Then we had a wave of supply chain attacks that tried to insert malware into build scripts of popular dependencies.
So the ecosystem started moving toward more batteries-included style development in response.