message: Blog post tweaks
diff: @@ -13,7 +13,7 @@ layout: layouts/blog.liquid
  We're excited to announce the first release and general availability of the **Rome** linter for JavaScript and TypeScript.
  -This is only the beginning. Rome is not only linter but also a compiler, bundler, test runner, and [more](#development-status), for JavaScript, TypeScript, HTML, Markdown, and CSS. We aim to unify the entire frontend development toolchain.
  +This is only the beginning. Rome is not only linter but also a compiler, bundler, test runner, and [more](/#development-status), for JavaScript, TypeScript, HTML, Markdown, and CSS. We aim to unify the entire frontend development toolchain.
  Rome is a [monolithic](https://en.wikipedia.org/wiki/Monolithic_application) tool containing functionality that has traditionally been separate tools in the frontend ecosystem. We call this a toolchain. It is **not** a collection of existing tools, but completely custom, built [largely](/credits) from scratch, contained entirely in a single package and codebase.
  @@ -55,11 +55,9 @@ There would have been no way to provide backward compatibility, and with expecta
  In an ode to the [Ship of Theseus](https://en.wikipedia.org/wiki/Ship_of_Theseus), if all components of an object are replaced, is it the same object? There is far less confusion and friction to release something entirely new than drastically change something that's already in widespread usage. I had since moved on from the project, and so any evolution would not have been possible, and would have required complete vision alignment.
  -### Post-Babel
  -
  Even though I wasn't involved in Babel, I still maintained a presence in the developer tooling ecosystem. I eventually went on to develop other tools like [Yarn](https://yarnpkg.com/) and be involved in projects like [Prepack](https://prepack.io/) and [Flipper](https://fbflipper.com/). This work continued to develop the ideas that would eventually become Rome and shaped my philosophy on developer experience. A focus on excellent errors, clean user interface, and minimal configuration.
  -{% include figure.liquid, width: 500, src: "/img/blog/introducing-rome-post-babel-logos.png", description: "The logo of Yarn, Prepack, and Flipper" %}
  +{% include figure.liquid, width: 500, src: "/img/blog/introducing-rome-post-babel-logos.png", description: "The logos of Yarn, Prepack, and Flipper" %}
  The original idea behind Babel had always stuck. What sort of capabilities would be possible if a tool did more than one thing? This sort of philosophy has always seemed alien in the JavaScript ecosystem where micropackages and arbitrary separation of concerns are the norms. These tools being independent has never provided the sort of user autonomy and efficiency that most skeptics of [monolithic](https://en.wikipedia.org/wiki/Monolithic_application) tools proclaim.
  @@ -67,8 +65,6 @@ Language tooling maintainers spend so much time working on the same things. Proc
  A linter in the JavaScript ecosystem is exactly the same as a compiler. They both consume code, then produce compiled code and errors. What the compiled code is varies. In the case of a linter, the compiled code is formatted source code with automatic fixes applied. The more powerful your compilation infrastructure, the more theoretically powerful your linter could be. These commonalities extend to pretty much anything that involves language processing. We can build more powerful tools using a shared base that is easily adaptable.
  -### Development
  -
  Rome is the spiritual successor of that idea, except rather than exposing a large public API for other tools to be built on, we are building them all in one place, with batteries included. We support frontend languages other than JavaScript too, those that can benefit the most from tight integration.
  I had always maintained private repos where I would experiment with ideas, but the original code that would become Rome was started at the beginning of 2017 while I was working for Facebook in my free time. I continued iterating and experimenting on the idea and building out all the different pieces, until 2019, when I was given the opportunity to work on and explore using it at Facebook full-time.
  