today's howtos

posted by Roy Schestowitz on Dec 28, 2025

• ID Root ☛ How To Install Yarn on Debian 13

  Yarn has emerged as one of the most popular JavaScript package managers, offering developers a faster, more reliable alternative to npm. If you’re running Debian 13 and need to manage JavaScript dependencies efficiently, installing Yarn is an essential step in setting up your development environment.

• linuxcapable

  • Linux Capable ☛ How to Install Kodi on Ubuntu

  • Linux Capable ☛ How to Install UrBackup on Ubuntu

  • Linux Capable ☛ How to Install Exaile on Ubuntu

  • Linux Capable ☛ How to Install LightZone on Ubuntu

• Justin Duke ☛ mise hooks

  I am not a fan of injecting scripts into things that you want to be as fast as humanly possible, but here's one exception: I use the enter hook to print a little welcome message when I cd into a project: [...]

• Fernando Borretti ☛ 1Password Dependency Breaks Syntax Highlighting

  Why write about this? Because 1Password is a security critical product, and they are apparently pulling random JavaScript dependencies and unwittingly running them in the tab context, where the code has access to everything. This is no good. I don’t need to explain how bad a supply-chain attack on the 1Password browser extension would be.

• Eliseo Martelli ☛ Reverse Engineering the Cinema: Bypassing "Seat Adjacency" Rules with DevTools

  We have all been there: you navigate to the cinema’s booking site, find that perfect row in the center of the theater, and click to select your seats.

  But instead of confirming, the website throws an error: "You cannot leave a single seat empty" or "Please select adjacent seats."

• Coyote ☛ You Can Make A Website

  If you have any doubts, then you're the target audience of this guide. Many people hesitate or even write off the possibility of making a website due to common misconceptions, poorly-written instructions, or simply feeling unsure where to start. So to help you over those hurdles, this guide is designed to address some of those misconceptions, walk you through resolving certain mental blocks, and present you with some tutorials to help get you on your way.

  The first misconception to address is the idea that you don't already have what it takes to begin. Many people hesitate because they think in order to make a website, you need to spend money (you don't) or that you need to engage in advanced computer wizardry that a normal person could never possibly understand (this isn't true either). There are only a few things you truly need: [...]

• Amit Patel ☛ Goodbye SASS

  A few years ago I had switched variables and calculations from SASS to CSS, but I still needed SASS for nesting. Since CSS nesting has now been supported for two years, I decided it should be safe for me to use it. And that means I no longer need SASS.

  I divided the CSS into eight files that I can simply concatenate together (using cat), then esbuild to minify the result: [...]

• Manuel Matuzović ☛ Class names for content not design

  Due to the use of frameworks, a lot of sites nowadays have become a div and class soup that makes the HTML code unreadable and hard to troubleshoot. Developers who never learnt to code HTML from scratch lack the basic understanding of a solid HTML layout with good class names.

• Manuel Matuzović ☛ Replacing JS with just HTML - HTMHell

  For many years now, JavaScript has been the workhorse of the web. If you wanted to do something that couldn't be done with just HTML and CSS, you could usually find a way to do it with JS. And that is great! JS has helped push user experiences forward, and honestly helped push HTML and CSS forward!

  But as time marches on, and the HTML and CSS methods gain traction, we need to start replacing the old JS methods that feel so comfy with new methods that require less JS.

  Nothing against JS, but it has better things to do than setup and manage your accordions or offscreen navigation menus... Plus, JS needs to be downloaded, decompressed, evaluated, processed, and then often consumes memory to monitor and maintain features. If we can hand-off any JS functionality to native HTML or CSS, then users can download less stuff, and the remaining JS can pay attention to more important tasks that HTML and CSS can't handle (yet).

  Below are a few examples; any you care to add?

• Manuel Matuzović ☛ HTML Input Validation is (maybe) Good

  I think of client-side validation as a progressive enhancement for your users. You have to validate user input on the server (you can't trust what comes from the client), but some validation on the client makes for a nice UX. But that doesn't have to mean lots of JS code or using some validation library on your client. You can get pretty far with the browser's built-in HTML input validation. And then you can layer a little bit of JS on top of that to make it even better.

• Salih Muhammed ☛ Opening this PNG in Chrome shows a different image than in Safari or any desktop app

  If you are using Firefox or a Chromium browser (for me Google Chrome 143.0.7499.170), it's very likely that you are seeing a very foggy version of the painting, however, if you download the image and open it with your default image viewer (or open it in the Safari browser), you will see the image normally.

  My website contains some of these artworks, you're probably looking at one now on the right side of the page if you are reading from a desktop browser, I sent one of the pages to my friend and he told me that the image looks foggy, and I spent hours debugging a nasty edge case in how browsers handle PNG color profiles.