The diversity of Linux distributions is one of its strengths, but it can also be challenging for app and game development. Where do we need more standards? For example, package management, graphics APIs, or other aspects of the ecosystem? Would such increased standards encourage broader adoption of the Linux ecosystem by developers?
Where app data is stored.
~/.local
~/.config
~/.var
~/.appname
Pick one and stop cluttering my home directory
I have good news and bad news:
A specification already exists. https://specifications.freedesktop.org/basedir-spec/latest/
good luck winning any of these refusers over https://wiki.archlinux.org/title/XDG_Base_Directory#Hardcoded
Yea I like how a lot have moved to using .config but mozilla just moved out of there and now has a .mozilla folder outside of it… wtf… It is insanely sad.
I have actually moved my entire “user home folder”… folders out of there just because it is so ugly and unorganized. I now use /home/user/userfolders/… all my stuff like documents / videos etc in here
it’s pretty bad. steam for example has both
~/.steam and
~/.local/share/Steam
for some reason. I’m just happy I moved to an impermanent setup for my PC, so I don’t need to worry something I temporarily install is going to clutter my home directory with garbagethat .steam is a bunch of symlinks to the .local one… which makes it even worse. they have also .steampid and .steampath.
and even worse a bunch of games are starting to add them there too.
Factorio puts game saves in ~/.factorio for some reason…
damn, of all the people you’d think those guys would actually have used the .local or .config =[
I have 73 dot files in my home directory lmao
This would also be nice for atomic distros, application space and system space could be separated in more cases.
This would be convenient indeed, but I’ve learned to be indifferent about it as long as the manual or readme provides helpful and succinct information.
Rewrite the entire kernel exclusively in rust!
-hehehe-
And that’s how WW3 started…!
There is a separate kernel which is being written entirely in rust from scratch that might interest you. I’m not sure if this is the main one https://github.com/asterinas/asterinas but it is the first one that came up when I searched.
By the tone of your post you might just want to watch the world burn in which case I’d raise an issue in that repo saying “Rewrite in C++ for compatibility with wider variety of CPU archs” ;)
I’m of the opinion that a full rewrite in rust will eventually happen, but they need to be cautious and not risk alienating developers ala windows mobile so right now it’s still done in pieces. I’m also aware that many of the devs who sharpened their teeth on the kernel C code like it as it is, resist all change, and this causes lots of arguments.
I’m not sure whether this should be a “standard”, but we need a Linux Distribution where the user never has to touch the command line. Such a distro would be beneficial and useful to new users, who don’t want to learn about command line commands.
I really don’t understand this. I put a fairly popular Linux distro on my son’s computer and never needed to touch the command line. I update it by command line only because I think it’s easier.
Sure, you may run into driver scenarios or things like that from time to time, but using supported hardware would never present that issue. And Windows has just as many random “gotchas”.
Why do people keep saying this? If you don’t want to use the command line then don’t.
But there is no good reason to say people shouldn’t. It’s always the best way to get across what needs to be done and have the person execute it.
The fedora laptop I have been using for the past year has never needed the command line.
On my desktop I use arch. I use the command line because I know it and it makes sense.
Its sad people see it as a negative when it is really useful. But as of today you can get by without it.
I think there are some that are getting pretty close to this. Like SteamOS (although not a traditional DE) and Mint.
Ubuntu as well. I wish I could say OpenSuse…
While all areas could benefit in terms of stability and ease of development from standadization, the whole system and each area would suffer in terms of creativity. There needs to be a balance. However, if I had to choose one thing, I’d say the package management. At the moment we have deb, rpm, pacman, flatpak, snap (the latter probably should not be considered as the server side is proprietary) and more from some niche distros. This makes is very difficult for small developers to offer their work to all/most users. Otherwise, I think it is a blessing having so many DEs, APIs, etc.
Each monitor should have its own framebuffer device rather than only one app controlling all monitors at any time and needing each app to implement its own multi-monitor support. I know fbdev is an inefficient, un-accelerated wrapper of the DRI, but it’s so easy to use!
Want to draw something on a particular monitor? Write to its framebuffer file. Want to run multiple apps on multiple screens without needing your DE to launch everything? Give each app write access to a single fbdev. Want multi-seat support without needing multiple GPUs? Same thing.
Right now, each GPU only gets 1 fbdev and it has the resolution of the smallest monitor plugged into that GPU. Its contents are then mirrored to every monitor, even though they all have their own framebuffers on a hardware level.
This right here is why i moved to a single display setup.
So this is why multi monitor support has been a never ending hot mess?!
Yes and no. It would solve some problems, but because it has no (non-hacky) graphics acceleration, most DEs wouldn’t use it anyway. The biggest benefit would be from not having to use a DE in some circumstances where it’s currently required.
Domain authentication and group policy analogs. Honestly, I think it’s the major reason it isn’t used as a workstation OS when it’s inherently more suited for it than Windows in most office/gov environments. But if IT can’t centrally managed it like you can with Windows, it’s not going to gain traction.
Linux in server farms is a different beast to IT. They don’t have to deal with users on that side, just admins.
Ubuntu Server supports Windows Active Directory. I haven’t used it for anything but authentication (and authentication works flawlessly) and some basic directory/share permissions but theoretically it should support group policy too.
It’d be cool if there was a mainstream FOSS alternative though (there might be, I’ve done literally 0 research), but this works okay-ish in the meantime.
But for management of the actual production servers at work I use a combination of ManageEngine (super great and reasonably priced) and Microsoft’s Entra (doesn’t work well, don’t do it)
An immutable distro would be ideal for this kind of thing. ChromeOS (an immutable distro example) can be centrally managed, but the caveat with ChromeOS in particular is that it’s management can only go through Google via their enterprise Google Workspace suite.
But as a concept, this shows that it’s doable.
I’m surprised more user friendly distros don’t have this, especially more commercial ones
I’ve never understood putting arbitrary limits on a company laptop. I had always been seeking for ways to hijack them. Once I ended up using a VM, without limit…
Rule #1 never trust your users
Because people are stupid. One of my coworkers (older guy) tends to click on things without thinking. He’s been through multiple cyber security training courses, and has even been written up for opening multiple obvious phishing emails.
People like that are why company-owned laptops are locked down with group policy and other security measures.
ARM support. Every SoC is a new horror.
Armbian does great work, but if you want another distro you’re gonna have to go on a lil adventure.
Wouldn’t it make more sense to focus on an open standard like RISC-V instead of ARM?
Standardizing package management? Imagine everyone being stuck with .rpm
Configuration gui standard. Usually there is a config file that I am suppose to edit as root and usually done in the terminal.
There should be a general gui tool that read those files and obey another file with the rules. Lets say it is if you enable this feature then you can’t have this on at the same time. Or the number has to be between 1 and 5. Not more or less on the number. Basic validation. And run the program with --validation to let itself decide if it looks good or not.
so, YaST?
I agree. OpenSuse should set the standards in this.
Tbf, they really need a designer to upgrade this visually a bit. It exudes its strong “Sys Admin only” vibes a bit much. In my opinion. 🙂
Small thing about filesystem dialogs. Some apps group directories at the top and others mix them in alphabetically with files. My preference is for them to be grouped, but being consistent either way would be nice.
interoperability > homogeneity
interoperability == API standardization == API homogeneity
standardization != monopolization
Not offering a solution here exactly, but as a software engineer and architect, this is not a Linux only problem. This problem exists across all software. There are very few applications that are fully self contained these days because it’s too complex to build everything from scratch every time. And a lot of software depends on the way that some poorly documented feature worked at the time that was actually a bug and was eventually fixed and then breaks the applications that depended on it, etc. Also, any time improvements are made in a library application it has potential to break your application, and most developers don’t get time to test the every newer version.
The real solution would be better CI/CD build systems that automatically test the applications with newer versions of libraries and report dependencies better. But so many applications are short on automated unit and integration tests because it’s tedious and so many companies and younger developers consider it a waste of time/money. So it would only work in well maintained and managed open source types of applications really. But who has time for all that?
Anyway, it’s something I’ve been thinking about a lot at my current job as an architect for a major corporation. I’ve had to do a lot of side work to get things even part of the way there. And I don’t have to deal with multiple OSes and architectures. But I think it’s an underserved area of software development and distribution that is just not “fun” enough to get much attention. I’d love to see it at all levels of software.
One that Linux should’ve had 30 years ago is a standard, fully-featured dynamic library system. Its shared libraries are more akin to static libraries, just linked at runtime by ld.so instead of ld. That means that executables are tied to particular versions of shared libraries, and all of them must be present for the executable to load, leading to the dependecy hell that package managers were developed, in part, to address. The dynamically-loaded libraries that exist are generally non-standard plug-in systems.
A proper dynamic library system (like in Darwin) would allow libraries to declare what API level they’re backwards-compatible with, so new versions don’t necessarily break old executables. (It would ensure ABI compatibility, of course.) It would also allow processes to start running even if libraries declared by the program as optional weren’t present, allowing programs to drop certain features gracefully, so we wouldn’t need different executable versions of the same programs with different library support compiled in. If it were standard, compilers could more easily provide integrated language support for the system, too.
Dependency hell was one of the main obstacles to packaging Linux applications for years, until Flatpak, Snap, etc. came along to brute-force away the issue by just piling everything the application needs into a giant blob.
I find the Darwin approach to dynamic linking too restrictive. Sometimes there needs to be a new release which is not backwards compatible or you end up with Windows weirdness. It is also too restrictive on volunteer developers giving their time to open source.
At the same time, containerization where we through every library - and the kitchen sink - at an executable to get it to run does not seem like progress to me. It’s like the meme where the dude is standing on a huge horizontal pile of ladders to look over a small wall.
At the moment you can choose to use a distro which follows a particular approach to this problem; one which enthuses its developers, giving some guarantee of long term support. This free market of distros that we have at the moment is ideal in my opinion.
The term “dependency hell” reminds me of “DLL hell” Windows devs used to refer to. Something must have changed around 2000 because I remember an article announcing, “No more DLL hell.” but I don’t remember what the change was.
Manuals or notifications written with lay people in mind, not experts.
Stability and standardisation within the kernel for kernel modules. There are plenty of commercial products that use proprietary kernel modules that basically only work on a very specific kernel version, preventing upgrades.
Or they could just open source and inline their garbage kernel modules…
