The only software that didn’t break this week...

#Tech Outages #Solid 2.0 #JavaScript Frameworks #Asynchronous Programming #AI Development #Web Development #Programming
💬 Chat with this Video
Ask anything about this video…
It's been a rough week trying to be a 21st century human existing on this planet. Last Thursday, Microsoft 365 went down for almost 24 hours. On Friday, the FAA issued a nationwide ground stop. On Monday, Chase, Bank of America, and US Bank all started having outages while hackers shipped malicious code to 178 orgs, including CNN, Zoom, and Salesforce. Then, just a few days ago, the NSA's classified internal network went offline. To which the president responded, "Things like that happen. It's fine." And then it just kept going. United had to delay hundreds of flights because the web app its pilots used to calculate weight stopped working. Apple pushed an internal update that knocked out iCloud, the app store and the checkout systems in its own retail stores. But by Tuesday afternoon, people were so rattled that 911 itself started trending on down detector. And on Wednesday, we found out that almost every engine X server on the internet had a vulnerability since 2015 that lets anyone run code on it. So, in today's video, we'll ignore all of that and go old school by looking at a piece of software that actually got tested before it shipped, but find out how it makes loading states and race conditions disappear and why its error messages are now written for your agent instead of you. It is November 19th, 2026, and you're watching the code report. On Monday, Ryan Carneato shipped Solid 2.0, which is the framework's first major release in over 5 years. If you've never used it, it's essentially React: The Good Parts. It comes with components and JSX, but how it works under the hood is completely different. A component function runs exactly once, and when a value changes, only the specific DOM node that depends on it gets updated, so you don't have to think about when your app will rerender. The thing that makes that possible is called a signal. And when solid 1.0 came out in 2021 and popularized it, React developers laughed at it. Then signals started showing up in Angular, spelt with runes, in view with vapor mode, and even in a TC39 proposal that wanted to put them directly into JavaScript. So with everyone stealing his whole flow, Ryan needed 2.0 to be even better. And so he went back to the drawing board, and what he came up with was a way to make async data behave like any other signal. In Solid 1, signals were synchronous, which meant anything that came from a server needed its own special primitive, which you'd have to wrap in suspense, then sprinkle with transitions. But in 2.0, know a computation can just return a promise is so you fetch your data inside a regular memo and then read the result in JSX like any other value and because solid knows that value isn't ready yet everything that depends on it just waits that might sound like a small change but it really pays off when async values depend on each other like if you had a drop down of preferences where the attributes get fetched based on what's selected normally that means a ton of loading flags and a race condition you find out about in production when a donkey who selects he's just here for hay gets asked whether he's a top upper bottom. But in Solid 2.0, it's just a few lines of code and the framework handles the loading and the cancellation for you. And once he got that working, Ryan did something that framework authors almost never do and started deleting his darlings, including the function that everybody used to fetch data in Solid 1, along with six others that only existed to work around the old model. Then he went after Solid Start, which if you're not familiar, is Solid's official meta framework, which introduced the world to server functions back in 2022, a full year before React shipped its own version. In 2.0, know those server functions moved into solid itself which didn't leave much left for solid start to do. So Ryan did the valiant thing and killed it. His reasoning is that React never shipped the building blocks for state async or the server is so its ecosystem splintered into a thousand competing opinions. And since solid now ships those itself, you can just use Solid and bring whatever router you want. Of course, all that deleting means if you have an app built in Solid 1 that you and Claude are about to spend some quality time together. And the most interesting thing about 2.0 know is that it was built with this in mind since only the pure of heart write code by hand anymore. Now, whenever Solid runs into an error, it'll give you an error code, the exact location, a fix, and a path to a skill.md file that tells your agent exactly how to fix it. And because Solid tracks exactly what state gets read and what's about to update, it can also catch things like request waterfalls and badly implemented effect loops before they ever wreck prod. The 2.0 beta landed back in March and then from there it still took 23 release candidates, 971 PRs and 750 closed issues to get there with some of the last bug reports coming from agents hammering edge cases in the scheduler. Even then, the team refused to call it stable until a full week went by without a single regression, which from what I can tell is more than Microsoft, Apple, Java, Engine X, and even the NSA can say. Yes, React still has jobs and libraries, but Solid's a solid take on the future of app development. And assuming MPM is still up by the time you watch this, you should give Solid 2.0 a try. Or better yet, make your agents try it while you supervise, which you can do with Jet Brains, the sponsor of today's video. Now that I've finally been promoted from lowly developer to engineering manager, the hardest part of my job is supervising all my agents and reviewing their code. That's why I'm excited to see that Jet Brains Air ships inside every Jet Brains IDE where you can run the agents you already pay for like Claude Code, Codeex, C-Pilot, Juny, and more side by side. that they also access the IDE's tools to run tests, check inspections, and use the debugger instead of just guessing. Then I can step through their changes in the review panel and leave a code note on any line that looks sketchy, which gets sent straight back to the agent. To try everything Air can do, every Jet Brains account comes with a free baseline coding model called Juny Light for simple repetitive tasks. Or you can switch off Air completely in the plug-in settings if you'd rather write artisal code by hand. Update your IDE to 2026.3 and try Jet Brains Air today at the link below. This has been the code report. Thanks for watching and I will see you in the next one.

Generated algorithmically for Search Engine Indexing.

Summarize Another Video