Marvin Hagemeister

At a certain scale, the characteristics of software development change.

In a traditional DDoS attack, a server is flooded with so many requests that it can no longer respond to legitimate ones.

Over the winter holidays curiosity got the better of me and I spent a lot of time reading up on how modern compilers achieve interactivity in the days of LSPs and tight editor integrations.

It's funny, sometimes I feel like I'm living in two different programming worlds.

Lately, my mind has been occupied with finding ways to make tools simpler to work with.

Whilst dabbling with the Preact repo I noticed that running npm install takes more than 3s.

Over the past year (2024) there has been a strong movement to rewrite JavaScript tools in Rust to make them faster.

If you've visited Node's homepage at some point in your life you have probably seen this snippet: js import { createServer } from "node:http"; const server = createServer((req, res) => { res.writeHead(200, { "Content-Type": "text/plain" }); res.end("He…

Unbeknownst to many, the new isolatedDeclaration feature shipped in TypeScript 5.5 is much more important than you might realize.

In the realm of web development, the efficiency of server-side rendering HTML plays a crucial role in delivering fast and responsive user experiences.

Admittedly, I currently don’t have a bigger project written with Tailwind CSS at hand at the moment.

Let's imagine you are working on a big project with many files.

In the previous posts we looked at runtime performance and I thought it would be fun to look at node modules install time instead.

If you've been writing command line tools for other developers to use, there will come a time where the clarity of the output can be enhanced through colors.

I received a very interesting issue via email from Josh Goldberg regarding a website that froze for about 2-3s.

If you’re working with JavaScript you’ve likely used the "scripts" field in package.json to set up common tasks for your project.

We've talked quite a bit about linting in the past two posts of this series, so I thought it's time to give eslint the proper limelight it deserves.

In part 1 of this series we found a few ways to speed various libraries used in JavaScript tools.

Whilst the trend is seemingly to rewrite every JavaScript build tool in other languages such as Rust or Go, the current JavaScript-based tools could be a lot faster.

Recently, I tweeted that the whole test suite for Preact, a modern framework to build web apps, runs in approximately 1s.

A common rite of passage for every frontend framework is to compare the execution speed with the established players.

About a week ago, I spent time looking at web components, specifically how we can ease converting Preact components.

So today I spent a few hours going through various GitHub repos to see how the Portal component in various virtual-dom Frameworks is used (and abused?)

When Manu from the Stencil team pinged me on Twitter regarding a code golfing challenge, I just couldn't resist!

A little bit of time has past since the announcement that we are working on our very own devtools extension.

As many of you know the react team released a revamped devtools extension recently.

It's been a while now that the hooks concept took over the frontend world by storm.

One thing we're known for over at Preact is making code a lot smaller than it originally was.

Someone in our Preact Slack channel (join here) was running into an issue where the page would be blank as soon as the page loaded.

What's the difference between preact and preact/compat?

I though I'd start the blog with something special that not many Preact users may know about.