Earlier quoted context omitted.
If they end up using Rome internally that should be a good sign that it will be supported for years to come. React has been very well maintained for the past 5+ years.
I don't know. I don't think they stopped testing, but their open-source javascript testing framework jest has been unmaintained for a little while.
Rome: An experimental JavaScript toolchain
51–60 of 96 posts
Re: Rome: An experimental JavaScript toolchain
#52I 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...
[1] https://www.folklore.org/StoryView.py?story=Negative_2000_Li...
Re: Rome: An experimental JavaScript toolchain
#53Maybe this is intuitive to JS devs, but what are the advantages of "zero third-party dependencies" and "being a comprehensive tool for the processing of anything JS related" or any of the other selling points of Rome? It seems like an impressive project, but it's not obvious to me what its actual benefits are.
Dependencies are great for solving problems you are not willing or capable of solving. They are great when you need them, but most software includes dependencies that aren't needed or even directly requested. That is bloat. For example the Angular JS framework requests nearly 1100 NPM dependencies. That is a tremendous amount of code for an insignificant value add.
Re: Rome: An experimental JavaScript toolchain
#54Re: Rome: An experimental JavaScript toolchain
#55> Rome has a logo of an ancient Greek spartan helmet. It's not very relevant since it's not Roman, but it looks cooler than a Galea. It's OK. JavaScript has very little to do with Java, so it fits.
Re: Rome: An experimental JavaScript toolchain
#56Maybe this is intuitive to JS devs, but what are the advantages of "zero third-party dependencies" and "being a comprehensive tool for the processing of anything JS related" or any of the other selling points of Rome? It seems like an impressive project, but it's not obvious to me what its actual benefits are.
Re: Rome: An experimental JavaScript toolchain
#57Earlier quoted context omitted.
typescript is just a language, how is that a dependency? by that logic, nothing is dependency free.
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.
Yes, that tool is Rome. They are re-implementing the TypeScript compiler, just like everything else
Re: Rome: An experimental JavaScript toolchain
#58It says "No Third Party Dependencies" but 95% of the code is written in TypeScript, so it isn't even JavaScript and the entire thing is built on top of one big dependency. Would not be a problem if it didn't sell itself as "zero third party dependencies" while being built on top of one that is not even JavaScript... Might as well built the tool in any other language that would have been better for the task.
typescript is just a language, how is that a dependency? by that logic, nothing is dependency free.
What this project means by no dependencies is that there is nothing external pulled into the compiled JavaScript.
Re: Rome: An experimental JavaScript toolchain
#59Earlier quoted context omitted.
typescript is just a language, how is that a dependency? by that logic, nothing is dependency free.
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.
Re: Rome: An experimental JavaScript toolchain
#60From the Getting Started Guide: > Then, navigate into it and build rome: > cd rome; ./scripts/build-release dist Be aware that this command might take a long time to complete. After all, Rome wasn't built in a day.