I have helped people migrate from Windows to Plasma 5. They loved it. However, getting\installing software and general system management is still not straightforward enough. We also need system management tools that are solid. No terminal gymnastics at all for the common user on distros targeted at the masses.
Flatpak is all cool, but we need core user-space applications to be standardized. LibreOffice, for example, needs to become the industry standard office-suite. How can we achieve that? People I know just do not want to move away from MS Office. Even government agencies invest heavily in MS Office. This might just be the most important impediment.
I think, the Linux ecosystem shows us what a real "free market" looks like. Lots of small players and no monopoly. People love choices and they have. You want a minimal Window Manager, you got many to choose from. You want a full-blown Desktop Environment, you are spoilt for choice. Not a bad thing in an ideal world, but...
Every distribution spends more time on packaging and integration testing than developing useful functionality. When developing for Linux you need to package your application in a few different formats. We also have different init systems to make it more difficult. Every distro has own store and repositories. For GUI there are different frameworks and display servers.
If Linux world standardizes around snap/flatpak, systemd and wayland then we stand a chance.
DE being the first thing a common user interfaces with, it holds a very important position, in my opinion. KDE and Gnome are very different w.r.t design principles, hence the polarization and debate. KDE and Xfce are not so different. I like Gnome, but have no use for it.
I agree with all else.
Also, I think, a real "free market" would resemble Linux ecosystem. No monopoly, small players and lots of choices. However, if we wish to compete in "real world", we need to do something similar to what you say.
Consider the possibility that your idea of what "the common user" wants is something you made up.
I would argue that having a choice between hundreds of DE's is a bad thing for the more casual user.
The large majority of their users don't even know what kernel is running the runtimes of their apps.
One of the reasons of netbooks failure, besides the cheap Windows XP licenses move from MS, was that each netbook Linux was its own little silo.
The big players tend to be compared, isn't that reasonable?
In spite of piracy, a large set of population actually pays for them, versus bashing the authors for considering to charge money for their work while suggesting free alternatives.
A full stack framework that in spite of OEM customization is relatively standard across all devices with an Android label on them.
Don’t worry Linus, with Snaps and AppImages we’re hard at work fragmenting that front too!
The tradeoff is pretty obvious: on the one hand you get full control over what code you bring in, but you also get full responsibility of keeping it up to date and it does indeed take up more space. On the other hand you get systemwide updates, but also unpredictability which can break things.
In the former, you have a lot of work to do yourself to maintain your ecosystem between releases. In the latter, a greater amount of effort and responsibility goes onto those who maintain the packages at a distribution level to ensure mutually compatible package selections. This can be done (viz. most of the top tier distributions successfully doing this with occasional problems for decades) but we keep trying new all-in-one mechanisms every few years.
I'm not convinced that there's ever going to be a final answer to this, but it is clear that storage is cheap as chips...
The reason you don't see this on Linux is because there is no such thing as a separation between 'system' and 'application' in its culture. Consequently there has never been a "base system" to target or keep compatibility with so applications have to either target a specific version of a specific distro (waste of time) or include everything above the stable kernel ABI in their product (waste of space).
It is actually a very simple problem to solve, it just isn't one that the Linux community is interested in solving simply, so instead they invent ridiculously complicated tooling like package managers and Flatpak, introducing a bunch of unnecessary limitations and yet more parts to break and ruin your day.
Edit: clarification.
We'd need something more smoove and better over-all integration because there is still too many shortcomings and tiny bugs that could annoy a day-to-day user that doesn't want to know anything about config files or extended menus with special settings. It should be a great thing out of the box with sane defaults. That includes the icon set as well as a decent file browser and terminal emulator experience (iTerm2 on mac is THE REFERENCE here, I wouldn't want anything less).
Next comes workflows like office /graphics /audio stuff. I like how OSX handles PDFs etc and would love to see that on linux as well.
But I'm afraid this scattering is one of the biggest enemies of adoption and maturity of open source software. There is so many OSes and tools that you often have to research stuff for hours before you start off with a shitty tool that get's the job half done and then you recognize you can start from scratch because it doesn't work as you expected.
Instead many open source projects could live up to their potential if they'd combine efforts to merge the best they did and create ONE super awesome tool.
The reallity is that very often projects are just abandoned because adoption / donations etc. are too low or the 2 maintainers are tired after years of working on a project only 100 ppl on the globe are using.
Unite! At least converge to 2 big streams: Pro-Users (the ppl making jokes about shellscripts) and People (your mom)
Just focus on delivering for these 2 groups and I think most ppl would be glad about the end product. I for myself will try to do my best in putting efforts into projects I hope will have the biggest adoption.
I couldn't disagree more. As a community, developers and Linux developers in particular need to stop believing in the divide between the Glourious Developer Master Race and Ignorant Users What Think Their CD Tray Is A Cup Holder.
Linux Desktop has been pandering to this imagined notion of an "average user" for decades and it still sucks.
Here's what needs to be done: make the system simple (not easy) enough that it can be reasoned about, something that someone can look at and comprehend and build a model of its functioning so they can conform how it functions to their needs without reading C source code and 40 different text-based file formats and out of date man pages. Stop being a Rube Goldberg machine of interconnected disparate components.
I'm impatient to be able to update my laptop for a X1 carbon and a speedy KDE.
I have an old MBP (the one that has all the ports you'd including a standard HDMI, don't know what year) and never upgraded beyond osx mavericks - it runs fine until today.
A friend told me they use new MBPs @work and they seem to break much too often. I also tried the keyboard on his working machine to find out how bad it is nowadays! I prefer the oldschool thinkpad keyboard but was surprised by the keyboard on the old MBP. The new one's on the other hand are just a tool for torturing users who like to write much.
iTerm2 was my favourite because of the features (like intuitive tmux usage without learning it's CLI-foo). I also like how it is integrated with the rest of the desktop (searching, copy&paste, url-clicking etc.) but can't really compare to the default terminal emulator as I haven't used it much after trying iTerm2 when it was recommended by the whole world.
It's been very good since like at least OSX 10.5 (when they added tabs) or so.
I always wonder why people use other terminals (but don't seem to use any of it's special features).
I'd be curious to see if you think it performs better.
This is happening. The web is becoming the de-facto desktop environment.
Take a trivial example of desktop application integration, which is with us since Windows 3.11 - common file and printing dialog. Nothing standard like that on the web. Most web applications won't let you even export the data in editable format.
UI - horrible. Desktops had standard menus and shortcuts since 1980s. In fact, many SPAs are trying to invent their own desktop.
I could go on.. the fragmentation of web apps is so much larger than fragmentation of desktop apps.
So a few weeks ago, I'm sitting in the waiting room at my doctor's offices. And they seem to be running late. And the waiting room is filling up. So I go to the receptionist's window, and ask what's up.
Turns out that their ISP was having problems. And they were totally dead in the water. They had no local backup. And knew nothing. No patient data. No schedule. Nothing.
So hey, I just left, and rescheduled. But damn.
A browser could run bare metal for what I care.
What do you do when the internet is crashed / your app is down?
I like the data-sync & backup part of web apps - you don't have to save etc. and your whole machine can just fall into a river but you still have your work. But I'd rather do this with a seperate solution and keep stuff on my PC so I can access it without a network.
By providing a minimal kernel for juggling browser instances, local file system and browser specific "native" APIs.
Welcome back to the timesharing days, just with prettier UIs.
It is however the pace how things are going, even most mobile apps are modern versions of those 2-tier apps during the 90s.
I prefer using apps with ncurses interface to many web apps. Also the standards are not good enough for my demands. I've worked in web development and I know how tedious it is to re-implement the wheel for each and every user (at least it feels that way) because you have to ensure everything is rendered and works on 10 different browsers (different versions of course because who want's to update?). Also you have the devices (I don't even want to think about that) etc...
It is nearly 2k19 and still centering stuff with CSS seems to be a huge deal. That's just not very assuring for me.
> I still wish we were better at having a standardized desktop that goes across all the distributions. There's been some progress there. I mean, this is not a kernel issue, so this is just more of a personal annoyance how the fragmentation of the different vendors have, I think, held the desktop back a bit. But there has been some progress on that front too with Flatpak and things like that, so I'm still optimistic, but it's been 25 years. It's going to be another few years at least.