What if, and hear me out on this, the fossilized reefs aren't the same species as today's corals. Having gone extinct, and evolved again...
Convergent evolution: the same type of organism evolving multiple times...
Libreelec, and a NAS.
Me when I confused "secrets" with "trade secrets"
well, then that should also apply to company "secrets" . can't have it both ways.
Or the other way around: I write GPL2+ code, I use AI. It's trained on my GPL2+ code. Now all of your code assisted by AI is derivative.
Good luck sorting this legal mess.
Geeks assemble, spin up an email server, an XMPP server, get your friends on it, and keep the user count under 1000.
you have the knowledge, use it!
Also fight these laws. But that'll be harder.
No, "considering a stake in" isn't seizing means of production, this is forcing the private sector to do their bidding, extracting riches as they go.
Those are very different things.
Seizing means of production looks very different.
you still need to set it all up. Have a server somewhere.
Harder than it sounds.
Or use something decentralized, like bitchat. that has its own can of worms.
> One thing I do know is that France says this year is cooler than the last. https://climatologie.meteocont... [meteocontact.fr]
That is not what this link says, like at all. Read the graphS . Its graphed per month, and your assertion is only valid until march. In april it's way up again.
The seasonal graph, only available for spring, shows an increase for 2025.
No no, you're behind on your playbook. Now you're supposed to ask about the Krasheninnikov eruption.
Oh wait, that might kick in only in a few months.
> some portable cooling system which I feel isn't hard at all to manufacture
Fremen stillsuits! Lets get cracking.
Comes with the year of birth...
Point 1 is way more complicated... Sorting out paths is the easiest, then you need to figure out dynamic linking/import hierarchies, and in the end you will have 2 distros in the same filesystem side by side. That's AppImage/Snap/Flatpak.
The second is a "devops" problem: developer, integrator and distributor should be separate entities. All three would constantly push and pull with different requirements.
Language repositories could be a thing, if they could be integrated directly into distro package managers, with a sane retention policy, and a common set of package sanity tests.
Paludis tried with perl or ruby, but found out that the language repository was using invalid yaml files everywhere, and it only worked because of a bug in the language yaml library.
I really hope for the day when pip can be taken over by portage.
It wouldn't be worse than pip itself (which has no way to specify build time dependencies, as I discovered with sqlalchemy, which failed to update because of an old GCC on the system)
I'd also like cargo to be taken over by portage, but considering rust doesn't do dynamic linking, the only use would be auditing the system.
ie the package manger warning you "firefox is using an old crate", but that breaks once again, because rust's crate dependencies are of specific versions.
In other words: We're creating a completely unmanageable mess...
To be fair, it does have some nice features.
One of my favourites is the while/for
Akregator for me. https://apps.kde.org/akregator...
I just can't work with GNOME UX.
It's great to be smart 'cause then you know stuff.
