Ricky

@ricky.fm

14269 Followers 917 Following

React core team • Forbes 30 worst over 30

Meme “JACOBS BY MARC JACOBS FOR MARC BY MARC JACOBS IN COLLABORATION WITH MARC JACOBS FOR MARC BY MARC JACOBS”
screenshot of terminal: git status On branch main Your branch is up to date with 'origin/main'. Changes to be committed: (use "git restore --staged <file>..." to unstage) new file: src/content/blog/2025/09/tbd/react-19-2.md
“lots of gas but not much substance”
@ Server Component 'use server' export default async function Use // This runs on the server const user = await fetch /api/ return ( < div> <h1>{user. name}</h1> <p>{user. email}</p> </div>
This optimization requires SlowList to be wrapped in memo. This is because whenever the text changes, React needs to be able to re-render the parent component quickly. During that re-render, deferredText still has its previous value, so SlowList is able to skip re-rendering (its props have not changed). Without memo, it would have to re-render anyway, defeating the point of the optimization.
Screenshot from google "Yes, a materialized view is a type of database cache because it precomputes and physically stores the results of a query, allowing for faster read access compared to a standard, on-demand view. Like a cache, a materialized view stores data to improve performance by reducing the cost of repeated query execution. However, materialized views have a more formal structure, can have indexes built on them, and are typically refreshed on a scheduled or triggered basis, making them a persistent, performance-boosting resource rather than a temporary cache.
What are good alternatives to data fetching in Effects? Hide Details Writing fetch calls inside Effects is a popular way to fetch data, especially in fully client-side apps. This is, however, a very manual approach and it has significant downsides: Effects don’t run on the server. This means that the initial server-rendered HTML will only include a loading state with no data. The client computer will have to download all JavaScript and render your app only to discover that now it needs to load the data. This is not very efficient. Fetching directly in Effects makes it easy to create “network waterfalls”. You render the parent component, it fetches some data, renders the child components, and then they start fetching their data. If the network is not very fast, this is significantly slower than fetching all data in parallel. Fetching directly in Effects usually means you don’t preload or cache data. For example, if the component unmounts and then mounts again, it would have to fetch the data again. It’s not very ergonomic. There’s quite a bit of boilerplate code involved when writing fetch calls in a way that doesn’t suffer from bugs like race conditions. This list of downsides is not specific to React. It applies to fetching data on mount with any library. Like with routing, data fetching is not trivial to do well, so we recommend the following approaches: If you use a framework, use its built-in data fetching mechanism. Modern React frameworks have integrated data fetching mechanisms that are efficient and don’t suffer from the above pitfalls. Otherwise, consider using or building a client-side cache. Popular open source solutions include React Query, useSWR, and React Router 6.4+. You can build your own solution too, in which case you would use Effects under the hood, but add logic for deduplicating requests, caching responses, and avoiding network waterfalls (by preloading data or hoisting data requirements to routes).
React Server Components Server Components are for use in React Server Components. Server Components are a new type of Component that renders ahead of time, before bundling, in an environment separate from your client app or SSR server. This separate environment is the "server" in React Server Components. Server Components can run once at build time on your Cl server, or they can be run for each request using a web server. • Server Components without a Server • Server Components with a Server • Adding interactivity to Server Components • Async components with Server Components
screenshot of a broken reddit home page with a giant blue Reddit logo and a post listed with broken styles. also Ego Nwodim is leaving SNL (according to a post in the screenshot)
Music Clips Events Merch You liked 2 songs • Hot Mulligan
Screenshot of React docs with a note that says: "The Suspense component is activated by suspending. This includes: Reading the value of a Promise with use. Lazy-loading component code with lazy. Data-fetching libraries that suspend, like TanStack Query and Relay. Frameworks that support Server Components, like React Router v7 and Next.js App Router. Suspense does not activate when data is fetched inside an Effect or event handler."
Wat meme
Screenshot of the "new feature" splash image on bluesky that, itself, includes a screenshot of a Jerry post that says "inventing a saturday that immediately follows monday". Below the screenshot is the title "Jerry No" and subtitle "Finally! Get rid of Jerry for good."
Screenshot of the "new feature" splash image on bluesky that, itself, includes a screenshot of a Jerry post (pictured: handsome) that says "inventing a saturday that immediately follows monday". Below the screenshot is the title "Saved Posts" and subtitle "Finally! Keep track of posts that matter to you. Save them to revist anytime."
Screenshot of bluesky: Discover tab This feed is empty! You may need to follow more users or tune your language settings. Button: Find accounts to follow
The user edits each row, which immediately update the item total with no loading state. The total is pending until all of the updates are finished.
The user edits the quantity in each row and the item total and cart total all update instantly without a pending state.
As the user makes edits, the loading states for each row stay pending until the user stops edition and the new total has loaded.
The user is editing the rows, and as they're editing one field the page is updating the result of the other field.