> I don't believe in anti-aliasing for a coding font, not even on a retina display

This is a very good point. As resolution increases, antialiased fonts become less ugly, but also less necessary. Thus at no resolution they make any sense; but they look ridiculous for different reasons.

cannot even read this thing. Guess I'm not human enough...

what a strange way to put it... why didn't they just say that they are not using any more taxpayer money to finance your parking space? Land in a city is not "for free".

> It's very easy to call another group entitled if you're not one of them

yeah, well: my point, exactly!

I cycle in Paris every week, and the only annoying experience climate-wise is the extreme heat you can get some days in july and august. If it's cold or wet, you can just wear appropriate clothes and be comfortable. But if it's sunny and 35°C, you are going to be drenched in sweat no matter what! Of course, being in the metro those days is even worse...

why not? the language is straightforward and loops are fast. It is portable and your code will work unchanged for the next 50 years. It may be a bit verbose, but that's not a big deal with today's tooling.

going by your text editor analogy, we are arguing against implementing undo/redo as a "non-destructive delete", based on adding backspace control characters within the text file. I want infinitw undo/redo, but i also want that when I delete a character it is really gone, not hidden!

I'm honestly baffled at your surprise... say, if you crop an image, and 2 seconds later you enlarge it to its original size; do you expect to get the inital image back? Or a uniform color padding around your crop?

Scaling is just cropping in the frequency domain. Behaviour should be the same.

Here's the nice thing about it: they are! If they don't work (for any of the equally exploitative companies in their country) they die.

But this is the basic principle of capitalism. The company exploits workers (in order to obtain a net benefit from their work), and exploits customers (by selling the lowest-quality, most expensive product it can manage to). Companies that don't behave like that get out-competed by companies that do. This dynamic is the root of our economic system, as was very clearly explained by Adam Smith and Karl Marx two centuries ago (in slightly different tones of voice).

The particular case you mention is nothing special. The exact same thing happens for all the products that people buy. This is just the stable state of our (some would say "rotten", some would say "healthy") society.

no, it isn't. The point of the GPL is to grant users of the software four basic freedoms (run, study, modify and redistribute). There's no restriction to distribution per se, other than disallowing the removal of these freedoms to other users.

I have mixed feelings about this... Sometimes I feel young and reckless and want to just output whatever I need without checking $TERM. In practice, all modern terminal emulators are essentially xterm-256color compatible. If something breaks, the worse you get is some funny characters. Is that such a big deal? Much better than propagate the silly termcap/terminfo complexity.

By the way, xterm supports sixels since forever.

These are self-inflicted problems by these apps. Nothing to do with the OS. These apps simply don't work. Complain to the companies that push these broken apps to you.

Would you buy a microwave oven that kills itself if you play the wrong kind of music in your kitchen?

This would make some sort of sense if it was honest. For a start, the owners and shareholders are plainly cost centers (they are literally useless sinks of revenue).

It's like a piano that had the high notes to the left.

"I like this job and would do it for free if I was rich. But I'm not: I'll need to live with this salary. The absolute minimum I require is food and shelter for my family (single dad of 3). Look at the rent of a comfortable 4 bedroom apartment within 10 minutes on foot to the lab, and multiply it by three. That number is the least that I'm able to take. But of course if you pay me more I'll be happier."

But is this "stochastic nature" inherent to the LLM? Can't you make the outputs deterministic by specifying a version of the weights and a seed for the random number generator?

Your vibe coding log (i.e. your source code) may start like this:

    fix weights as of 18-1-2026
    set rng seed to 42

    write a program that prints hello world

This seems to be a great general principle of api design! The best apis are those that are hated by the developer and loved by the end users.