Rome: An experimental JavaScript toolchain
1–10 of 96 posts
Re: Rome: An experimental JavaScript toolchain
#2Re: Rome: An experimental JavaScript toolchain
#3Re: Rome: An experimental JavaScript toolchain
#4After all, Rome wasn't built in a day.
Re: Rome: An experimental JavaScript toolchain
#5Re: Rome: An experimental JavaScript toolchain
#6This is a really exciting idea to me, but this website is pretty anemic (guessing it's a work in progress?). Kinda surprising to me, given the 7K stars on github. Maybe it should be submitted when it's a little more filled in?
Personally, considering how ambitious the project is, I was hoping they would go just a bit more ambitious and cover type checking as well (rather than just transpile out the syntax), otherwise we still need to install Typescript/flow and run their parsers independently from rome.
Re: Rome: An experimental JavaScript toolchain
#7I mean, clarifying that it's in-progress is important. After all, Rome wasn't built in a day.
And when you do something with your project they didn't anticipate their response would be: 'When in Rome...'.
Re: Rome: An experimental JavaScript toolchain
#8I mean, clarifying that it's in-progress is important. After all, Rome wasn't built in a day.
Re: Rome: An experimental JavaScript toolchain
#9Maybe 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.