Minha gente, fiz um site aqui pra visualizar os casos de COVID-19 por munícipio: https://t.co/Kwk3GxBZXR Completamente open source, subindo nos ombros de gigantes como next.js (@zeithq), chakra-ui (do @thesegunadebayo), vx, d3.js entre outros ❤️

Just implemented a feature using GitHub spec-kit. It's an opinionated workflow for coding via an LLM. I used it with Claude Code, but it works with many different LLMs. Wow. It does a LOT. - Creates feature branch - Generates a high-level plan - Creates a quickstart doc for

Agora é oficial: sou Lead Developer Advocate na @meteorjs ☄️ “Mas pera, MeteorJS ainda existe?” Não só existe como tá mais vivo do que nunca! Tem versão nova, comunidade engajada e produtos além do framework. Ansioso pra trabalhar com open source e por tudo que vem aí ❤️

We have an announcement https://t.co/WBG18EsLvG

I couldn't be happier today - we're entering a world without forwardRef ✨

React 19: Never forwardRef again

I often see aria-labels that look like an id: 🚩 aria-label="delete-user-button" An aria-label should have a *user-friendly* label that describes what the button does. And it shouldn't repeat the tag's name - that's redundant. ✅ aria-label="Delete Cory House"

We are introducing a new mode for Blocks called Lift Mode. Enable Lift Mode to "lift" components from a block template for copy and paste i.e you will be able to copy the smaller parts that make up a block template like cards, forms...etc Visit the Blocks page to try it out.

Do you love The Office? I've created a small free-to-play fan game to show some love for the series! Help me by showing this little game to the world!! https://t.co/WWCiDZlKLK

A developer shouldn't merely do what they're told. Why? Because it's not a developer's job to merely follow orders. We're paid to see the gaps. We're paid to collaborate with others. We're paid for our professional judgement. So: We should push back. We should point out

This is actually a good question (quoted below), and I have a good answer for it. I was an iOS native dev from 2012-2015 (Obj-C days) and really, really loved it. Xcode was annoying but I could get around that with various tooling (RubyMotion, cocoapods, etc) that made it so I

Acusação: o podcast Xadrez Verbal é financiado por think tank dos EUA e do MBL Realidade: Padrim, dívida com os ouvintes, muita insistência minha e do Matias e só uns cinco anunciantes em nove anos de podcast Não postem sob efeitos de lisérgicos, jovens

using a <div> as a <button>

PSA: Whenever you think of writing useEffect, the only sane thing is to NOT do it. Instead, go to the react docs and re-read the page about why you don't need an effect. You really don't. But what if I ne.. - NO. read the page! In my specia.. - NO. read the page! READ THE PAGE

A common case of needless state: Dialog visibility. Example: If a dialog displays when I click on a user, I only need one piece of state, not two. And this can be streamlined even further. Here, assume UserDialog only renders when provided a user. UserDialog simply returns

components / hooks / types / utils (and constants) is the split I'm seeing in many codebases, yet it's the one I dislike the most. It groups by type, not by domain. "useTheme" will live next to "useTodo", but not next to ThemeProvider ... why?

You inspired me, @cassidoo. Since hooks and the early conception of the suspense API, I have personally felt that React has been obsessed with just a handful of concepts. While technically impressive and undoubtedly pushing the limits and boundaries of what a single-threaded UI

Please don't name your variables `renderTable` or `showIcon`. It is not helpful to read: { renderTable ? <Table data={data} /> : null } If we should render it, we render it. Thank you, Captain Obvious 🦸 Instead, try to name variables for what they represent:

I work with many teams who use different languages and repos for their web UI and the backend. Example: 1. React UI 2. C# .NET JSON API Problem: It requires tedious and error prone coding and testing to assure the UI works with the JSON API's requests, responses, HTTP status

Why I'm excited about React Server Components (RSC): 1. Smaller JS bundle (Server components add zero K to the bundle) 2. Performance. Fetching starts faster, runs on the server, and the results stream via HTTP streaming. 3. Simple fetching. No useEffect or state! 4. I don't

The key difference between @nextjs and @remix_run: Next is a React framework. Remix is a framework that happens to use React. Next embraces React features early and often. Remix embraces web standards and favors stability and proven web standards. It’s a tradeoff.