NullVoxPopuli / NullVoxPopuli/website

Why a Mac is not for me

Open
#154 8 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
1
Forks
4
Avg merge
8h 59m
Merged PRs (30d)
1

Description

If you're thinking about pushing mac usage on non-mac users, consider these frustrations.

Software

  • If primarily using a desktop, the mac will be used in clamshell mode:

    • External Keyboard and Mouse (non-apple) are poorly supported, and don't wake the machine.
    • Have to open the laptop (so it can't be stowed away) so you can login / unlock the screen (this is a big problem as well, since the mac laptop has so few ports on it, and has to have things plugged in on both sides (left: power, headphones. right: keyboard, monitor (HDMI))
  • Fullscreen mode is incorrect, it creates a whole new desktop, and ruins your spacial mapping of the virtual space by placing windows out of order. Fullscreen should overlay on the current virtual workspace.

  • All hotkeys are wrong. This goes beyond copy/paste/cut and swapping command for control. the home/end end of word / beginning of word keys are wrong in MacOS.
    Misaligned hotkeys cause worse productivity overall, because the misalignment between OSes causes worse habits to develop because the wrong behavior keeps happening (for what is expected -- for example, using arrow keys))

    • home goes to the beginning of the page - should go to start of line
    • end goes to the end of the page - should go to the end of the line
    • control-right/left should go to the end/beginning of a word, instead, they go to the end/beginning of the line.
  • Default bash is ancient. v3, when current is v5. v3 was released 20 years ago. (have to install bash from brew or similar)

  • If you switch from zsh to bash, the built in terminal tells you to switch back, and you have to add to your profile

  • No built in package manager -- brew is common tho.

  • The default terminal is really bad

  • Xcode will break every OS update and you have to re-install it.

  • No devtools work without Xcode being installed

  • Every time I wake the mac from a sleep, my hotkeys get disabled, which makes it hard for me to switch virtual desktops to get back to the terminal that re-enables the hotkeys

  • on the lockscreen

    • cannot hit spacebar to focus the password field from the pre-field-visible view, you must use the mouse / move the cursor
  • multi-monitor support

    • can't disable the laptop screen while using an external display without closing the laptop -- this is bad because of aforementioned wake-from-sleep / reboot procedure..

Required Additional Software

  • bash v5+ - because the default bash version is > 20 years old.
  • Yubai - for tree-based tiling and changing how fullscreen behavior works
    • https://github.com/koekeishiya/yabai
    • this provides a fix for fullscreen mode, which I've mapped to F11 (via shkd)
    • Bug: even though this is the best tiling tool out there for MacOS, it has super buggy window resizing behavior, resulting in opposite-sides moving around when you're trying to resize a specific window-boundary
  • SHKD - for scripting hotkeys and remappings
  • JankyBorders - for showing a focus ring around tiled windows
  • Alacritty, because the default terminal is terrible
    • https://alacritty.org/
    • though, even this is slow when resizing a neovim sesh
    • probably a mac performance issue
  • Inconsistently placed window controls make for an annoying time when I do use a mouse
    • chrome
      image
    • activity monitor
      image
    • alacritty
      image
    • iterm
      image
    • terminal
      image
    • vscode
      image
    • discord
      image
    • slack
      image

One off problems?

After an update to MacOS 14.5 (from 14.4),

  • I lost all of my OS-level and Window-level navigation keys
    • my shortcut for opening spotlight is gone
    • I can't focus or move windows to the right (CMD+N)
    • Karabiner seems to be slightly disabled?

Hardware

  • HDMI is not on the same side as power
    • this means that you have to use both sides for plugins, so the laptop can't be used in clamshell effectively unless you can somehow have access to both sides (such as through a wire/mesh laptop holder to stow the laptop out of the way)

I have a lot more, but this is all I had energy to write at the moment. Dealing with mac machines is exhausting.

I'll add to this list as I run in to new things.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue contains a broad list of macOS frustrations but names no website file, page, entry point, or test. First clarify whether this should become website content and agree on a focused scope; done requires an identified destination and an explicit reviewable content change.

Written by the indexing model from the issue text.

Assessment

Tech stack
bash, macos, zsh
Domain
content, developer-experience, documentation, operating-systems, tooling
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.