QOI is just a format that's easy for a programmer to get their head around.

It's not designed for everyday use and hardware optimization like jpeg-xl is.

You're most likely to see QOI in homebrewed game engines.

stdlib.io is a data process/vis library, not a standard library.

jQuery was a DOM/Utility DX library (and also a compatibility layer before all browsers finally focussed on standards), not a standard library.

Deno people are trying so fucking hard to be relevant. It’s embarrassing. Bringing nothing to the table has been their MO from day 1.

Let's examine that.

Deno has always been:

(parapharing) "Hi, I'm the creator of Node and want to make it better but can't get everyone on board with the changes. So I'm going to create a new JS runtime. Node will need to implement these improvements to keep up or everyone will switch away from node. Either way, developers win."

We know it's been that way since he was a month into Deno's development in his famous talk: 10 Things I Regret About Node.js

Deno [...] Bringing nothing to the table [...]

Have a look through each of those 10 points he brought up, then compare that to node before, and node now. It's pretty clear he gave them the swift kick in the ass to start making those changes. We win. That's clearly a success.

Lol, well I could change it, but it was based on the gif at https://quietkit.com/box-breathing/

I think it's because you're not supposed to expand your lungs so much that they feel like they're going to burst.

But if you scroll to the bottom of the css and look at line 69, you can change transform: scale(90%); to transform: scale(100%); to see if you like it better.

Why would I leave windows if Linux isn’t offering anything better?

Because Linux offers an ad-free experience, whereas Windows offers a free ads experience.

It seemed pretty clear to me that the article states that css is doing it's job and it's actually fonts that are the problem

If you're reaching for yaml, why not use toml?

That doesn't really work when you need two comments at the same level, since they'd both have the same key

I think you're forgetting about the Animation API.

Example: making something flash once to get a user's attention

element.animate( {opacity: [1, 0, 1]}, { duration: 500 } );

Use CSS animations everywhere you can, but if you need to be able to hook into an animation (to dynamically change the speed, cancel something, sync animations together, etc...) you should be using the Animation API.

There's never a need for jQuery.

But why bother with creating a new language

I can just do items.map(item => 〈Item key={item.id} item={item} /〉)

I don't think this is a very good example. You've just said not to use a new language, then used JSX, a new language.

I have yet to be given an example of something a “general” intelligence would be able to do that an LLM can’t do.

Presenting...

Something a general intelligence can do that an LLM can't do:

Play chess: https://www.youtube.com/watch?v=kvTs_nbc8Eg

Why can't it play it? Because LLM's don't have memory, so they can't work with logic. They are the same as the little "next word predictor" in your phone's keyboard. It just says what it thinks is the most probable next word based on previous words, it's not actually thinking or understanding anything. So instead, we get moves that don't make sense or are completely invalid.

I'm curious why people would downvote a request for port forwarding?

first major release under daddy Microsoft, so things may be different

I wouldn't hold my breath:

1. Bethesda's management have always unvalued spending effort on engine development
2. Microsoft's awful mandated top-down rules are what seriously messed up Halo Infinite:

• To go into this point in more detail:
  • 343 industries hired a large amount of "temporary" contractors to work on Halo Infinite (this is standard in AAA games)
  • For legal reasons, any contractor who had worked on a project for 18 months is given workers protections
  • Microsoft mandated that each contractor be "let go" right before reaching this 18 month time-frame.
  • During the regular process of development, different developers would build different things, then over time either help out with any questions on how to use it, or tweak it to support a new use case.
  • During Microsoft's mandated development, the developer who built a tool or best knew how it worked was let go. Since it's easier to write new code rather than read existing code unassisted the developer who needs something done before a deadline has to build a new tool. After 5 years we now have 40 something tools that are all built based on different assumptions that keep overwriting each other's results in wildly expected way. No one knows how anything works anymore.