https://developers.google.com/ml-kit/

You all realize pretty soon no human is going to update an existing code-base?

Who wants to spend their time understanding 10 year old legacy code? They’ll just feed it into an AI and tell it to add or fix a feature, then generate tests, and file a PR.

If it ends up having an airplane do a loop on take-off or sending your paycheck to Antarctica 🤷🏻‍♂️

• RPN: OR Trick Treat

• Async multithreading: Treat Trick (loop closed) OR (stack trace)

A few jobs ago, everyone hated the tech stack. The people who had come up with it had long left. I talked to everyone, then came up with a plan to transition to a modern stack. Got buy-in from management.

Half the people (and all who had said they hated the status quo) threatened to quit if we made the change.

Fortunately, it was just in time to collect the 1-year retention bonus. Life’s too short. Walked away.

Tried bash, Make, and awk/sed. All hit brick walls. Finally landed on pyinvoke. Two dependencies to install on any new machine. Never had problems. Also, easy to debug and modify as projects evolve.

I just spent the weekend installing 24.04 on a Lenovo laptop as a self-hosted server. The only thing that didn’t work was the fingerprint scanner. No big deal, but it seems peripheral device driver support is still a bit janky.

Running the self-hosted apps under Docker, though, worked without a hitch. chef’s kiss

“It also includes optimized support for Raspberry Pi SBCs to deliver enhanced performance and compatibility.”

Have you looked into the suid bit? You can set it on the file, then change the script owner to root and it runs in elevated mode: https://linuxhandbook.com/suid-sgid-sticky-bit/

Let’s not forget… the reason this type of licensing exists is because large cloud providers were taking a large code base and selling them as services . Often, the main path for the creators to make any money from their code is to offer a paid, managed tier, along with professional services. They would end up competing, and losing, against those cloud providers.

Not saying this kind of license is good or bad, but the reason is often not to stop self-hosting or screw contributors, but to maintain couple of the only pathways FOSS can bring in revenue.

Ignore them. Send a pull request with the full source of Arch Linux.