| ▲ | sankalpmukim 8 hours ago |
| I wonder why did it take so long for someone to make something(s) this fast when this much performance was always available on the table.
Crazy accomplishment! |
|
| ▲ | WD-42 7 hours ago | parent | next [-] |
| Because Rust makes developers excited in a way that C/C++ just doesn't. |
| |
| ▲ | pjmlp 5 hours ago | parent | next [-] | | Yeah, it is as if there were never other compiled languages before to rewrite JavaScripting tooling. | | |
| ▲ | dwattttt 4 hours ago | parent [-] | | The word 'excited' in GP's post isn't decorative. | | |
| ▲ | pjmlp 4 hours ago | parent [-] | | I am fully aware of it, there have been many 'excited' posts in HN history about various programming languages, with related rewrite X in Y, the remark still stands. |
|
| |
| ▲ | phplovesong 3 hours ago | parent | prev | next [-] | | We had many languages that are faster that are not c/c++. Compare Go (esbuild) to webpack (JS), its over 100x faster easily. For a dev time matters, but is relative, waiting 50sec for a webpack build compared to 50ms with a Go toolchain is life changing. But for a dev waiting 50ms or 20ms does not matter. At all. So the conclusion is javascript devs like hype, and flooded Rust and built tooling for JS in Rust. They could have used any other compiled languge and get near the same peformance computer-time-wise, or the exact same time human-timewise. | | | |
| ▲ | grougnax 5 hours ago | parent | prev [-] | | C++ is pure trash C is fine but old | | |
|
|
| ▲ | chrysoprace 6 hours ago | parent | prev | next [-] |
| I believe it goes back a few years to originally being just oxlint, and then recently Void Zero was created to fund the project. One of the big obstacles I can imagine is that it needs extensive plugin support to support all the modern flavours of TypeScript like React, Vue, Svelte, and backwards compatibility with old linting rules (in the case of oxlint, as opposed to oxc which I imagine was a by-product). |
|
| ▲ | TheAlexLichter 5 hours ago | parent | prev | next [-] |
| For a couple of reasons: * You need have a clean architecture, so starting "almost from scratch"
* Knowledge about performance (for Rust and for build tools in general) is necessary
* Enough reason to do so, lack of perf in competition and users feeling friction
* Time and money (still have to pay bills, right?) |
|
| ▲ | nullsanity 6 hours ago | parent | prev | next [-] |
| It takes a good programmer to write it, and most good programmers avoid JavaScript, unless forced to use it for their day job. in that case, there is no incentive to speed up the part of the job that isn't writing JavaScript. |
| |
| ▲ | pjmlp 5 hours ago | parent | next [-] | | Some of us, already have all the speed we need with Java and .NET tooling, don't waste our time rewriting stuff, nor need to bother with borrow checker, even if it isn't a big deal to write affine types compliant code. And we can always reach out to Scala or F# if feeling creating to play with type systems. | |
| ▲ | wiseowise 2 hours ago | parent | prev [-] | | > It takes a good programmer to write it, and most good programmers avoid JavaScript, unless forced to use it for their day job. Nonsense. |
|
|
| ▲ | throw567643u8 3 hours ago | parent | prev [-] |
| Fractured ecosystem. Low barrier to entry, so loads of tooling. |
