Tom Preston-Werner (co-founder of GitHub, board member at Netlify) joins the party and brings his new, opinionated, full-stack, serverless web app framework with him. Will Redwood help usher in the future Tom predicted back in 2018? We discuss that and a whole lot more on this must-listen episode.
Want great developer experience and easy scaling? Redwood is here! Built on React, GraphQL, and Prisma, Redwood works with the components and development workflow you love, but with simple conventions and helpers to make your experience even better.
Supports too many languages to list here, but all of the usual suspects are there. Maybe you’re hoping for a web-based demo? No 🎲
Do not run the Web UI on a port open to public traffic! Doing so would allow remote code execution on your machine.
This looks like an excellent read for anyone looking to level up their fullstack JS chops:
I do React consulting and this is a showcase product I’ve built in my spare time. It’s a very good example of modern, real-world React codebase.
There are many showcase/example React projects out there but most of them are way too simple. I like to think that this codebase contains enough complexity to offer valuable insights to React developers of all skill levels while still being relatively easy to understand.
This is a super-cool tool for getting your ideas on “paper” quickly. It’s pretty rough around the edges, but that’s forgivable for now since it’s pretty new. Try it for yourself right here.
A nice side-by-side comparison of a simple todo app built with both frameworks. If you’ve experimented with these tools, you’ll probably find this article too elementary to be useful, but if either is unfamiliar to you, definitely give it a read.
KBall connects with Katie Sylor-Miller to talk about migrating OhShitGit to the JAMStack, migrating legacy codebases to modern front-end technologies, and design systems.
Blocks UI is in alpha, but definitely impressive already. You drag/drop components, tweak their properties/style, and it spits out “production-ready” React code. Try the demo right here.
We are going to rewrite React from scratch. Step by step. Following the architecture from the real React code but without all the optimizations and non-essential features.
If you think you’ve seen this before, look again. This post is based on React 16.8, which means it uses hooks and drops all the code related to classes.
I do love the hand-drawn style for charts like these. It almost feels like you worked harder on them for some reason.
Make your site editable in five minutes.
Every day, the moat around React gets bigger, deeper, and filled with more 🐊🐊s
I’ve been a big fan of Segment since way back before they became our sponsors. The adapter pattern for marketing/analytics tools is a great idea and they’ve executed on it very well. I’m also a big fan of open source alternatives to commercial products. 😀
If the “Why Rudder?” section of the README (privacy & security, processing flexibility, unlimited events) has you nodding in agreement, this is worth a deeper look.
Words cannot describe how much I adore the thought that building this extremely ambitious piece of software was a better alternative to the tedious process of installing the game. 😆
The fastest wiki and knowledge base for growing teams. Beautiful, feature rich, markdown compatible and open source.
Run Outline yourself for free or pay for the hosted version.
Fascinating look behind the scenes at both the process of rewriting a massively used application and the particular architectural choices made along the way. The approach used was at once incremental and all-encompassing, rewriting a piece at a time into a gradually growing “modern” section of the application that utilized React and Redux. And the results? 50% reduction of memory use and 33% improvement in load time… not too shabby.
Good news fellow Slack users, your productivity just got bumped by the perf gods of Slack thanks to their continued efforts and focus on the desktop app’s performance.
Slack is unveiling a new version of its desktop app for Windows and macOS today that promises big performance improvements. Slack has rebuilt its desktop app to focus on speed, and the company claims Slack will now launch 33 percent faster than before. The Slack app will even use 50 percent less RAM than before, according to the company.
Slack has been working on this overhaul for two years, slowly modernizing parts of its code along the way. While the desktop apps still run on Electron, all of the UI parts have been rebuilt using React to fix some of the shortcomings of the existing Slack app.
Works out of the box with Angular, React, and Vue.
KBall catches up with Florian Rival about bring a C++ based game engine to the web by compiling to WebAssembly and creating a React-based frontend.
This looks like a nice way to help make web components easier to use. If you want to see it in action, Chris Coyier has a solid write-up over on CSS-Tricks.
Our friends at Gatsby just announced the stable release of Gatsby themes.
Chris Biscardi writes on the Gastby blog:
Using a Gatsby theme, all of your default configuration (shared functionality, data sourcing, design) is abstracted out of your site, and into an installable package.
This means that the configuration and functionality isn’t directly written into your project, but rather versioned, centrally managed, and installed as a dependency. You can seamlessly update a theme, compose themes together, and even swap out one compatible theme for another.
What does “stable” mean?
The core theme APIs have been stable for a long time under the
gatsby-config.js. Since they’re being used in production by a number of different companies to great effect, we’re promoting these APIs, specifically composition and shadowing, to stable within Gatsby core so that people can take advantage of them with confidence.
Great description of how the Hooks API leads us from an imperative style of implementing side effects (“Do thing x on mount, do thing y on unmount”) to a declarative style of implementing side effects.
Author Sebastian De Deyne puts it this way:
Instead of thinking about when we should apply the side effect, we declare the side effect’s dependencies. This way React knows when it needs to run, update, or clean up.
Fascinating look through at one of the up-coming features in React. The React team keeps innovating and pushing the ecosystem forward. In this case, by creating a beautifully simple declarative approach to handling with variable network times and asynchronicity.