Go's `http.ResponseWriter` writes directly to the socket, which can lead to subtle bugs like forgetting to set a status code or accidentally modifying headers too late. In this article I explain how to write your own defensive ResponseWriter.
System colors are a way for the OS, the browser, or the users to provide some colors to your CSS. This is a great opportunity for accessibility, as the colors will also reflect users preferences on high contrast colors.
Consistency is achieved through conventions. Conventions are an investment that let's use save time by not having to take the same decision over and over again.
“For fuck sake, another fucking JS framework??”. I can read your mind! Bear
with me though, I want to give a peek at what Astro has to offer and why Hugo
(or other static site generators) feels obsolete to me. 
 I really wanted to start writing again, I'm currently reading
 On Writing Well 
and it's inspiring. I truly believe that getting better at writing has a
positive…
(a rant about Next.js and Sveltekit) 
 Modern frontend development is basically about: 
 
 Making a good looking UI (i.e. writing css and other javascript tricks to do fancy animations) 
 Fetching data from some API (no matter if you use graphql or plain http requests, you still need to get some data asynchronously) 
 State management across the app (also including caching…