• 0 Posts
  • 45 Comments
Joined 1 year ago
cake
Cake day: June 20th, 2023

help-circle



  • Sure.

    MacOS is an excellent workspace operating system, largely due to its near-POSIX compliance and the fact that it has access to the enormous body of tools developed for UNIX-like OSs. For development work in particular, it can use the same free and open source software, configured in the same way, that Linux uses. Aside from the DE, a developer could swap between Linux and MacOS and barely realize it. Everything from Node, to Clang, to openJDK, to Rust, along with endless ecosystems of tooling, is installable in a consistent way that matches the bulk of online documentation. This is largely in contrast to Windows, where every piece of the puzzle will have a number of gotchas and footguns, especially when dealing with having multiple environments installed.

    From a design perspective, MacOS is opinionated, but feels like it’s put together by experts in UX. Its high usability is at least partially due to its simplicity and consistency, which in my opinion are hallmarks of well-designed software. MacOS also provides enough access through the Accessibility API to largely rebuild the WM, so those who don’t like the defaults have options.

    The most frequent complaint that I hear about MacOS is that x feature doesn’t work like it does in windows, even though the way that x feature works in windows is steaming hot garbage. Someone who’s used to Windows would probably need a few hours/days to become as fluent with MacOS, depending on their computer literacy.

    People also complain about the fact that MacOS leverages a lot of FOSS software, while keeping their software closed-source and proprietary. I agree with this criticism, but I don’t think it has anything to do with how usable MacOS is.

    I’m not going to start a flame war about mobile OSs because I don’t use a mobile OS as my primary productivity device (and neither should you, but I’m not your mom). The differences between mobile OSs are much smaller, and are virtually all subjective.

    You’re welcome.


  • Having the highest market share doesn’t mean that windows uses logical conventions, it just means that lots of people are accustomed to the conventions that it uses. The vast majority of professionals that I’ve interacted with strongly dislike having to work on a windows machine once they’ve been exposed to anything else.

    Off of the top of my head, the illogical conventions that Windows uses are: storing application and OS settings together in an opaque and dangerous, globally-editable database (the registry), obfuscating the way that disks are mounted to the file system, using /cr/lf for new lines, using a backslash for directory mappings, not having anything close to a POSIX compatible scripting language, the stranglehold that “wizards” have on the OS at every level, etc. ad nausium. Most of these issues are due to Microsoft deciding to reinvent the wheel instead of conforming to existing conventions. Some of the differences are only annoying because they pick the exact opposite convention that everyone else uses (path separators, line endings), and some of them are annoying because they’re an objectively worse solution than what exists everywhere else (the registry, installation/uninstallation via wizards spawned by a settings menu).

    For basic usability functions, see the lack of functional multi-desktop support 20 years after it became mainstream elsewhere. There is actually no way to switch one monitor to a 2nd workspace without switching every monitor, which makes the feature worse than useless for any serious work. In addition to that, window management in general is completely barebones. Multitasking requires you to either click on icons every time you want to switch a window, or cycle through all of your open windows with alt-tab. The file manager is kludgy and full of opinionated defaults that mysteriously only serve to make it worse at just showing files. The stock terminal emulator is something out of 1995, the new one that can be optionally enabled as a feature is better, but it still exposes a pair of painful options for shells. With WSL, the windows terminal suddenly becomes pretty useful, but having to use a Linux abstraction layer just serves to support the point that windows sucks.

    I could go on and on all day, I’m a SWE with a decade of experience using Linux, 3 decades using Windows, and a few years on Mac here and there. I love my windows machine at home… as a gaming console. Having to do serious work in windows is agonizing.


  • Of the three major desktop operating systems, windows is by far the worst.

    The only advantage windows has is that Microsoft’s monopolistic practices in the 90s and 00s made it the de-facto OS for business to furnish employees with, which resulted in it still having better 3rd party software support than the alternatives.

    As an OS, it’s hard to use, doesn’t follow logical convention’s, is super opinionated about how users should interact with it, and is missing basic usability features that have been in every other modern OS for 10+ years. It’s awesome as a video game console, barely useable as an adobe or autodesk machine, but sucks as a general purpose OS.





  • jemorgan@lemm.eetoLinux@lemmy.mlWhy tile?
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    Yeah, definitely a matter of workflow and personal preference. Nobody wants to convert anyone else, you just ask why people use tiling WM, and people are answering.

    why tile windows at all

    I can answer that pretty comfortably. There are two main reasons, the first is that it’s very common to have to look at two things at once. If I’m taking notes while reading something complicated, or writing some complex code while referencing the documentation, or tweaking CSS rules while looking at the page I’m working on, it’s just way too disruptive to constantly have to switch windows.

    The second main reason (for me) is that a lot of the time, the content of a single window is too small to make use of the space on your monitor. In those cases, if I have something else I’m working on and it’s also small, I’ll tile them. It might be easy to toggle between windows with a hotkey, but it’s strictly easier to not have to toggle, and just move your eyes over. Peripheral vision means that you don’t entirely lose the context of either window. When you’re ready to switch back to the one you just left, you don’t have to touch anything, and you don’t have to wait for the window to render to visually locate where you left off.


  • jemorgan@lemm.eetoLinux@lemmy.mlWhy tile?
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    If you’re only actively using one window at a time, that makes sense, but alt+tabbing through a stack of 8 open applications to go back and forth between something you’re working on and something you’re closely referencing sucks. If your primary workflow for a computer involves that, I honestly don’t understand how someone can live without tiling.



  • jemorgan@lemm.eetoLinux@lemmy.mlWhy tile?
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    You really hit the nail on the head here. Never having to take take your hands off the keyboard, while always having windows take up exactly the right amount of room, is the main reason I hate having to use non-tiling WM.

    And your other point is spot on, too. Any workflow that you use in a standard WM you can also do in a tiling WM, except (imo) more easily. And there are lots of workflows that are agonizing without tiling functionality.

    I want to read this book full screen. Hang on, didn’t that other book say something different about this? I want to open it. This is complex, I want to compare side-by-side. Oh, I get it, I should take notes on both of these. Hang on, I need to look at both books while taking notes. Okay I’m done with the second book but I still want to take notes on the first.

    Slogging a mouse around to click, drag, click, drag, double click, drag, all while repositioning your hands to type, sucks so bad.

    The case is even more clear when you consider that the concept of tiling WMs is just an extension of the game-changing paradigm behind terminal multiplexers and IDE splits.

    It’s just better. There’s probably a bit of an adjustment when you’re first adapting to it, especially if they’re really used to a mouse-centric, window-draggy workflow, which is likely the only reason that people think they don’t like them.


  • jemorgan@lemm.eetoLinux@lemmy.mlWhy tile?
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Honestly, if you’re using 3 monitors, you’re kind of using a single display split into a minimum of 3 tiles.

    Tiling window managers support a workflow with one large monitor that you can split into n tiles whichever way you want without touching your mouse.

    I’m not saying it’s objectively better or anything, but once you get past the learning curve, having to manually size all of your windows is a chore. I love having my browser window open full screen, pressing a hotkey, and having a text editor open next to it taking up 1/3rd of the screen, with the browser resized to fit.

    Mostly, things are full screen, and I love that my WM launches apps in full screen automatically, unless there’s another window open on the workspace I’m targeting.

    And when they’re not in full screen, it’s all handled smoothly without me ever having to take my hands off the keyboard.


  • jemorgan@lemm.eetoLinux@lemmy.mlWhy tile?
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Do you have a small monitor?

    In my opinion, on a >32 4k or 1440p display, the full screen is just way too big for a single window. Which isn’t a problem, because as easy as it is to switch between two windows, it’s even easier not to. Especially for things like having a web browser and dev tools, switching back and forth every time I tweak a CSS rule would be agonizing.


  • I’ve used arch for the past 10 years or so as my primary OS, and it only took 7 or 8 of those years to get the OS set up.

    /s in all seriousness, I kind of get what you’re saying. But I don’t think that having a bad experience is the goal at all though. I think the goal is to provide an OS that lets users decide on exactly what collection of packages they want on their system, and to provide packages that are up to date and unmodified from their upstream.

    Setting up your system additively comes with a cost, though. It’s way less convenient than just installing something that someone else has configured.

    To me personally, I think the one-time upfront cost of setting up arch is less burdensome than dealing with configuration files that have been moved to non-default locations (transmission-daemon on Debian-based distros is one example), packages being seriously out of date and thus missing new features and bug fixes (neovim), and dealing with cleaning up packages if you prefer to use non-default software and don’t want a ton of clutter.

    Definitely valid to prefer a preconfigured system, I just think it’s a misrepresentation to say that the point of arch is to be difficult, or that configuration takes a ton of time for users of arch. Maybe learning to use arch takes longer, but learning to use arch is just learning to use Linux, so it’s hard for me to see that as a bad thing. And it doesn’t take that long to learn, I was more productive in arch after a couple days than I’ve ever been on *buntu, Debian or Mint.





  • Sorry but it’s very uncommon for the people who are making a place into somewhere that the underprivileged hate to be the same people that are moving to other places.

    If you’ve got the power to drive up housing prices in the state that you currently live in, you’re not going to be in the group that’s moving across the country to have a shot at being successful.

    Of course when people can’t earn enough to be successful in CA and move to CO for a better life, the uncreased housing demand in CO is going to bring prices up a bit. But those people aren’t the ones who made CA so expensive. In fact, they’re actively making it less expensive by leaving the state.