5 ms·
I keep seeing people say things about how the Mac is sidelining serious developers and content producers, but I haven't seen any actual argument as to why this
by zepto 10y ago
I keep seeing people say things about how the Mac is sidelining serious developers and content producers, but I haven't seen any actual argument as to why this is so. Can you explain?
- trurl 10y agoBecause serious developers require computers with more horsepower (CPU, GPU, memory, etc.) than Apple is providing? 16GB is nowhere near enough for my work. And I can't seriously justify buying a iMac or MacPro at this point when their hardware is so out of date.
- eknkc 10y agoNot arguing, just curious. What type of work are you in?
- trurl 10y agoI am building a next generation database system.
- grzm 10y agoSounds interesting! What system are you currently using? What limitations are you running into? What do you envision the system running on in production?
- trurl 10y agoIf you mean my development computer, I use a 2012 rMBP with 16GB RAM. For production we generally run on EC2 or GCE. The biggest limitation is RAM, but in the near future we may start using the GPU too. Between the database, middleware above the database, an IDB, a web browser, etc. macOS decides to start compressing pages rather aggressively when I run unit tests. If the IDE gets compressed, pretty much the only solution is to restart. I could switch to Linux development, but aside from Linux laptop support generally being poor, macOS just works so I can spend more time working instead of fighting with my computer's configuration. Still, I am very seriously considering getting a Linux desktop in the near future, because I'm just tired of waiting for Apple.
- grzm 10y agoThanks. My development machine is a 2015 13" MBA/8GB. I'm pretty satisfied with it as a development box. (Though I do need to figure out some performance issues in my integration test suite). Of course, it sounds like your development needs are quite different than mine :) I wonder what the next round of iMacs will look like. If you're looking at a desktop system anyway, perhaps they'll be available with larger memory options. As I understand it, the memory limitation on the new MBP is due to the chip choice, which in turn was chosen with energy efficiency in mind. That shouldn't be a driving factor in the iMac. But then again, when will the next rev of iMacs come out? I hope you're able to find a system that suits your needs!
- jasonjei 10y agoTouchBar killed the tactile ESC key. People using vim or BootCamp and/or Linux, Windows, VMware, or Photoshop are in for a more difficult ride. So instead of having access to ESC/Func keys, we can type emoji or use Apple Pay. The hardware on all Macs are updated on a very infrequent basis as mentioned in the article. GPUs sold with machines today are often the same as ones sold years ago. Apple killed their external monitor option.
- trurl 10y agoI really think too many people are making a big deal of the TouchBar. I'm a vim user, and when the first rumors of it surfaced earlier this year I switched ESC to capslock and after a day or so adapted just fine. I don't know that I really need any of the things TouchBar offers, but it seems to be unreasonably vilified without no one actually using it. For me the key issue is the performance, which no amount of key remapping can solve.
- jasonjei 10y agoI'm just wondering how one will install certain OSes if the Func keys aren't usable during OS install in Boot Camp. I don't remember being able to remap an installer hotkeys easily. Maybe Apple doesn't want that demographic, or perhaps we'll have to connect a USB-C keyboard. Boot Camp drivers are also terribly out of date.
- threeseed 10y agoBoot Camp has already been addressed though. The function keys will be shown and since Touch Bar is running WatchOS it should be easily possible to show them without drivers.
- jasonjei 10y agoI read that there is an independent ARM processor controlling TouchBar. Is there solid proof the TouchBar reverts to Func keys when no OS has initialized/rendered keys to the TouchBar?
- danjoc 10y agoI'll sum up the points I've seen for the 2016 Macbook Pro. 1) No esc key or fkeys. These are pretty important for vim, and vim is the defacto editor on most Linux systems. If you want these keys, you have to accept the lower end dual core CPU and no discrete GPU. 2) 16GB of RAM, not really enough for running multiple VMs. 32GB has been common for years from other manufacturers. Phil Schiller responded that this was to conserve battery life. 3) Skylake. This CPU is old. Kaby Lake has been shipping since late August. It's a bit of a stretch to call a laptop "premium" or "pro" when it ships with the last generation hardware. 4) GPU. Same gripe. NVidia is the undisputed leader in GPUs. Shipping a Radeon which is half the speed of a comparable NVidia offering is really disappointing. 5) Magsafe. They removed Magsafe in favor of USB-C charging. Great for Apple repair and replacement sales, not so great for end users. 6) Price. Everyone expects to pay some premium for an Apple, but this round is really excessive. They've made it worse by axing the lower priced Macbook Air line, so the least expensive model available now is a $1299 Macbook, and that's an even older 5th generation Broadwell CPU model they've been selling for nearly two years now.
- majewsky 10y ago> 1) No esc key or fkeys. These are pretty important for vim, and vim is the defacto editor on most Linux systems. Ooohhh, I can already see the angry complaints from Emacs users. More seriously though, vim doesn't rely on F keys at all. (The only default function mapped to an F key is F1 for help, which is only there to assist newbies AFAICT.) The F keys are useful as a blank slate for one's own mappings, though, so a lot of individual vim users (me included) might be upset about their favorite functions gone. The F keys are of much bigger importance in Xcode, where F6/F7/F8 are the default bindings for stepping during debugging. (I cannot comment on this myself as I'm from the printf-debugging camp, but a lot of people pointed to this concrete function in HN commentary in the past few days.)
- thatswrong0 10y ago> 4) GPU. Same gripe. NVidia is the undisputed leader in GPUs. Shipping a Radeon which is half the speed of a comparable NVidia offering is really disappointing. This one is understandable - the AMD 450/455/460 all fit within a 50W TDP. The Nvidia 1060M is at 80W... way too high. The 1050M should be 50W, but it won't be out until early 2017. The timing of all of this seems weird to me. Since Apple already waited so long to release this update to begin with, would it have killed them to wait just a bit longer to be able to integrate Kaby Lake and the mobile Nvidia cards?