2024-03-25-Inspirations

Back in 2008, most people thought of JavaScript as just a client-side language. But when Google's V8 appeared, young developer Ryan Dahl made the connection between non-blocking servers, V8, and JavaScript. It was by combining these key elements that he was able to create the now hugely popular Node.js. (...) What young Ryan Dahl probably didn't expect was how much forking drama would follow.

All I would say is finding the lowest-tech solution and leaning into browser capabilities as much as possible is a good way to build something resilient and reliable. Also avoiding doing as much client-side rendering (and re-rendering) as possible usually makes things better for everyone too.

There are a lot of CSS units available at the moment and we mostly still rely on pixels and (r)ems for our sizing and fonts. I say it’s time to do a little freshening up. Instead of writing a list of which units are available in CSS that you can easily find on MDN as well, I thought I’d give some examples of where they could come in handy. I will create a mini-series out of this and for the first part, let’s start off with relative length units based on font.

What features am I using almost daily or don’t want to miss anymore? Here’s a quick list ...

Recognizing and avoiding these mistakes will help you write CSS that: Works across devices—not just your laptop, works the first time you try it, makes you less frustrated with CSS

I figured a blog post exploring the mechanics of functions, promises, and the event loop would be fun.

In this interactive guide, we'll explore why, when, and how React renders.

This article discusses some super useful (and possibly less well known) features added to JavaScript in the last 5 years.