3 ms·
As an enteprise and private user of mac, I think there's one thing that you didn't touch. Mac no longer serve as a 'development machine'. For instance, in my l
by Aperocky 7y ago
As an enteprise and private user of mac, I think there's one thing that you didn't touch.
Mac no longer serve as a 'development machine'. For instance, in my line of work I have a 64 core cloud dev box that I use, my mac are used to connect to that box and serve as a frontend. Granted, there are still workflows that happen on the mac (i.e. IDEs for language that can't really work without one), but more and more things happen directly in the dev box, somewhere far away from home.
And I think that will be the future - that's why I think the air is a great machine. Top out the user experience and design at the cost of performance, which even the enteprise customers are starting to need less.
- secabeen 7y agoThe air is a great machine if you don't need performance, until you suddenly do. I have a user with the top of the line air from like 2 years ago, and it won't run Zoom virtual desktops. Zoom just says the cpu is too slow. So people can think things are okay, but when they aren't, you're stuck.
- DeathArrow 7y ago>For instance, in my line of work I have a 64 core cloud dev box that I use I prefer to use a local box for faster feedback. But even if someone would prefer using a remote box, they can also use a Windows laptop to do the same thing.
- Aperocky 7y ago> use a Windows laptop to do the same thing. That's where all the bad things come in. I can use all the normal commands in mac or at remote, with almost no change. The aliases work on both machines (I use .. 2 to go up 2 parent dirs, etc). I usually don't use UI with the exception of the browser, and I can't see how that can work in Windows.