News for hackers. Stuff that matters.

A comment on The JavaScript Oxidation Compiler. Parent comment

Re:The JavaScript Oxidation Compiler by wiseowise on Monday February 23, 2026 @05:23AM (#47120390)
> But for a dev waiting 50ms or 20ms does not matter. At all.

It absolutely does:

https://mail.python.org/pipermail/python-dev/2018-May/153296...

https://news.ycombinator.com/item?id=16978932.

[ Parent | on HN ]
Re:The JavaScript Oxidation Compiler by pjmlp on Monday February 23, 2026 @07:31AM (#47121476)
To win benchmark games it does, in a world where people keep shipping Electron crap, not really.
[ Parent | on HN ]
Re:The JavaScript Oxidation Compiler by phplovesong on Tuesday February 24, 2026 @05:04AM (#47135146)
Not sure if you missed the /s?

Anyway, you posted about speed, and then followed by a link to some python related thing. In python speed has never been a key tenet, at least when it comes to pure cpu based calculations. How much tooling is built in python? All the modern python tooling is mostly Rust based too. So theres that.

I mean for a dev working in JS with JS built tooling the speed is not in milliseconds, but in seconds, even minutes.

I still think my point holds, having a build take int he 10s of seconds vs 50ms is very much good enough for development (the usual frontend save and refresh browser cycle)

[ Parent | on HN ]