Tag: react
Don't pass className to your components
Why className and style props make your life harder, not easier
React Server Components: Do They Really Improve Performance?
Nadia Makarevich has some great numbers from a realistic benchmark. (h/t to Chris Coyier for putting it in my feed.) The whole writeup is worth reading, since it goes in-depth into several data-loading strategies. The summary is excellent:
React Conf 2024. React v19 RC
The first day of React.js Conf just concluded. This much-anticipated conference took place almost 3 years after the previous one. The React updates were just as eagerly awaited. The conference began with these updates and this article will be dedicated to them. And yes, as you saw from the preview — version 19 has moved into the release candidate status. The full release is promised within two weeks.
Caching in next.js. Gift or Curse
The App Router significantly expands the functionality of next.js — partial pre-rendering, templates, parallel and interceptable routes, server components, and much more. However, despite all these improvements, not everyone has decided to switch to the App Router. And there are reasons for that.
More libraries to the library god or how I remade i18n [next.js v14]
There are dozens of amazing libraries made for internationalization, such as i18n, react-intl, next-intl. They all do an excellent job of adding translations to an application or website. Most of them are tested, debugged, and consistently supported.
Streams of AGI
DIY streaming for OpenAI's chat API using ReadableStreams, event parsing, and a custom React hook.
Next.js v13: What's New and What's Coming
Next.js is the largest framework for web application development. It was created six years ago, on October 25, 2016. Since then, 12 major releases have been issued, making the web faster and faster. Despite the framework’s complexity, the size of each subsequent release did not decrease, though the pace of updates did slow down.
Next.js Layout RFC: Changing Everything to Make the Web Faster
In May of this year, Next.js unexpectedly published an RFC (request for comments) on its blog. It primarily discusses a new abstraction - layouts - as well as a host of related changes aimed at speeding up development, improving DX, and standardizing through the creation of new conventions. This working proposal definitely deserves attention, both because of its complexity for the framework and because it literally describes what it will look like in the future.
Theming. Part 2. New Browser APIs. Theming with SSR. Choosing Between SPA, SSR, and SSG.
According to data collected by Android Authority (2,514 respondents) and an analysis by Thomas Steiner, over 80% of users use a dark theme. Of course, it’s hard to call this sample entirely representative, since the surveys were conducted on technical forums, but overall, we can say that a good half of the internet uses a dark theme.
Next.js: Where is it going, where did it come from, and what does Google have to do with it?
It’s been almost two weeks since the Next 11 presentation. Today, I'd like to talk about which technologies soon received comprehensive support, understand who helped implement them, and what goals the company was pursuing.
Thematization: History, Causes, and Implementation
A dark theme for nighttime use isn’t the only reason for adding theming to a website. Another important goal is service accessibility. Worldwide, there are 285 million people with total or partial vision loss; in Russia, there are 218,000, and up to 2.2 billion with various visual impairments