Usually I do my best to blame the network with cause!
Scoopta
joined 2 years ago
Apparently it only impacts officially compiled versions. Guess I'll just stay away from those? I run librewolf anyway and that aside I'm on Linux where officially compiled versions aren't even the norm. Chrome is definitely not my answer
The fact your gnome one has the kde icon in the top left threw me for a loop at first
I wonder how that works on multi-user systems. How do they structure that so that settings are per-user?
macOS applications are folders and that will never stop being weird to me. They basically use the same setup as windows but instead of making the application the executable in the folder they turn the whole folder into the executable
Lol, yeah but React isn't Linux based so doesn't quite end up so cursed. Last time I played with it it was still really squirrelly.
Because it's fun. As someone who is writing a hobbyist kernel(slowly) it isn't about making a functional OS, it's about learning how systems work and suffering while you do it =D.
I wouldn't classify React as a hobby project per-say. I suppose it is but I put hobby OSes in a category of not having a goal to ever be production ready for anyone outside the developers. Tbh react would have way better compat if they focused on win32 over Linux as opposed to developing NT from scratch but the project is also old enough(1998) to be from a time where Linux wasn't what it is today in terms of wide spread hardware support.
Your updated question has given me a rather cursed idea...psychopathic even. Replace the *nix userland with wine...have win32 user space on your Linux. The biggest problem I see with the idea is wine would need a DRM backend so as to not depend on X/Wayland. Ofc the kernel API would still be *nix but your user space would be anything but. There's only so much you can do to get away from a *nix environment when using a *nix kernel.
Define what you mean by non-unix like? Android is Unix like, it hides it from the user but the NDK is still a Unix like API, all devices have a POSIX shell /system/bin/sh installed which can be accessed via a terminal emulator app or using adb. The filesystem structure is different than most systems but there's still a /dev, /etc, /bin, and /proc. Not to mention one of the most unixy designs being the fork() call which android uses as the basis of all app processes. What I mean is Android has a parent process containing all the basic stuff an app needs called zygote which is then forked to become an app processes when an app is launched and then the rest of the app stuff is loaded into that new process, an exec to fully replace the parent is not done. That's a very unixy design decision that isn't usually available on other systems.
Technically speaking if we're going by the hides it from the user perspective then the steam deck qualifies to the same extent. It's hidden until a power user doesn't want it to be
I definitely think this was a good move. Proprietary video codecs are silly and I'm glad VP9 and AV1 have been so widely adopted. I do wish more services used them instead of h.264 but at least it's something.
The thing about the kernel in particular is it's already mostly about money. With very few exceptions most maintainers are employed by someone, even just the Linux foundation, to work on the kernel full time. There's very little community involvement outside of the random patches here and there that community members submit. I think what OP is getting at is it would be nice if there was a community sponsored maintainer so it wasn't all just corporate employees but that likely means providing financial compensation.
I didn't really pay any attention to him until he started becoming mainstream...and I will say the disappointment has been annoying.
Hmmm, this is a really interesting article. I always make it a habit that every time I have multiple threads accessing a data structure I use the Collections.synchronized methods to create the structure so as to avoid race conditions. This just gives me another data point as to why that's a good idea.