It won't last. Remember (when was it? Last year?) when Musk went after Microsoft for turning Open AI into proprietary closed code? We never know what's going on behind closed doors, but something changed, Musk backed off, and nothing changed.

In the first year of Google search, it was possible to find exactly what you were looking for. The engine paid attention to inclusions, exclusions, the whole nine yards. It was a thing of beauty and it was why Google took over from all the other search engines that used to haunt the Internet of the late 1990's and early 2000's. And if what you were looking for didn't exist? You got 0 hits. (Sigh)

...and you could call a friend and say: "insert X into google, click the second result on page 2" - both of you had the same output back then

Let's hope other countries follow suit. Next, let's go after the email spammers! YES!

Wow, that's so much more ambitious than what I'm doing. I'm learning Flet so I can build a multi-headed timer for cooking.

Tobi Lütke also made some rather controversial statements lately, too, agreeing with a retired TD Bank CEO that more votes should be given to the rich. On the surface, this sounds awful, but what Eric Thor actually said was that the number of votes should be tied to the amount of income tax a person pays. Considering that (from what I've heard) billionaires pay no income taxes, I'd say it's not a bad idea. No tax: no vote.

A native Linux application would be preferable, even if it does work with WINE (which I don't know... yet).

Win32 is Linux's only stable ABI.

A fair statement, but a stable ABI is only needed when you don't have the source. Seeing as most of the value proposition of Linux is that having the source is good, I find no fault in an unstable ABI.

Source available is of little use for many of the current breed of languages and libraries. Even standard C support is starting to break down as incompatible "standard" newC is being pushed because some C++ guy didn't like K&R function definitions.

Linux's remarkably stable kernel ABI is the only reason we can still use a lot of unbuildable dependency hell stuff on Docker containers.

> a stable ABI is only needed when you don't have the source

> A stable ABI is only needed when you don't have the source or you don't know enough C to fix incompatibilities with every new version.

There, I fixed it for you.

That is mixing up a stable ABI vs a stable API.

OpenBSD is sort of the poster child here, They notoriously do not have a stable ABI, I would not want to try and ship closed source software on obsd, it would be an absolute nightmare. But their API is very stable (insert counterexample of the recent pledge change here)

An interesting side effect of obsd changing their ABI fairly often is they are good at it(add comment about this is because it is a small self contained system with few users here), in Linux land an ABI change is a nasty, messy, multi year process with much wailing and gnashing of teeth, for obsd, it just happens. To misquote Raul Julia in Streetfighter "For you, the day the ABI changed was the most important day of your life. But for me, it was Tuesday.

It's the compiler too. I recently found out that kernel 6.6 can't be compiled by gcc 15. So, even if you have the source, unless it's extremely simple, at some point the current toolchain will refuse to build it.

Winemaker + winegcc.

This was the first thing that crossed my mind when I read about this port. It's heartening to find out I'm not the only one!

I never thought about it before, but you're right. In the old days (ie. before chat-bots) while writing code, I was usually in an alpha state. This makes so much sense.

Ban cell phones worldwide.

Ban cell phones.