If you plan on making money off of your software, dual license AGPL and commercial. True open source developers can benefit from your work for free and contribute, while clients that would rather not have GPL can pay you.

The reason for AGPL is to prevent people taking your GPL code, changing it, hosting it as SaaS, and never disclosing their changes as technically they’re not distributing the software.

Also, your non core business libraries are the most prime candidates for GPL/AGPL. You want to benefit from community contributions to those, not bear the full cost of development and give it away for free without getting anything in return.

She spent 11 days detained.

“I was put in a cell, and I had to sleep on a mat with no blanket, no pillow, with an aluminum foil wrapped over my body like a dead body for two and a half days,” […] “I have never in my life seen anything so inhumane.” She went on to describe one incident when she and 30 other women were moved in the middle of the night to a facility in Arizona. During the ordeal, she was forced to be “up for 24 hours wrapped in chains.”

From CBC.CA (Eagles is her mother’s surname):

Eagles said the detainees at the San Luis facility have no sleeping mats or blankets or windows, and the lights are on all day and night.

An organization pivoting hard on their entire software stack because someone didn’t like a word in a message somewhere… someone powerful in there didn’t arrive by competence alone.

Considering there’s no incentive for a developer donating their work for free to add thin-skinned users to the masses demanding features and fixes, I can’t say I disavow them. Anyone can just fork their project to change the name, and handle the hassle.

If such a thing would happen, all you need to do is fork the previous, copyleft, version of the code and go on with life as if nothing happened. That’s an economic disincentive for maintainers to try such shenanigans.

I never quite understood the massive hard-on programmers have for splitting hairs.

I can see exactly one use case: context-aware OCR of code.

Late 80s. Little kid me got picked up from school but dad still had work to do, so I join him at work. He notices I’m bored. Sits me in front of a terminal to their Unix mainframe, opens up Pico. I type in stuff there, happy as a clam. Good times.

OnlyOffice is certainly more mature as a hosted app. It was born like this, the desktop version was the port. LibreOffice Online is still beta, I think.

So if your interest is in hosting and online editing, OnlyOffice. Also has an interface that’s very similar to MS Office 365, which can be a pro or con to some. LibreOffice has a more traditional toolbar paradigm.

You can try both before string up a server to see what you prefer. They’re both copyleft so no chance of a rug pull.

There’s Servo too. So ladybird can crash and burn for all I care.

So like OnlyOffice and LibreOffice Online?

Edit: to clarify: both of these products can be self hosted. OnlyOffice’s main business model is to sell hosting services, their software is AGPL v3.

I’m not complaining, but why create something from the ground up when they could be improving OnlyOffice or LibreOffice?

Honestly all the highlights are really cool. The non destructive editing is a game changer.

You can sign up for free on most servers. I think tchncs.de has video and audio conferencing enabled if you want to try that out.

Teams is sort of a drag though. Very resource intensive for what it does. But if everyone in your company has ram and CPU to spare, it’s mostly painless.

Pascal is so awful. Damn, I wish it was dead.

In C too*.

*for certain compilers, that is.

Cool, thanks for explaining! I take it they don’t work that well on WINE either?

No they don’t.

It’sa tentative anti AI scrapping measure.

I’m clueless as to why one would want either. Running old hardware peripherals?