Bytes #9, published August 17, 2020, is a short developer newsletter built around Rome’s ambitions for frontend tooling. It also summarizes the React 17 release candidate, looks back at the IBM 5150, and rounds out the issue with a React code puzzle and developer links. Its software coverage is a snapshot of 2020, not a guide to what developers should adopt today.
Why Rome was the lead story
Bytes introduced Rome’s first beta as “just a simple linter for JavaScript and TypeScript,” then pointed to a much broader goal: bringing several parts of frontend development into one package. The intended scope included compilation, bundling and testing as well as linting.
As an Amazon Associate I earn from qualifying purchases.
The issue attributed Rome’s announcement to Sebastian McKenzie, describing him as Babel’s creator. It presented Rome as a renewed attempt at consolidating frontend tools after McKenzie had previously considered bringing that work together within Babel. The newsletter’s boldest formulation was that “Rome is designed to replace Babel, ESLint, webpack, Prettier, Jest, and others.” That describes the project’s ambition as presented in 2020; it is not evidence that Rome had already replaced those tools or that the claim reflects Rome’s present-day scope.
What the issue said about React 17
React 17 was at release-candidate stage when the issue appeared. Bytes highlighted gradual upgrades, a change to event delegation, the new JSX transform and the removal of event pooling. The React team’s August 10, 2020 release-candidate post described the release as focused on making React easier to upgrade, rather than adding developer-facing features. As the post put it: “The React 17 release is unusual because it doesn’t add any new developer-facing features.”
Gradual upgrades and event delegation
The React team framed React 17 as a stepping stone intended to make gradual upgrades between React versions safer. One relevant change was moving most event handlers from the document level to the root DOM container. The team said this would make it easier to embed trees managed by different React versions and help React interoperate with other technologies.
Event pooling
React 17 also removed event pooling. In React 16 and earlier, event fields could be nulled after an event handler ran; developers sometimes worked around that behavior by calling e.persist() or reading needed values earlier. These are details of the 2020 release. The newsletter is not, by itself, a current upgrade guide: developers considering an upgrade should check current React documentation and the version their project actually uses.
The IBM 5150 as a history sidebar
The issue’s “This week in history” item looked back at the IBM 5150, which Bytes said IBM had released 39 years earlier. It characterized the machine as the first desktop computer called a “PC” to achieve mainstream traction and listed a 4.77 MHz working speed, 16 KB of RAM, dual 160 KB disk drives and a cassette port. Bytes gave its price as $1,565, or $4,440 in 2020 dollars. Those specifications and price are figures as reported in the newsletter, not independently verified here against IBM archival records. The 5150 is a historical aside, not a purchase recommendation.
What else was in Bytes #9
Beyond its Rome and React coverage, the issue included a React code puzzle and a collection of developer links. Taken together, those items make the newsletter a brief mix of toolchain news, release context, a computing-history note and learning or reading material—not a standalone tutorial or a detailed product comparison.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
