3 ms·
It'll be equally hard to write it from scratch in rust as it would be to add this to esbuild. Maybe there are some considerations I don't know about but it doe
by kjksf 3y ago
It'll be equally hard to write it from scratch in rust as it would be to add this to esbuild.
Maybe there are some considerations I don't know about but it does seem like hard forking esbuild would be much faster way to get there (hard fork so that they are not blocked or slowed down by whatever esbuild owner wants).
- pas 3y agoIt really depends on who (which team) is doing it. I would almost surely give up before understanding what esbuild does and how, and what needs to be modified. (Because Go basically gives me the creeps.) So someone with a lot of Rust experience probably simply opts for the rewrite. That said, it seems folks on the Vite team decided to give this a try because of oxc_parser (a JS parser written in Rust), so probably it's not because of Rust-Go sentimentalism. // Though ... there's also otto[1] (a JS parser in Go) ... so who knows! :)) // And of course even more context here[2] and here[3] (this one is from Evan You) // [1] https://github.com/robertkrimen/otto https://github.com/robertkrimen/otto [2] https://news.ycombinator.com/item?id=39641634 https://news.ycombinator.com/item?id=39641634 [3] https://news.ycombinator.com/item?id=39648399 https://news.ycombinator.com/item?id=39648399