Re:New MacBook Pro outsold every competing laptop in just fi...
by alasdair_ on Wednesday November 09, 2016 @05:48PM
(#12915584)
>I am personally appalled that 16GB could be considered too little memory for developer workloads
It depends what you are developing. If I am debugging, I often have to spin up Unity, plus a crapton on 3D models and assets, plus the server which is a bunch of VMs, plus IntelliJ. This is in addition to Chrome and slack. It's okay on 16GB but I occasionally get issues and a couple of years from now this will likely get worse.
I am personally appalled that 16GB could be considered too little memory for developer workloads (except for maybe some very specialised ones). While the Apple II with 48KB was a bit cramped, even an Amiga with 512k + 2MB RAMDisk was pretty decent, never mind the workstation-class NeXT cube with 16 or 32MB. (IIRC, developers at NeXT had 8MB machines, with compiles farmed out to servers, in order to "encourage" efficiency). I also developed significant Java server software on a 12" PowerBook G4.
Of course, the reality is that Xcode with clang/LLVM based tooling and its dictionary-based programming style sucks up RAM and CPU like you wouldn't believe, and various other decisions have been made in favour of recompiling/reindexing the world whenever possible. Swift takes that direction and dials it up to 11.
Anyone interested in more efficient dev tooling? Factor 10-100 improvements in performance are well within reach. Sub-second rebuild instead of minute+, MacBook/iPad plenty fast enough. etc.