I know I do.
GPL forces mega corps to give back when they use community code.
MIT just lets companies take community code without giving anything back.
GPL code is code for the community by the community. Meta crops can use the code too but they have to give back.
Choosing MIT over GPL, LGPL, or MPL (all community oriented) in my book is pretty close to corporate bootlicking.
It might be my lemmy client but when I go to that link I just see a basic steam next fest post with a Linux picking section from a different user.
What am I missing?
If you don’t mind me asking, why did you choose Zorin? How do you hear about Zorin?
Why would you choose the crypto bro ad company browser out of all the chrome spinoffs?
Why not use any of the others?
Will probably make the price go up. The whole reason why they do this crap is to get more money out of the consumer.
Strong recommend for learning the swipe motions. It takes a few min to learn but it’s free real-estate after that. And it’s faster. At least for me.
And the easy retort to that is that they don’t apply Chinese censorship globally. Only in China. Regional laws only apply regionally.
Bro. This is the fediverse. Don’t crap where you (we) live.
You can if you want to. But I don’t think that is best practice. The idea of quadlets is the bring Linux norms to containers. You contain and manage all permissions for that container in that user.
I personally have completely separated users and selinux mls contexts for each container group (formerly docker compose file) and I manage them thusly. It’s more annoying but it substantially more secure.
This being said I think you can do it as root. I think this might work but I am not certain sudo systemctl --user -M theuser@ status myunit.service
Are you placing your service files in ~/.config/containers/systemd of the home dir of the user you want them to run as?
Here is a link: https://linuxconfig.org/how-to-run-podman-containers-under-systemd-with-quadlet
Not true. I run them rootless on my server as we speak. :)
Hot take. Under semantic versioning everything after vista has been in essence a new version of vista.
Going from NT 5.x to 6.x was a major jump.
The reason why Vista had no/terrible drivers was because they went from an insecure one driver bug crashed the whole system model to more secure isolated drivers that don’t crash the whole system model. Developers had to learn how to write new drivers and none of the XP drivers worked.
They went from a single user OS with a multi user skin on top, to a full role based access control user system.
They went from global admin/non-admin permissions to scoped UAC permissions for apps.
Remember on Vista when apps constantly had that “asking for permissions” popup? That was the apps not using the 6.x UAC APIs.
Given the underlying architectural situation everything since Vista has been vista with polish added (or removed depending on how you look at it)
Things will go beyond vista when a new major release with new mandatory APIs shows up.
Yah but your user name is “LanguageIsCool” and you talk about the fun levels of various types of punctuation. You are definitely the outlier here. A cool outlier but an outlier none the less.
Ok. You can physically type them I concede, but normal humans don’t use them. Still a sign.
I would bet that the amount of non proof writers that uses em dashes goes up just because people see that it’s associated with ai and want to be funny.
I mean most people are going to use their phones to write messages and given you can’t physically type an em dash it would be normal to be suspicious if you see one.
Edit: turns out you can physically type them. Still, given that it’s not normal to use them it’s a sign in my book.
I mean it could be Mutex, or Rwlock or anything atomic. It’s just when I have to put stuff into an Arc<> to pass around I know trouble is coming.
You’ll be fine. You will learn the lifetime stuff and all will work out. It’s not that bad to be honest.
I mean yah. That’s what it takes. But like when I try to write code around Arc<_> the performance just tanks in highly concurrent work. Maybe it’s an OOP rust skill issue on my end. Lol.
Avoiding this leads, for me at least, to happiness and fearless, performant, concurrent work.
I’m not a huge fan of go-lang but I think they got it right with the don’t communicate by sharing memory thing.
Companies are allowed to participate in the community. They are wallowed to use community code. Companies donating servers and resources is actually a good thing. This includes Valve. The “greediness” you talk about isn’t a factor.
Also factually none of those projects you listed were started by IBM. Half of them were started by GNU foundation. The other half were started by Redhat before it was acquired by IBM.
The way Redhat made money was by taking community code and packaging it with support guarantees for other companies. Redhat took that money and hired people to further improve that community code they were packaging. I was at Redhat at the time.
Regarding freeBSD you are forgetting the literal largest user of BSD in the world. Netflix voluntarily gives back code to the community but they aren’t forced to.
Sony is the largest user of FreeBSD in the world. They take the code. Use it improve it and give nothing back. From the PS3 forward all of their devices are based on FreeBSD.
Microsoft also is a large user of FreeBSD in a way. When they couldn’t add a proper networking stack to Windows without everything crashing all the time they’re turned to FreeBSD. Microsoft ripped out the networking code and glued it into Windows 2000. From there we got XP, Vista, 7, 8, 10, and now 11. All with community code taken and used to fight community coded operating systems.
I guess it all comes down to how you see companies. If you believe that companies will always act in the interest of the community even at the expense of competitiveness I can see how one might see MIT or BSD licenses as adequate.
GPL, LGPL, and MPL on the other hand force companies to give back when they take.
I don’t trust companies enough to use MIT. I choose GPL, LGPL, and MPL.
If a company intended to give back to the community there is no reason why they would not use GPL, LGPL, or MPL. They intend to tie back anyways. Right? MIT just lets them keep their taking but not giving options open.