A few years ago we had some very Linux-friendly laptops. Sadly, they are getting a bit old and hard to come by.
What are some brand new Linux-friendly laptops, all the way down to firmware if possible, you have had good experience with?
Here's my laundry list:
My dad was trying to save money by keeping his Desktop PC w/ Intel Core 2 Duo w/ 999mb Ram and Nvidia Graphics It is running XP and it is crashing like crazy. I am going to install Slacko Puppy on it. Are there any better Linux OS's? I just need it to be able to run a web browser.submitted by /u/Drunk_Panda_456
I've been scouring Google for hours. I want to create a bash script that imports the 50+ VPN configurations I have but I need the commands to accomplish this. I'm amazed that with all the vpns who lack a Linux app, that this hasn't been done before.
If I missed a resource online, I swear I've been trying to figure this out for days before posting here.
Distro: OpenSUSE Leap 42.1
I'm an intermediate user. I can usually learn what I need to online but I'm clueless at this point.submitted by /u/inquisitivechild
So recently there has been discussion about why Xfce is still on GTK2. An interesting point was brought up that I feel deserves further, more in-depth discussion; Why not merge Xfce and MATE into one DE?
Now I know what you're thinking "Rathernott, what in Apt's name are you suggesting, man?! That's bloody crazy talk!" But bear with me here.
Right now in the Desktop Environment world, most use cases are pretty well covered. We've got the 'big three' large, fancy, full featured DE's consisting of Gnome, KDE, and Unity. For middle of the road we've got Cinnamon. And lastly the lightweight alternatives for both toolkits (GTK & Qt) such as MATE, LXQt, LXDE, Xfce, along with the various tiling WM/DE's like i3.
As we all know, LXDE has essentially been replaced by LXQt due to the LXDE developers not wanting to switch to the moving target that is GTK3. Now during their transition to Qt, something happened that really surprised me...They actually collaborated with another DE project! Specifically Razor Qt, thus becoming the LXQt we all know today.
This merging of these projects made a lot of sense, with the end result being more developers working toward a common goal, helping to prevent a lot of reinventing the of wheel once more. It was a Win-Win for everybody involved, and deserves high praise.
So whilst considering how well that particular merger went, let us now turn our gaze to the GTK alternatives.
Xfce started out life as a successful CDE (Common Desktop Environment) clone, however this changed in version 4.0, when it decided to radically transition to being more Gnome 2 like, for better or worse. Recently Xfce development has slowed tremendously, to the point where minor iterations can take years to release. This isn't necessarily a bad thing (why fix what ain't broke?), but simply something to consider for later.
MATE, on the other hand, is a Resurrection of Gnome 2, after being killed off in favor of Gnome 3.x which was a radical change in UI. It has since become a successful and popular alternative to the 'big three', with quite active development, and a bright future.
So with all the preliminary stuff out of the way, let's get down the meat of the issue.
MATE is a continuation of Gnome 2. Xfce since 4.0 is essentially a clone of Gnome 2, back when it was still the standard. Both use GTK2, and both have announced they wish to transition to GTK3 at some point in the future. They're project goals are similar, they use similar amounts of hardware resources, and even function similarly.
Taking all of this into consideration, it really does beg the question: Why not join forces, and merge into a single project?
As it is currently stands, both DE's are essentially doing the same work twice for no real reason, or advantage. If a merger were to happen, they could combine the best bits from each DE, and simply depreciate the rest.
Would this be a long, arduous, and possibly even painful process? Likely yes. But I believe the end result of combining the teams, reducing redundancy, and increasing the overall productivity of the project would make it worth it.
If it all fails in some spectacular fashion due to developer ego, clashing philosophies, or a simple lack of onion rings (Mmm...), at least we'd be able to say we gave it our best try.
Just to clarify, I don't this any of this will actually happen, because...Well, these types of things just don't generally occur. This is all just me spit-balling, really.
What's your take(s) on all of this?submitted by /u/RatherNott