tools

Reminded me of RJSON: https://github.com/rome/tools/issues/13 In MAML, are comments preserved when reserializing?

The article really needs a date too. It talks about projects like Rome as if they're current when Rome was archived a year and a half ago: https://github.com/rome/tools I think it used to have one but it was lost in a site redesign a few months ago: https://github.com/leerob/site/pull/727/files#diff-888ddb306...

It definitely existed by the time rome_console/biome_console was created! The crate was created 2 years ago[1] and miette was released more than 2 years ago[2]. By the time rome_console was created miette was on v4, so presumably somewhat mature. [1]: https://github.com/rome/tools/commits/main/crates/rome_conso... [2]: https://crates.io/crates/miette/versions

Some preliminary works were done [0]. [0] https://github.com/rome/tools/issues/4658

Biome formats and lints your JavaScript and TypeScript code in a fraction of a second. Biome is the community successor of Rome [0]. As part of the announcement of Biome [1], we have released the first stable version of Biome [2], which includes many bug fixes and new features! Join us on our Discord [3] to share the excitement of the launch! I am one of the main maintainers of Biome. I will be happy to answer any question :) [0] https://github.com/rome/tools [1] https://biomejs.dev/blog/annoucing-biome [2] https://biomejs.dev/blog/biome-v1 [3] https://discord.com/invite/BypW39g6Yc

I have no idea how true this is, but the source of the claim seems to come from here: https://github.com/rome/tools/discussions/4302 "But in short, the company Rome Tools ran out of funding, so the core team of last year are no longer working on the project." Of course this also seems to be second-hand information, as there is an "Anyone feel free to correct me" disclaimer at the end of the message above.

For now, Rome implements most of the ESLint recommended rules (including TypeScript ESLint) and some additional rules that are enabled by default. In the future, you can expect a recommended preset that is a superset of the ESLint recommended preset. So if you're not heavily customising ESLint, you should be able to use Rome. Otherwise, most of the rules are not fine-tunable in the way that ESLint is. Rome tries to provide the experience that Prettier provided in the formatting landscape: good defaults for a near-zero configuration experience. It tries to adopt the conventions of the JS/TS community. Still, some configuration is provided when the community is divided on some opinions (e.g. space vs. tab indentation, semicolons or as-needed semicolons, ...). There is an open issue [1] for listing equivalent rules between ESLint and Rome. E

Is not an official source, but it seems that it is the case according to this discussion[0], searching in the social media accounts there's nothing, also Sebastian[1] didn't published anything more about Rome since December [0] https://github.com/rome/tools/discussions/4302 [1] https://twitter.com/sebmck

Looking at the top contributors (https://github.com/rome/tools/graphs/contributors) that does not seem to be true? It is Ireland, undisclosed (the founder, so probably SF), France, and UK.

I am talking about compilation speed. I recently started working with Rust for contributing to projects like Rome/tools [1] and deno_lint [2]. My first impression with Rust is a bit frustrating: compilation takes tens of seconds or minutes. I am waiting in front of my IDE to get type hints / go-to def (often to fall-back to a text search). When I am launching unit tests, I am waiting that rust-analyzer terminates its indexing, and then I am waiting again that the tests compile… The tools are now mature, and a lot of engineering work is done on both rust compiler and rust-analyzer. I am afraid that the slow compilation of Rust is rooted to its inherent complexity. [1] https://github.com/rome/tools [2] https://github.com/denoland/deno_lint

Fast compilation seems very appealing. It is one of the main reason why I am interested into Go and Zig. I recently started working with Rust for contributing to projects like Rome/tools [1] and deno_lint [2]. The compilation and IDE experience is frustrating. Compilation is slow. I am afraid that this is rooted to the inherent complexity of Rust. [1] https://github.com/rome/tools [2] https://github.com/denoland/deno_lint

Exiting news! Congratulations to the Rome team! I hope that Rome will soon support semicolon removal [1] and lint rules such as explicit-module-boundary-types provided by Deno-lint [2]. [1] https://github.com/rome/tools/issues/3535 [2] https://lint.deno.land/?q=&all=on#explicit-module-boundary-t...

I found it interesting that a good chunk of outside contributions[1] happened before funding, and have almost completely stopped. [1] https://github.com/rome/tools/graphs/contributors

So I don't agree with GP poster that there's no reason to use spaces for indentation, but Rome recently switched to using tabs for accessibility reasons: https://github.com/rome/tools/issues/425 (Especially look at the Reddit thread linked from that issue: https://www.reddit.com/r/javascript/comments/c8drjo/nobody_t... ) (The problem is that people with visual impairment disabilities benefit a lot from being able to customize tab widths.)

This is that facebook project though (not just the same name), see here: https://github.com/rome/tools/blob/main/website/src/blog/pos... Seems like the author could take it with him when leaving facebook, which is nice.