The problem there isn't copyright. It's whoever is demanding students use the latest version.

> Copyright rarely helps small authors who actually need it. > > It usually gets employed by conglomerates that own distribution and are already screwing authors as hard as they think they can get away with.

Do you think these small authors have the resources to try to enforce copyright?

If it's easier to use than jq, they should sell the tool on that.

Yes, NixOS containers can be run in:

* declarative mode, where your guest config is defined within your host config, or

* imperative mode, where your guest NixOS config is defined in a separate file. You can choose to reuse config between host and guest config files, of course.

It sounds like you want imperative containers. Here's the docs: https://nixos.org/manual/nixos/stable/#sec-imperative-contai...

Oh I totally missed that!

I'm less convinced.

To keep and/or increase my current compensation, I have to be competitive in the software development market.

(Whether I need AI to remain competitive is another matter.)

The 16,000 new babies will be competing in different markets.

Oh, and of those 16,000 babies, many are born in far less fortunate circumstances, they're already far behind their cohort. :/

> keep and/or increase my current compensation, I have to be competitive in the software development market

Author’s point is that competitiveness can come in many forms. Having the same AI proficiency as everyone else isn’t differentiating. (And it isn’t table stakes.)

Tech sentiment around 2022 was time was Zuckerberg was a good leader for actually setting a clear direction for his company.

I'm not sure what to conclude from this.

It was? I've always thought he's just someone who will say anything to protect his stock price and... yeah, and that's about it.

Try to imagine a deployment/CI system where that isn't possible. That's what the post is asking.

* Maybe you don't have privileges to delete the database

* Maybe your CI environments are actually high fidelity, and will fail when there is no DB

* Maybe destructive actions require further review

* Maybe your service isn't exposed to the public internet, and exposing to 0.0.0.0/0 isn't a problem.

* Maybe we engineer our systems to have trivial instant undo, and deleting a DB triggers an undo

Our tooling is kind of crappy. There's a lot we can do.

"- buggy Android compatibility and near zero native devs, all jumped ship"

I'm a bit confused by this. Are you saying that the developers who once wrote native Sailfish OS apps are no longer writing those native apps?

Is there any hope for using the responsive libadwaita programs from the Mobile Linux space? I realise this isn't particularly large, but it is active.

> Is there any hope for using the responsive libadwaita programs from the Mobile Linux space?

Currently not, if I understand correctly. There are plans to update or rewrite the Wayland compositor. If all goes well it should support GTK programs and I assume libadwaita too.

If the goal is less AI in militaries, how does having better open source models improve things?

No, he's advising us that we software developers might be coming to an end of a golden age, that if so, resistance is futile, and how to find another.