What does it compile JavaScript to? WebAssembly or machine code or something else?
TypeScript and JSX to JavaScript.
Rome: An experimental JavaScript toolchain
71–80 of 96 posts
Re: Rome: An experimental JavaScript toolchain
#72An alternative lightweight and fast JavaScript buildchain using Snowpack: https://github.com/garage11/vuepack-demo
Re: Rome: An experimental JavaScript toolchain
#73Earlier quoted context omitted.
But the end users can't run the typescript, whereas they can run javascript directly. So, an external tool is required by the developer. A similar comparison would be shipping a program to end users, saying that 'no dependencies required', but instead of giving them a binary to run, you hand them a c++ file. I think everyone would agree that a C++ compiler is clearly a required dependency in that case.
Nobody says a C file has a "dependency" because you have to compile it.
Like that point is fair, but almost no C code has no dependencies. Like just a basic application that returns 0 and nothing else from main will need to link to crt0.
https://en.wikipedia.org/wiki/Crt0
However, you can compile C code as a bin file (just instructions). More common in the embedded world or you need to bootstrap an OS ect...
Re: Rome: An experimental JavaScript toolchain
#74Can't we just use SVG instead of all this JavaScript crap?
Re: Rome: An experimental JavaScript toolchain
#75Earlier quoted context omitted.
The scope is even broader! Webpack is just a bundler. Rome is a bundler, linter, test runner, typescript compiler, and formatter. The proper comparison would be Webpack + ESLint + Jest + TSC + Prettier.
Thank you! So, this is a bundler with built in plugins? Is there is a way to add Babel etc, that I would have used with Webpack? Does it handle CSS? And why would I prefer this over that chain (simpler to set up? Trust in Facebook over the people at js.foundation?)
The selling point is that you don't need plugins at all. Rome is the entire toolchain in one tool. For example, you don't need to add Babel because Rome handles transpilation.
The question is - will Rome perform as well as all the tools it intends to replace. Can it be a better Babel than Babel is? (There's a good chance it could since the creator of Rome is the creator of Babel)
Re: Rome: An experimental JavaScript toolchain
#76I have been following the progress of this project on Twitter for months. However I'm very skeptical to see this project used in a production app. Re-implementing the entire JS toolchain for a modern SPA is a HUGE task, just checkout CRA dependencies : https://github.com/facebook/create-react-app/blob/master/pac...
yes this is a very ambitious project but with enough time and resources it can serve the JavaScript a great service.
I believe in Sebastian. He can do it.
Re: Rome: An experimental JavaScript toolchain
#77Re: Rome: An experimental JavaScript toolchain
#78Previous discussion: https://news.ycombinator.com/item?id=22430682
Same jokes too.
Re: Rome: An experimental JavaScript toolchain
#79Re: Rome: An experimental JavaScript toolchain
#80Earlier quoted context omitted.
It's not intuitive to me as a JS dev too... Are you guys gonna re-implement typescript for example? Where does 'no deps' line get drawn?
"No dependencies" isn't quite accurate. There are a couple, and they are TypeScript and related packages: https://github.com/facebookexperimental/rome/tree/master/nod... But everything else is on track to be reimplemented within Rome.
Note that the TypeScript dependency is not used at runtime. It's only used to type check the Rome source code.