RemoteIndian

I would contest macbooks placement on that list. The couple of years I used a mac, I hated it.

What was that thing which makes a bad experience for you? <@U8Z3Q3TQR>

Lots, but the biggest pain was window management probably. Worse than even windows. Need thirdparty apps/daemons to even do simple window snapping to half screen without going crazy.

Atleast mine had function keys unlike newer models. A lot of my workflows are built arounf dunction key shortcuts.

And the bottom left cornermost key being a fn key on most models. Absolutely insane - but this might not be a problem for someone who starts off on a mac.

Commandline tools being non gnu versions - they won't accept switches at the end. Outdated tools.. It's close enough to give a linux like feel but has enough differences and pain points to rake. No package management - brew is like a bandaid, but atleast thank god for bandaids.

I am not a mac user but I have seen a lot of videos on Youtube and I think mac do have option to split windows

&gt; Commandline tools being non gnu versions - they won't accept switches at the end. Outdated tools.. It's close enough to give a linux like feel but has enough differences and pain points to rake. No package management - brew is like a bandaid, but atleast thank god for bandaids.

Not sure if I understand this message.

There are options, but they are not good. For something as simple and common as having two side by side windows, you need to jump through too many hoops

<https://remoteindian.slack.com/archives/C6M8YKK96/p1556421864031800?thread_ts=1556345136.026000&amp;cid=C6M8YKK96>

Ever tried doing `ls something`, only to remember you need an additional switch, say `-l`?

On gnu ls, you can do ls something -l. Just up arrow, add switches at end. Ls on mac won't accept it. It is anal about having switches before arguments.

Not just ls, every single utility that's bread and butter - has the same issue. There's a fix, you can install gnu versions and shadow them using brew - but it's another pain point. You can't just pickup a colleague's machine for a short task/explanation without having to curse osx.

It might be better to run the system on which your code is eventually going to run. For backend devs, that means running linux in a VM. But that costs memory.