Fake Brian Cox and Richard Fynemen are in abundance.

Imagine 50 years down the road impossible to tell which things Richard Feynman really said in his lectures and which are all made up.

I just blocked a fake Brian Cox one a couple of hours ago. There can be a certain time waste looking at the things before figuring they are rubbish.

Youtube should give you more options than just block or don't show me this. You should be able to click 'AI fake of real person' so they don't get inflicted on others unless they like that stuff.

Unfortunately it's not possible to block a channel on YouTube, or I'd have blocked thousands. All you can do is tell it not to recommend a channel.

Why not use SQLite then as database for package managers? A local copy could be replicated easily with delta fetch.

Could you elaborate on the storage engine and processing pipeline if not confidential?

The authentication account should have a permanent stable identifier that should be the provider's responsibility to issue and manage.

Everything else including email and username should be changeable (provided there's no conflict with other accounts)

> (provided there's no conflict with other accounts)

Couldn't you use this to figure out which emails have registered with Claude?

You can do this on almost every online service by trying to create an account with an email that already has an account.

So essentially - it only works with Latin script? Because without fonts, every other script is NOT going to render.

Agree, the lack of support for TTF fonts is a bummer for most non-english use cases:-/

Echo is really great framework. Blazzing fast and great documentation.

This evangelism around HTMX is bit misplaced.

First - simple use cases sure great. But imagine you have to update some element out of the from tree. Now you need to have OOB swaps and your HTML must contain that fragment.

Not just that your server template code now has to determine if it is HTMX request and only render OOB fragments if so.

Even at decent size app, soon it turns super brittle.

Yet to talk about complicated interfaces. Let's not go complicated just think of variants in an E-commerce admin panel.

3 variants with 5 values each these are 125 SKU rows that must be collapsed group wise.

htmx can do it but it's going to be very very difficult and brittle.

So it is surely very useful but it is NOT the only tool for all use cases.

Charging for the self hosted runners - That's close to flat $90 per month for a machine that you host yourself no matter how small or large the machine is.

Very well written but I can't understand much of this article.

What would be one good primer to be able to comprehend all the design issues raised?

IMO the minimum is to be able to read a “hello world / first triangle” example for any of the modern graphics APIs (OpenGL/WebGL doesn’t count, WebGPU does), and have a general understanding of each step performed (resource creation, pipeline setup, passing data to shaders, draws, synchronization). Also to understand where the pipeline explosion issue comes from.

Bonus points if you then look at CUDA “hello world” and consider that it can do nontrivial work on the same hardware (sans fixed function accelerators) with much less boilerplate (and driver overhead).

To be honest there isn't really one, a lot of these concepts are advanced even for graphics programmers

A working understanding of legacy graphics APIs, GPU hardware, and some knowledge of Vulkan/DirectX 12/CUDA.

I have all of that but DX12 knowledge, and 50% of this article still went over my head.

Gut gemacht!

Danke!