I mean, it is probably not a bad idea to take a look at one of the most well-loved DEs for ideas.. and Gnome did take only good things from it and my subjective opinion is that they have a proper vision taking many of the good things from OSX.
kaba0
joined 2 years ago
You are free to fork it at anytime. I really can’t hate them for having a cohesive vision they plan on developing.
Is there any desktop OS that open apps instantly? Because I have never seen any, my phone definitely beats any of them.
I like and use it each day. Now who wins?
Security doesn’t work like that and I find it important to share the insecure nature of most linux distros with many people, hopefully to make it improve one day.
Currently a make install can do literally anything to your computer besides installing a video card driver (as per the old xkcd comic) and sure there is firejail.. but let’s be honest, how often do you use it? Defaults matter, and thus linux is insecure.
Also, again, how is osx locked down? What’s a concrete thing you can’t do on it?
Package management is the ultimate problem that was previously left unsolved (no, docker just pushes the problem away, doesn’t solve it. That apt install won’t be the same now as it was when you wrote it). Nix is the first thing that actually solves it properly.
Arguably: docker sucks.
They are both UNIXes, that’s quite a lot of similarity and I wouldn’t write it off that fast.
In what way does it limit your freedom? When I first tried OSX I was quite surprised at how customizable it actually is, contrary to all the talk I heard about it.
Macs are actually secure. Not as much as ios, but compared to the general linux userspace, it is like a military establishment vs a homeless tent.
I believe we should have a new word that differentiates between ultra-basic tiny unit tests, and bigger unit tests that are still not integration tests.
E.g. rust and some other newer languages have a way to write basically an inline test for a function — that would constitute my former category. These make sense during development as a reality check. “Yes, this ad hoc stack I need inside this class should have two elements if I push two elems” sort of thing. That implementation may not even be accessible from the outside in case of an OOP language so you can’t even properly test it. Also, these are the ones that should change with the code and removing them is no big deal.
The other kind should work against the public APIs of libs/classes and they should not be rewritten on internal changes at all.
No wayland.