Oh yeah and a clean way for expressions to compose statements.

I still wish for extending classes with interfaces and a Nothing type. I think the AVX 10.2 in dotnet 10 is very welcome.

Some good stuff in there as well. Tail call in comp expressions is to have.

still can drink it inside.

Perhaps US decided to tax the entire world?

I got another one I know has been used successfully(??) in the past. Take candidate to lunch. If they eat the lunch quickly => hire. If they eat slowly and likes to chat => reject.

Too hard. Just look at the candidates posture. Lean-forward => hire, lean-backwards => reject (I have talked to people claiming this is a good signal).

Immediate like IMGUI? That programming model should get more love.

A console fragment shader is probably something like the character state/token in and the coordinate of it and then the new character state/token out.

I have used similar techniques to fragment shaders when doing console effects. As there are a lot less pixels on the screen the CPU is probably enough. A fragment shader effect is basically cell coordinate in, color out and then some global state passed in.

I normalize thrice sometimes!

My joke fell flat.

What about the sixel performance?

Nah make it go higher!

I am hoping for a "classic" trend to come. Windows Classic - Without AI. Visual Studio Code Classic - Without copilot and so on

nightmare fuel....

When they describe future dev like micromanaging 10 agents doing different tasks it just sounds like nightmare to me. And I already getting annoyed with devs talking to themselves to solve problem (this is a me problem I realize) so if everybody is sitting talking I would go nuts.

This time I managed to join the twitch chat in time.