3 ms·
This seems a little giddy to me. In your linked article they claim that parts of key JS infra is being rewritten in Rust, but the claim seems exaggerated from
by andsoitis 4y ago
This seems a little giddy to me.
In your linked article they claim that parts of key JS infra is being rewritten in Rust, but the claim seems exaggerated from where I sit. For instance, they list webpack but is that a good example of huge momentum to rewrite webpack in rust?
You Python examples are of libraries that are used at runtime, not infrastructure.
Coming back to JS, this svelte project is noted by the author as being very early stage and it seems more like a learning project for them. I don’t need to add that svelte isn’t nearly as broadly used as other JS tech.
Don’t get me wrong, I’m not saying writing tools in faster compiled languages shouldn’t be done, but one might find that the excitement and prediction seems premature. There are trade offs - speed isn’t free.
- cercatrova 4y ago> huge momentum to rewrite webpack in rust Yes, see swc and esbuild (in Go) for examples. They are taking off in the JS world such that many other frameworks are eschewing Webpack and wrapping them due to their sheer speed, like NextJS with swc and Vite with esbuild. > libraries that are used at runtime, not infrastructure Sure, I was just giving an example. I would say though that due to JS being interpreted (okay, JITed), the infrastructure would have to run Webpack anyway, in order to bundle/compile the JS. > this svelte project is noted by the author as being very early stage and it seems more like a learning project for them I'm not talking about this project in particular, just the JS ecosystem as a whole is trending towards compiled-language tooling. But I will say though that this trend is not early stage as the examples above like swc/esbuild have been some years in the making. If anything this will simply accelerate such progress.