Earlier quoted context omitted.
20 years for 1%, there is always hope I guess.
Steam Deck should at least double that.
The same way that counting Android phones as desktop does?
Switching from macOS to Pop_OS
301–310 of 380 posts
Re: Switching from macOS to Pop_OS
#302Earlier quoted context omitted.
20 years for 1%, there is always hope I guess.
Only if you view the achievement as trying to win market share, but since Linux is FOSS there technically is no market to share with the commercially provided OSes. Market share only matters if you're trying to make money by creating the OS. Otherwise Year of Linux on the Desktop is a personal goal for the user so the usage is actually 100% when they switch over. 2021 was the year that Sally and Bob switched, 2022 wi…
Like many security exploits have proven, being FOSS matters very little when there aren't resources to keep it going.
Derrick, Anne and Louisa won't switch if it doesn't support their shinny new laptop.
By the way, I do use Linux since Slackware 2.0, winning Windows desktop market share was the original goal of The Year of Linux Desktop.
Now one can to turn it around to make it mean a slightly different goal, so that after 30 years it can finally tick the box.
Ironically the Year of Linux Desktop has been achieved indeed.
Derrick, Anne and Louisa don't need to switch, because it already runs on a VM installed via Windows Store.
Re: Switching from macOS to Pop_OS
#303Re: Switching from macOS to Pop_OS
#304Earlier quoted context omitted.
Linus tried it but had an issue where installing steam wiped his DE. He switched to Manjaro and Luke used Mint.
Not paying attention while installing steam wiped his desktop. TBF though he isn't that used to using Linux as a desktop. Manjaro did go much smoother for him.
Linus tried to make the point that on windows you don't have to pay close attention when doing something minor like installing Steam. Because why should something like that ever even have the potential to remove your desktop environment? (*On a system meant for the common consumer that is not an expert in the domain*)
Yes he didn't pay attention to the warning, but in fairness Linux gives a lot of warnings. Sudo gives a warning when you first use it, and that's clearly used all the time. To you and I who know what "gnome-de" is (or whatever the package name is) the warning is clear. But to someone new to the space, DE is not a commonly used acronym.
Re: Switching from macOS to Pop_OS
#305Re: Switching from macOS to Pop_OS
#306Earlier quoted context omitted.
It’s more about how on MacOS, Apple gets to dictate what signal that gesture is going to send to the applications and you can’t configure it to send anything else. So either the application recognizes that signal and it works for every system, or it doesn’t and it doesn’t work for every system. This makes it a lot more likely that apps are going to recognize that signal so it works for every system. It’s the paradox…
Not really. On macOS, trackpad swipes produce a series of horizontal scroll events, not a simple back/forward event. An app can do whatever it wants with the scroll events. Safari, when the scroll position is at the end of the horizontal outer edge of the document, does an interactive back/forward animation that tracks your fingers while they remain on the trackpad.
> On macOS, trackpad swipes produce a series of horizontal scroll events, not a simple back/forward event.
That's not true. On macOS (and also iOS), you subscribe to gesture recognizers (i.e. swipe gestures), not isolated events, which give you easy access to how users interact with macOS without having to analyze (and likely analyze incorrectly) low-level trackpad interaction.
You could always choose to look directly at events instead, but if you are trying to get the behavior of a widely-used gesture like swiping forward/back, you will get much more accuracy (and happiness from users, and less dev time) by just recognizing them at a high level, which is what Apple expects.
Re: Switching from macOS to Pop_OS
#307Earlier quoted context omitted.
I find this funny, in that I struggle with Mac all the time. The worst grievance lately is that I don't know how to just pop back and forth between three windows. Something about the way command tab works just kills my ability to reason about what the window stack currently is. And, for the life of me, I never get copy paste from a terminal to work like I want it to.
Make your desired windows fullscreen, then swipe side to side on the trackpad (3 or 4 fingers) to switch between them almost instantly. One of the best features of MacOS, IMO.
Gnome does the same. Slow, jarring and pretty useless for mouse+keyboard or displays larger than laptop sized.
"Just swish your virtual desktops around" seems extremely convoluted when I just want to switch between different windows.
Re: Switching from macOS to Pop_OS
#308All I want in life is a Linux distro with a package repo full of meticulously reworked & reconfigured packages that make all the keyboard shortcuts across the entire system and every application be like and be as consistent as my old Macs. I've been full-time Linux (Kubuntu) for a few years now, and I've hobbled together something that only irritates me to death about 30% of the time rather than the 100% of the time…
I find this funny, in that I struggle with Mac all the time. The worst grievance lately is that I don't know how to just pop back and forth between three windows. Something about the way command tab works just kills my ability to reason about what the window stack currently is. And, for the life of me, I never get copy paste from a terminal to work like I want it to.
> I never get copy paste
You can just use middle click everywhere, no? One checkbox in the clipboard manager and done.
Btw ctrl+shift+v to paste is often much more useful than ctrl+v, e.g. for emails, and is the exact same in the terminal.
Re: Switching from macOS to Pop_OS
#309Earlier quoted context omitted.
Lol. I came here to say the only thing that matters is that copy and paste in Linux is 'cntrl+shift+c'. You can try changing it, but your still fucked in most terminals, and then you end up with two key combos depending on context. It's a nightmare, and I'm really glad you have the top comment. Clearly I'm not alone.
Terminal is the only thing that maps ctrl+shift+c/v to copy/paste because ctrl+c/v conflicts with signals. I've never come across any other program that maps something that isn't ctrl+c/v to copy/paste. MacOS is able to keep this consistent because ctrl+c/v isn't mapped to copy/paste, and instead command+c/v is. If you really want, Linux is perfectly capable of mapping Super+c/v to copy/paste. You would probably only…
Four examples:
- Pretty much everything uses ctrl+shift+v for pasting without formating. Really useful for emails, Word, ...etc.
- vim does not use ctrl+c/v
- emacs (=Mac keybindings) also does not. Simply because their bindings predate IBM's ctrl+c/v
- middle mouse button works everywhere and can use the same clipboard (one checkbox)
Re: Switching from macOS to Pop_OS
#310Earlier quoted context omitted.
Having recently moved back to Linux (PopOS) from Windows, the one biggest annoyance is not being able to configure two-finger touchpad swipe to be browser back/forward. This is the default in Mac, easily configurable in Windows (perhaps it's the default?), and default in ChromeOS. But simply not an option in any Linux I've tried. The Epiphany Browser does it, but that lacks extension support so is a no-go for me. Any…
and default in ChromeOS. But simply not an option in any Linux I've tried. Bit of a tangent, but it's always funny to me to discuss ChromeOS and Android as distinct from Linux distributions. I get that they're each practically as "Linux" as TiVo (and might not even be that forever, depending on how Fuscia evolves), but it actually might help avoid confusion if we started using the term GNU/Linux unironically in some…
Because they actually are, the fact that they use the Linux kernel is an implementation detail.
Termux folks keep hitting walls, because they refuse to acknowledge these are the only APIs they are allowed to call.
https://developer.android.com/ndk/guides/stable_apis
So when they make use of other Linux stuff that according to Google are private APIs, things don't go well.
As for ChromeOS, the kernel isn't exposed to userspace in any form, which are basically Webapps.
Running Linux applications on Chrome OS makes use of a secondary distribution in a VM, pretty much similar to how WSL 2 works on Windows.
So they might use the Linux kernel, yet they are far away from being distros that can easily run the GNU stuff.