Skip Navigation

escaping windows/macOS and want to get work done? here's my list of dos and dont's

after trip-digit linux installs in the past year or so, here's my list for a seamless transition for people escaping windows/macOS who need to get work done:

1) don't tailor linux to your hardware, do it the other way around. get hardware that works OOB. no nvidia. no latest hardware. no weird realtek chipsets in budget deal-of-the week e-waste, no gaming (i.e. nvidia) laptops.

that don't mean breaking the bank, a thinkpad with 8th gen or newer CPU can be had for $100ish; add $50 or so to expand RAM and storage and that covers like 90% of use cases. a competent all AMD desktop a gen or two behind current tech that can game almost anything can be easily assembled for less than $400.

fedora and adjacent forums are littered with cries for help about stuff breaking or not working at all; 90% of those are nvidia related. can you make it work - absolutely. is that something you're willing to dick around on a deadline - hell nah.

2) no theming. no icons, no fonts, no plymouth screens, nada. as few extensions/plugins as you can, run it as close to stock as possible. shit's gonna break, this is a work device, you can't afford downtime because the single dev maintaining the thingy hasn't updated it for the newest Gnome of Plasma. Gnome don't feel like macOS? you'll get used to it; muscle memory is a removed but it's a tameable one.

an additional moment, especially if you're on a laptop, is to make the thing as fungible as possible. that's an easily breakable/losable thief-magnet, you want a setup that can be reproduced with as little fuss as possible so you can be operational again.

3) don't dual/triple/whatever boot. that's an advanced scenario, it's gonna break eventually and if that's a device you depend on for work or education, you don't want any of that. run it as a single OS occupying the whole disk; encryption on a mobile device is mandatory. if you absolutely need multiple OS, a 2nd device is stupid cheap and it compartmentalises your shit, i.e. one for work, one for private/gaming, etc.

4) no weird distros. no arches, no gentoos, no immutable thisisthefuture shit. when it becomes mainstream, we'll switch. until such time, middle of the road - fedora for newest hardware, mint for ancient stuff, ubuntu for everything else. a lot of people made sure they're operational OOB, it's less likely stuff will break and if it does, there's an army of folks who asked and answered whatever's bothering you.

5) no weird DEs. wayland only, gnome for laptops and tablets, plasma for desktops, there is no third option. you're transitioning from an infinitely polished UI and the best tech that money can buy, you want the closest possible experience and the widest used environment, worked on by the largest dev community aware of the widest possible usability issues, working towards fixing/implementing them. you're already relearning shit, invest that time wisely.

6) separate your system stuff from your applications as much as possible. purge all user-facing apps, like firefox and media players and such from the system's package manager (apt or dnf) and reinstall them from flatpak. that was a headache a few years ago, nowadays almost everything works OOB on wayland. the apps include everything they need to work, the setup is easy to maintain and recreate, upgrades are better (no reboots necessary) and all your settings and data are in one place.

this covered 90% use cases of 90% of the users I've dealt with. naturally, edge cases are gonna have a bad time - you want to ollama this and that and rock bleeding edge hardware and have a normal desktop experience? it's gonna hurt. you need mac-like power management and days away from power? doable but that needs work.

remember, this is a work device. for the same reason you don't decide to "upgrade" the suspension on the car that's supposed to get you to work the morning of, you don't mess with what's likely the only device you need for work/education.

greybeards dunking on you because you're not a "real" linuxer? enamoured with the spicy screenshots from linuxporn? get a $20 thinkpad and go wild - arch it, sway it, have the scrolling text on boot, rice it till it bursts. but leave your workhorse be.

