61–70 of 168 posts
The author has supposedly created a company ( https://sf.tools/ ), with a broken /jobs page, and yet is developing the project under their personal GitHub account. Does not look trustworthy.
The author shared their experience building the first version in a month: https://themackabu.dev/blog/js-in-one-month And then the follow up few months later: https://themackabu.dev/blog/ant-part-two I'm not sure what the economics of building a new runtime and ecosystem from scratch are but it seems we're already in a phase where individual developers are creating software which previously took a whole team. And its…
The author has supposedly created a company ( https://sf.tools/ ), with a broken /jobs page, and yet is developing the project under their personal GitHub account. Does not look trustworthy.
I’m not that deep in the JS ecosystem or runtimes, but I’m a little surprised by some of the claims here about being smaller, having fast starts, sandboxing, performance-competitive, etc. Does anyone have a sense of what insights, design choices, big bets, etc, unlock all these advantages against already mature and highly optimised JS stacks?
I don’t really see how you appeal to JavaScript developers with “small binaries”. What is a 50mb runtime you down once next to a 200mb node_modules ?
What's the benefits over v8?
its ~8mb including the entire runtime and node-compat work. pretty simple to embed anywhere as well
How is it so much smaller than V8 while also apparently including a package manager, a web server, a TypeScript compiler and a hypervisor?
I don’t really see how you appeal to JavaScript developers with “small binaries”. What is a 50mb runtime you down once next to a 200mb node_modules ?
At least with bun you can compile with bytecode enabled. That, tree shaking and other optimizations our production app entire docker image is like 120mb...