Live data from Hacker News

Lobotomizing Gnome

eklitzke.org

131–140 of 224 posts

Re: Lobotomizing Gnome

#131
post #84

Perhaps tangential but does anyone know if you can run Ableton Live on Linux using some emulation layer? This is maybe the one piece of software keeping me from ditching Mac OS X.

Here's a current thread regarding Ableton Live registration via Wine - https://linuxmusicians.com/viewtopic.php?f=1&t=18590 - apparently it's not the easiest.

Alternatively, Bitwig runs natively, though costs. It's about the only native software that does the clip launching style of production/performance well.

Re: Lobotomizing Gnome

#132

Earlier quoted context omitted.

Perhaps you're right and you just have to keep shutting your laptop down and booting up from cold to prevent Windows problems.. sorry, updates from happening at the wrong time. I watched a three hour stream of a professional chess player and youtuber and at the start he's saying "...oh, and I just updated my Windows laptop a few days ago so hopefully it won't start to slow down or apply an update while I'm playing".…

Those really in the know seems to upgrade to a variant that allows them to go into group policy and curb stomp the auto-update. Others achieve the same via registry modifications...

Or you block the download of updates via setting the wi-fi as a metered connection.

Re: Lobotomizing Gnome

#133

This mentality "lets add a daemon to run in background 24/7" to provide some service thats sits mostly unused is unacceptable. Its not only gnome developers, its widespread in open-source. The competitive edge of Linux is reduced quite a bit when there is enough bloatware running around by default.

What is going on as of late, and it is led by Gnome/freedesktop/RH devs, to split fully working software into two parts. A UI frontend, and a deamon backend. And between them sit dbus and polkit, so that someone, somewhere, may write some "fine grained policies" about who can and when they can do anything.

What i am observing is that what used to be a "clean" system once you got used to the unix thinking, is being torn to shreds trying to placate two sub-groups.

The first is the military-industrial complex that wants to make damned sure the grunts can't read how crap the "police action" is going.

The second the the cloud-heads that wants everything to be able to scale from 1 to 1 million running units with the push of a button.

Re: Lobotomizing Gnome

#134
post #112

Earlier quoted context omitted.

It's pretty different from the Redhat in the bookstore days. I tried MINT 5 years ago, and never looked back. While the top-rated distros might not be simple enough for grandma to -install-, after that it's cakewalk. (unless she's picked up bad habits using previous OS's). Forced upgrades ... man that's WAY far into the Dominator zone.

No forced upgrades is good, but e.g. from the requirements in the howto on upgrading Mint 17 to 18: * Good understanding of APT and vast experience in working from the command-line. Have fun Grandma!

I've always liked the way debian/Debian based systems do updates. Older versions of windows were maybe a little too subtle (many users just ignored the small icon in the tray) vs. the large dialog box that pops up. It's also very easy to just hit accept and let it run in the background. I switched my father's laptop over several years ago (he only surfs the internet/email/scans/prints) and haven't had a tech support call for two years. I'm stuck on windows until there's a decent mechanical CAD avaliable, but good lord am I wishing I stayed with 7. This is the first time I've ever had to change the default in GRUB to windows in ~10 years of dual-boot, since otherwise I have to babysit the thing every update. Sad part is, I actually prefer the UX of 10 more than even MacOS, but for anything 'power-user' orientated it's just such a pain to administer.

Side note: has anyone else had problems with system settings reverting to default after updates? I've turned off the suggestion notifications several times, as well as neutering cortana.

Re: Lobotomizing Gnome

#135
post #32

Open-source desktops are never perfect for anyone, but everyone expects them to be. For everyone who says they are too bloated, someone else says they are too spartan. That's probably why there are so many of them. I would expect working on Gnome (or KDE or Cinnamon or Mate or XFCE or LXDE, the list goes on) to be a thankless task. You try to please everybody and yet please nobody. The imperfections of Linux desktops…

