Live data from Hacker News

The Rome Toolchain: A linter, compiler, bundler, and more

github.com

31–34 of 34 posts

Re: The Rome Toolchain: A linter, compiler, bundler, and more

#31
post #19

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.

There’s a constantly swinging pendulum between “one tool to rule it all” and “bring your own tool.” Newcomers to an ecosystem get tired learning all the accumulated toolchain and want to build a thing to solve every problem. But it is always easier to build a tool that does only one thing, and gradually people replace each part of that one tool with better standalone tools, the ecosystem disintegrates into pieces. The cycle goes on. There’s no right or wrong, only nature.

Re: The Rome Toolchain: A linter, compiler, bundler, and more

#32
post #9
post #8

Earlier 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…

ayy tx for shoutout

Re: The Rome Toolchain: A linter, compiler, bundler, and more

#33
I am very pleased with Webpack, but it definitely shows its roots as a specifically javascript bundler with other formats hacked on top. For instance, while one can have a `.css` file or `.html` file as an entry point, Webpack will nevertheless output a `.js` file with the same name for every entrypoint.

I will be keeping my eye on Rome

Post reply on HN