Kind of goes without saying, but the flip side of having all of these tools under a single opinionated umbrella is that if any piece of it sucks, people are going to drop the whole toolchain. Hence this is a high risk project, especially because everything is being built from scratch.
The Rome Toolchain: A linter, compiler, bundler, and more
31–34 of 34 posts
Re: The Rome Toolchain: A linter, compiler, bundler, and more
#32Earlier quoted context omitted.
This is a weird peculiarity of the JS ecosystem. The rest of programming ecosystems do not have dozens of tools all doing a build for you. When you run tests in C you do not use a special cli testing tool that also compiles your project... You just run cc on your test files and run it like everything else. Why JS prefers hiding the build I'll never understand.
Not sure I agree with that statement. For example, I know that nUnit and jUnit are test runners for the .NET and Java ecosystems, and both of those are also runnable via the CLI. As for the JS ecosystem, it's definitely developed differently than other languages, because it deals with a very different set of constraints. See this article for background explanation (which also links to further reading) https://www.swy…
Re: The Rome Toolchain: A linter, compiler, bundler, and more
#33I will be keeping my eye on Rome
Re: The Rome Toolchain: A linter, compiler, bundler, and more
#34There are very old reports saying the Rome build times are quite long, longer than a day even. Has this changed?