a.k.a don’t fear the terminal

As a (mainly) web developer, I develop software that is mostly running on Linux - whether it’s a virtual machine in the cloud, a docker container, or my NAS under the staircase. So - for me - using any other operating system for development would be an extra hindrance.

To be honest, I like the customisability and freedom that only a Linux distribution can provide, I’m on Linux for more than 20 years, and happy with it. But if you are new, I try to give you a quick overview, why the terminal could be a useful tool.

Now that we are aware of the basic networking concepts, let’s take a deeper look at the main protocol of the web - HTTP.

So, what happens if you enter a URL into the browser’s location bar and press ENTER? A very many things, and eventually a website is loaded and rendered.

Let’s check the networking part!

I’m planning to create a custom web component which lets you easily embed your fragment shaders into any website for a long time. You can find some (mostly abandoned ones) on github, so this is my take on the topic (to abandon it eventually 😉).

It tries to be compatible with https://twigl.app/, supporting geekest mode and MRT as well (but only 300 es).

See details on github.

How do we see colors? How can we “define” them in a generic way? How do we compare them?

Well, this isn’t an easy topic.

Sometimes I have the itch to create something that’s not (just) useful, but pleases the eyes.

I’ve started experimenting with webgl a few years ago, mostly in shadertoy - but most of my experiments aren’t public.

This (fullscreen) is one of my favourites. But of course I’m still not entirely satisfied with it.

A quine is a computer program which takes no input and produces a copy of its own source code as its only output.

This one is not really a quine, but something similar, 1020 bytes of HTML/JS that animates it’s own code. Inspired by the great work of @aemkei.

Click here, to see it in action!

CSS Paint Worklet (Houdini) experiment to generate cellular noise based mesh.

Details on github.

There’s a simple function, which eventually can result in pure chaos:

x_n+1 = r * x_n * (1 - x_n)

WebAuthn uses public key cryptography (asymmetric) instead of passwords or SMS texts for registration, authentication and 2FA.

• Protection against phishing: webauthn signatures changes with the origin, so it won’t work on “similar” webpages (with different domain name).
• Reduced impact of data breaches: it does not really matter if the public key is stolen.
• Invulnerable to password attacks: much harder to crack it by “brute force” than passwords.