4 ms·

I look at tools like Rome and they might have been relevant 5 years ago. I think Bun has a better shot than Deno because it has a very fast built in node_modul

I look at tools like Rome and they might have been relevant 5 years ago. I think Bun has a better shot than Deno because it has a very fast built in node_modules installer. But I think Bun's goals are too ambitious - trying to be all things to all projects from a single binary. No one cares if you have to use a separate binary, esbuild, for all your bundling needs, for example. It's amusing how the entire JS ecosystem put up with such slow build times for a decade. If these JS tools teach us anything it's that JavaScript doesn't cut it for performance and a compiled language is the way to go.

samsquire 3y ago
My guess is that IO latency is the reason why Javascript tools are slow. Creating lots of separate TCP connections to download a tarball and then store it to disk, then decompress it and then write the files it contains. Lots of small files IO slows things down versus one large contiguous file transfer. If it is IO that is causing slow project builds, then the IO in theory would be slow with compiled tools as well.
conaclos 3y ago
Bun do not plan to implement a formatter or a linter. This makes Rome and others still relevant.
veidr 3y ago
I don't get your central point. What is different about now compared to 5 years ago, when it comes to a code linter and/or bundler? At first glance, I thought you were saying "this Rome thing might have been relevant 5 years ago, but now Bun and Deno exist, so it is not." But, that didn't really make sense because Bun and Deno are both new and growing and there's no clear winner, or even leader, in the "post-NodeJS runtimey programming thingamajig and excution environment". Re-reading your comment, though, it seems like what you are really saying is "JavaScript itself is slow, so it is no longer relevant". But when stated so plainly that sentiment becomes absurd, so as a reader I sort of mentally revise my interpretation of it to "JavaScript is slow (yes), so I personally wish people would just switch to faster languages". But that doesn't really make sense in this context, either, because this tool is written in Rust. So... what are you saying? What thot r u the thinkr of here?
v0idzer0 3y ago
Using compiled languages to build UI in a browser is still a disaster. And yes, I’ve tried them all from applets to AS3 to elm to bucklescript to Rust via WASM

samsquire 3y ago

My guess is that IO latency is the reason why Javascript tools are slow. Creating lots of separate TCP connections to download a tarball and then store it to disk, then decompress it and then write the files it contains. Lots of small files IO slows things down versus one large contiguous file transfer. If it is IO that is causing slow project builds, then the IO in theory would be slow with compiled tools as well.

conaclos 3y ago

Bun do not plan to implement a formatter or a linter. This makes Rome and others still relevant.

veidr 3y ago

I don't get your central point. What is different about now compared to 5 years ago, when it comes to a code linter and/or bundler? At first glance, I thought you were saying "this Rome thing might have been relevant 5 years ago, but now Bun and Deno exist, so it is not." But, that didn't really make sense because Bun and Deno are both new and growing and there's no clear winner, or even leader, in the "post-NodeJS runtimey programming thingamajig and excution environment". Re-reading your comment, though, it seems like what you are really saying is "JavaScript itself is slow, so it is no longer relevant". But when stated so plainly that sentiment becomes absurd, so as a reader I sort of mentally revise my interpretation of it to "JavaScript is slow (yes), so I personally wish people would just switch to faster languages". But that doesn't really make sense in this context, either, because this tool is written in Rust. So... what are you saying? What thot r u the thinkr of here?

v0idzer0 3y ago

Using compiled languages to build UI in a browser is still a disaster. And yes, I’ve tried them all from applets to AS3 to elm to bucklescript to Rust via WASM