Hendrikto

Some sorely needed context:

> [Gforth is] a free, fast, featureful and portable implementation of the Forth 2012 language.

> Gforth runs under GNU, BSD, and similar systems, MS Windows and MacOS X and should not be hard to port to other systems supported by GCC.

That‘s what subsystem maintainers are for.

> not to mention having far better UX

Yeah, it is totally great to have to set up a different account for every service, then having to do AML and KYC, and then having your account suspended for no apparent reason. So great that international transfers takes days and tens of dollars in fees, if they succeed at all. So great how a large part of the world‘s populace is denied access to the global financial system. Great as well how centralized it is, so things go down when there are technical problems at your bank. Absolutely awesome how Canada was able to freeze bank accounts of people who donated to the ”wrong“ cause.

They totally have it figured out, we should stop looking for alternatives. We already have the perfect system for the ages. Anybody who even tries is delusional.

> I was hesitant to write the entire frontend in C, but it wasn't nearly as painful as I imagined.

> All too many times have I:

> * Fought vim to highlight Go's html/template syntax.

> * Fought helix to detect Go templates without breaking html detection.

> * Fought rustrover to recognize jinja templates for a project using askama.

> Using C means there's no second language for your editor to half-detect, no mixed-syntax where highlighting falls apart, no plugin dance to get the two languages to cooperate.

None of that has to do with C. You can apply the exact same approach in Go, or in any other language for that matter.

For those who, like me, had no idea what QGIS was: It is a free Geographic Information System (GIS), which means that it deals with creating, managing, analyzing, storing, and visualizing geospatial information. Think of (3D) maps and stuff like that.

I liked the original, and I welcome the new non-AI section. Great work.

I have always had far fewer problems on rolling release distros. I have an Arch install I had since 2017, and it never broke. Every time I did a dist-upgrade on an LTS distro it caused major problems.

Granted, you have to know what you are doing and not just copy-paste random shell commands from the internet, but if you do, I would argue rolling releases are easier to maintain. You get breaking chances piecemeal as they happen, instead of all at once every two years.

Also, I think this question, posed by the author, is very pertinent:

> At what point does an LTS branch become a continuously rebased downstream fork rather than a stable release?

Just click the link…

> The repo now has ~42% top-line results formalized.

The annual reports are public. You can look up yourself how much money they are squandering each year. Mozilla is actually incredibly well funded. They are just extremely mismanged.

I and a lot of other people would be more than willing to donate to Firefox. But not to Mozilla, who keep throwing money out of the window. Also, the executives kept raising their own salary while market share declined, and while firing developers doing the actual work.

Mozilla is extremely mismanaged.

Another unasked for and fruitless side-project from Mozilla that did nothing but burn money and distract from their core product. Who could have seen it coming?

And for what benefit? 9/10 ”problems“ HR ”solves“ were created by them in the first place. HR is a net negative to society.

It is not at all about race. It is about the lifestyle. And you definitely choose that yourself.