51 comments
  • 90% of those are nvidia related.

    I'm not a Fedora user (Debian and Mint are my go to) but I don't have a similar impression. Also, my own NVIDIA GPU has always worked OOB (even without installing its proprietary drivers, it just works better after installing them) and still is, but it's also considered old being a 970.

    Imho, a simpler advice would be along the line of what you mentioned already. Something like: don't rush for the latest/greatest hardware. Often, new stuff will lack support.

    1. no theming. no icons, no fonts, no plymouth screens, nada. as few extensions/plugins as you can, run it as close to stock as possible.

    I agree with the idea of not wasting time but configuring the theme/look (which is part of the OOB experience, on Mint and Debian at least) can be essential to work in decent conditions.

    As a matter of fact, theming is one of the technical reasons why I switched to Linux from Mac. The ability to have the text as large as I wanted it to be: getting older, one slowly realizes that small thin light-greyish designer cherished fonts lose a lot of their appeal in favor of those non-fancy but larger and bolder dark fonts that are more easy to read :p

    So, I would object that theming can be a very legit, like 100% legit part of the process of turning a Linux machine into a usable working machine one will be able to work on for hours (like tweaking the keyboard layout would be for anyone, like me, writing in more than one language). And that is not even mentioning people with disabilities.

    1. don’t dual/triple/whatever boot.

    Unless one has too, sure. Try running any recent edition of Photoshop in Wine and do real paid work...

    My own solution was to keep a dedicated machine for anything like that: Photoshop and video. Note that for video one may decide to let go of FCP or Premiere and switch to DaVinci Resolve, instead.

    1. separate your system stuff from your applications as much as possible. purge all user-facing apps, like firefox and media players and such from the system’s package manager (apt or dnf) and reinstall them from flatpak

    Why would that be a good idea?

    I mean, I do my best to avoid all those third-party installer (like Flatpak) because they are not as well integrated to the system as the native installer is (in my case it is 'apt'), and because they also waste much more disk space for the reason that, like you said:

    the apps include everything they need to work,

    Which, sometimes/often, means a real lot of extra stuff.

    the setup is easy to maintain and recreate

    That's the exact reason why I use the native installer and not those third-party ones. That and the faultless integration with the system (menus, themes and stuff like that).

    And in the odd case I would have to reinstall Linux (an even stranger need on a work machine, since that machine I would not tweak it beyond what I deem necessary for me to be able to, well, work on it and therefore it would be rock stable), even in that case I would need to reinstall it, I find it so quick to reinstall all my apps by typing a single line: "sudo apt install app1 app2 app3 app9999", no matter how many apps.

    I am keeping such a list in a text file, I update every time I start using a new app, just in case one of those days I truly am forced to reinstall my system. So, I know it would only be a matter to copy-paste said command line in a new shell. Not pretty but real easy and quick ;)

    Flatpak (...) upgrades are better (no reboots necessary)

    Once again, I'm not a Fedora user but does Fedora really need to reboot after updating a bunch of apps? I have hard time imagining that.

    Sorry if my comments sounds critical, it's not my intention. But while I was reading your post I was very surprised how affirmative you were on certain decisions/choices and how much my own personal experience was different.

    greybeards dunking on you because you’re not a “real” linuxer?

    And if you're wondering, nope, I am not one of those 'real user' either even though my beard would be grey, if not plain white now... if I had one. I come from 35+ years (happily) using Apple hardware and software for work and for personal stuff ;)

    Edit: clarifications.

  • Who hurt you?

    greybeards dunking on you because you’re not a “real” linuxer

    Oh, right. I see.

  • downtime because the single dev maintaining the thingy hasn’t updated it for the newest Gnome of Plasma.

    is this really that bad? I remember seeing a Win7 theme for KDE, and I really want to install something like that on a spare laptop. will it break something with each update from the distro?

    • is this really that bad?

      As someone who slightly customize his Linux DE, I would say that the real but potential issue when using some non-official theming (or very niche ones) is that one does indeed risk having issues after a major system update, thing breaking off or just plain not working anymore. It's no 100% certain, but the risk is real. And that is something that, on a work machine at least, is never an option (the machine is supposed to be available and work in a predictable and reliable manner, hence why I'm so madly in love with Debian plus it's so well optimized :)). On a personal machine? Well, that's up to anyone to decide what their priorities are.

      Luckily one is not required to use extreme theming. Personally, I limit myself to whatever is provided with my version of Linux in order to change font size, colors/theme, wallpaper, cursor appearance and so on. So, everything is easier to see for my old eyes.

      It works very well and since it's part of the distribution I know it will not break after an update. The downside is that it's often much more limited than what some other dude may have done somewhere on their own machine and then decided to share online. I don't mind it ;)

  • I myself have been using linux for 15 years and disagree with what you've said.

    1. Learn how to install and update on Endeavor and you won't have to worry about much - it just works, on any hardware.

    Fedora always breaks on me, whether it be nvidia or amd. I used to love Fedora but found it breaks far more than otherwise.

    The Linux vernal is designed to work on up to current gen hardware. If anything the current gen nvidia stuff is rough (40 series). I've had no issues with 30 series or 7000 series amd GPUs.

    1. Why? Nothing wrong with using extensions. They're usually updated within a week if Gnome or KDE breaks them. With gnome I've had 10+ extensions with 0 issues across multiple computers.
    2. Not true. My dual boot has never broken on multiple computers. Whether is be Debian, Ubuntu, fedora, or arch.
    3. Also not great advice. I found Endeavor OS, which is Arch to run the best. PopOS was the only other one that just worked.
    4. This I do agree with; hyprland, i3, etc take a long time to fine tune. While tiling managers do help with productivity, setting them up takes a while.
    5. Flatpaks should not replace system packages. They tend to be updated much slower and scaling can be weird on them.
    • My dual boot has never broken on multiple computers. Whether is be Debian, Ubuntu, fedora, or arch.

      That's great, but it's still shockingly common and not something newbies should have to try to fix

  • 1: Agree, mostly. I bought a Thinkpad E16 for its Linux support, though I accidentally got a Realtek one that had few bugs that I've since ironed out. My only thought is if you own existing hardware that is still usable, it is worth your time at least trying.

    2: I somewhat agree. On my note taking laptop, I go by this philosophy. On my desktop, though, I theme away and still get lots done.

    3: I sort of agree with you; I think like you said, if you have one drive for each OS, you won't have problems - dual booting is fine. I've got 2 internal drives in my Thinkpad, though honestly, I hardly use the Windows one. I remember 2 partitions being livable on my Surface Go, but again, I barely touched Windows, so I don't think it had much chance to bork the bootloader.

    4: I agree on the Arch and Gentoo part - after trying to use Debian Testing on several laptops, I found rolling release just isn't conducive to a no-frills productivity device. Honestly, though, I don't see that much problem with immutable, especially if you go with Flatpak. I also think any stable distro you like should work so long as it has a backports kernel - I'm using Debian 12 that way on an E16 and it's been pretty smooth (besides the Realtek thing at the beginning, but I fixed that months ago).

    5: Wholeheartedly disagree, mostly because XFCE was excluded. 😭 I feel like X11's still not that far off the beaten path. This feeling will probably change when XFCE switches; 4.20 comes out with preliminary support in a few weeks, and my bet is 4.22 in 2026 will have full Wayland support.

    6: I don't totally agree with this either. I feel like when it works well natively, go for the native package. If you're having trouble, switch to the Flatpak. I've actually had problems with the VSCodium Flatpak on my laptop not using system environment by default, though there is a fix.

  • Immutable was the only thing that got me to switch back from QubesOS on my desktop. I was doing Qubes with a win10 HVM with my 3070 passed through and it was a couple frames off from native performance. Still keep Qubes on my T480 for infra specific work but my "dev" machine with no creds is the desktop now.

    Couldn't get the performance quite right for a Linux based HVM and was wanting the HW accel for some of my work (CAD, figma) so I loaded Bazzite with KDE which runs Fedora Atomic and it's been amazing for both gaming and work.

    Distrobox with boxbuddy and rootful containers where needed has been extremely pleasant and they all live as a subdirectory of my home with a ZSH install script I have to load the terminal styles I want into any new containers. Any apps you install in the container you can export to your start menu and launch seamlessly without tainting your host with any weird dependencies you might need for a project.

    We use ddev a lot so needed a rootful container for Docker but other projects I just treat like a VM almost (R projects for instance), install whats needed to get an env going real quick and fire up the IDE in the container and get to work.

    EVERYTING I care about is in /var, including my home which makes backups and snapshots stupid simple which I love coming from a traditional Linux distro

  • here's a combo reply that doesn't need to be there, but people have issues reading titles, I don't know...

    first off, do you realize where we're at? normies don't frequent lemmy, you have to put in considerable effort to find it and interact with it. your average lemmyst's tech expertise is way, way above the average user, compared to say reddit or, heaven forbid, facebook or such.

    I'm not answering dudes (no gender inferred) who are like "X years linuxing". have you read the title of the post? can you deduce who it's directed at? you're seriously suggesting endeavor and arch and friends to people who've opened the command prompt a total times of never and don't understand what regedit is/was for?

    this is a post directed towards people transitioning from windows and macOS. people who have issues comprehending bootloaders and kernels and DEs, WMs, etc - and frankly, it's 2024 and they don't need to. people who close the laptop when they're done and open 'em in the morning, basically people who don't do a lot of sysadmining in their daily lives.

    when was the last time you handed over a laptop with a fresh install to a linux illiterate being? I did so three times this week, and that's below average; can't get cheap SSDs right now to upgrade the the discards we get. my point is, I know what they come back with in terms of problems and grievances and none of them include "spending more time tweaking xorg.conf" or "learning systemd". they have issues printing and sharing files and laptops sleeping/waking when they're supposed to and counter-intuitive touchpad gestures and the like.

    I've also had my share of devs trying to convert their issued laptops with fully functioning installs to this weird rice after reading DHH's blog and the amount of lost time and productivity spent undoing that crap is staggering.

    linux has this problem of experienced users raining downright useless and often counterproductive advice on noobs. the shit that works for you doesn't work for them and you know that; the same way a racing car driver's advice is useless in everyday traffic

    • first off, do you realize where we’re at? normies don’t frequent lemmy

      No need to be passive aggressive, but if you think all people on lemmy are so tech savvy, then why post it here?

    • linux has this problem of experienced users raining downright useless and often counterproductive advice on noobs.

      Not to be rude, but you might want to take your own advice. I see a lot of hyperbole in your two, frankly, rants. "Greybeards" might have ruined your experience, but most people around here just want to help.

    • I'm going to actively voice my support for this mentality, more than just an up vote. People saying things like dual booting and rolling distributions are good ideas for genuinely new users who, like you said, have never opened a command prompt or regedit, really shouldn't be suggested those types of things.

      The average dev/tech enthusiast has a horribly bad habit of drastically over estimating the average person's technical ability. While I believe it's reasonable to expect new uses to want to try and learn (I'd hope everyone would want to learn sometimes), the reality is that most folks won't.

      The one that just makes me want to scream is when people suggest installing Arch via the wiki. I did this around 2015 or 2016 on a VM and couldn't get it working. To be fair, I wasn't terribly motivated to really dive into what was wrong, but people act like it's really magically simple and clear cut when it's not. (With the major caveat that perhaps it's gotten better since last time I tried.)

      I think so many of these discussions go to shit because of who the target audience is intended to be and who the responders believe the target audience to be.

51 comments