Did you not do code reviews? It's the main thing I would miss. Being able to comment in-line, and manage iterations, is very valuable to me.
is bricking systems really an issue/a common issue for common mutable Linux distros?
… or use them anyway because if they actually don't care for human rights, will they really care for licenses or licensing law in other countries?
Even then I think establishing intent is worth something.
And it may be different for some of the "lesser evil" modules of the license.
they will do it anyway or just not use your library
I think that's still worth something. Not being a part of it, even indirectly is worth something. Not enabling them.
It is not a generic term for source-available software, and never was.
The problem with that reasoning is that precedence and origin do not necessarily define language use after it. Language evolves. Society and communities make up new or change definitions.
Misuse of the term is evidence that it's not universally understood to be one way.
I think it's mainly because "open source" can be understood as accessible, readable source. And many people seem to intuitively understand it as such. The "free" terminology on the other hand has a more ambiguous meaning between freedom and no cost. And early on, the "freeware" terminology was established as a differentiation to "free software". "Open source" does not have such an equivalent established differentiation (like "source-available", which seems to be just not as prevalent, maybe because there have been much fewer products with that alone).
I understand the desire to correct, specifically with the established OSD. But I have to wonder if it will ever bear fruit, given these circumstances. And in consequence, whether it's even worth to point out.
From their FAQ:
Wait, isn’t that just Spore?
While Thrive was originally widely inspired by Spore’s intended concept, we aim to portray a creature’s evolution in a fun and interesting way while remaining scientifically accurate. Evolution will play out on not just your own creature, but those around you, each competing to survive within the simulated environment.
I still hate the "vibe" terminology.
What I would have liked it to mean: While coding, put on some music, and zone out to coding.
What it means now: Prompt an AI to generate working code and solutions.
I don't get where the "vibing" comes in. I guess you don't have to think about the technical details? And that's vibing? Maybe it's just unfamiliarity and lack of practice, but poking the AI via prompting and thinking about how you can influence it better doesn't feel like you could zone in to or "vibe".
Maybe it's about letting go of reasoning and just going for it? Vibing in the sense of going with the flow?
It's not the first terminology I find unfitting. I'm trying to accept that it is what it is, and that it just is what "we collectively" have decided to call it (or ran with).
really cool animations
When will it launch?
I'm not entirely sure yet. I'd love to get it out before the European summer this year.
What if I want it right now?
I'm going to do a pre-order, where you'll get access to the chapters that are already written. You'll get to see each chapter slowly take form as I push out new drafts.
If that's how you draw conclusions… damn
It would have been quite the surprise if they had 6 recommendations but their favorite was not amongst them.
But I guess it’s your fav language so you won’t take any criticism right?
If that's your take I'll just leave it at that.
10
What are the chances of the parent also beginning with seven zeroes?
I suspected author or commit date manipulation. But the commits look entirely like normal commits. So it must be pure chance?
00000003dd63b4c5af111a31269ed8a18d0823fa0000000ae6a4e242e802c943f465373b70b07469
Even just being able to view the source code without cloning is very valuable. A bare repo does not provide that.