> For everyone who says they are too bloated, someone else says they are too spartan. Sometimes it can even be the same person depending on their needs. On my coding laptop I swear by i3, it's fast, simple and powerful. Everything is just a keystroke away. On my entertainment machine though (TV, music and games) I find gnome much better because friends can use it and these tasks are better handled with a mouse. This…

For an entertainment machine, I'd suggest installing Steam and auto-launching to big picture. Very easy to navigate from a couch w/ a controller, and you can use it for nearly any media task you want. It does take some time to configure your media directories, but not having to deal w/ a mouse on a media machine is so much easier. Plus, since your base OS can be something like Debian, remoting into the machine for administration is eminintely doable.

Re: Lobotomizing Gnome

#136

Earlier quoted context omitted.

This is not my experience at all. I am using it on my first gneration i3 media center PC and it runs reasonably well. I don't use it for any heavy lifting -I am just starting browsers, running media players and watching videos, but for me it works fine - so well that I don't have any need to check out more lightweight options. It has more problems with the spotify app than with any of the things I am doing with Gnome…

I suspect it is mostly RAM related, not CPU related. My laptop is an older i5 with Intel graphics and 4GB of RAM, and Gnome Shell (on Wayland) uses about 1GB more memory than Sway (a tiling Wayland compositor) does, which makes a big difference with the same applications. But when it's not under RAM pressure, Gnome is perfectly smooth.

Then you've surely hit the memory reclaim problem. I checked just now and my GNOME Shell started this morning is using 153 MB memory (resident).

There are some latency issues after moving to Wayland, though. Don't have a good link, but AFAIK it has something to do with Mutter or the Shell which were never specifically optimized for latency ending up being responsible for input handling.

Re: Lobotomizing Gnome

#137
post #136

Earlier quoted context omitted.

I suspect it is mostly RAM related, not CPU related. My laptop is an older i5 with Intel graphics and 4GB of RAM, and Gnome Shell (on Wayland) uses about 1GB more memory than Sway (a tiling Wayland compositor) does, which makes a big difference with the same applications. But when it's not under RAM pressure, Gnome is perfectly smooth.

Then you've surely hit the memory reclaim problem. I checked just now and my GNOME Shell started this morning is using 153 MB memory (resident). There are some latency issues after moving to Wayland, though. Don't have a good link, but AFAIK it has something to do with Mutter or the Shell which were never specifically optimized for latency ending up being responsible for input handling.

It's not just Gnome Shell. I mean, I do hit the memory reclaim issue, but Gnome Shell is still not using that whole extra 1GB. The rest is evolution-data-server and so on.

Re: Lobotomizing Gnome

#138
post #127

Earlier quoted context omitted.

Not the author, but I just tried KDE for two weeks, and coming from Gnome, I couldn't acclimate. I found the Plasma experience unpolished, inconsistent, and prone to error. I also ran into quite a few bugs (at one point, Plasma just stopped giving me window previews when alt-tabbing, and not a single alternative alt-tab style from the built-in installer worked for me). Two examples of things I missed coming from Gnom…

IIRC on kde you can also resize windows with alt + right click, without needing to hit exactly the border. (Or maybe its middle click I don't remember. ) this is similar to alt + left click to drag a window without clicking the title bar. On gnome you can use Super + middle click to resize things and super + left click to drag them

I am on KDE 5 and TIL! Thanks.

Alt+right click resizes window and Alt+left click drags the window.

Re: Lobotomizing Gnome

#139
post #130

Earlier quoted context omitted.

I have no experience with Mate, but the feature I miss the most in the traditional desktops is starting programs by hitting the super (Windows) key and typing the programs. I know that you can use Alt+F2 for this, but using super is much more ingrained for me since I've seen Windows Vista (I am using Linux at home and Windows systems at work)

>hitting the super (Windows) key and typing the programs That's how Unity (Ubuntu's default DE) worked, until they transitioned to GNOME.

Gnome also works like that
Post reply on HN