5 ms·

I'm running a lot of tools in parallel and you need memory especially when you're doing memory tracing and debugging, which is kind of obvious. I mean, when you

I'm running a lot of tools in parallel and you need memory especially when you're doing memory tracing and debugging, which is kind of obvious. I mean, when you load 4 GB memory dumps, you tend to run out of memory pretty fast ;-) Couple this with a compiler that watches for file changes and constantly recompiles stuff in the background, runs tests and so on and with a full fledged IDE, like IntelliJ IDEA, with a browser loaded with stuff and things get painful. I'm working on a MacBook Pro with 8 GB of RAM and it constantly swaps to disk. Thank heavens I have an SSD, because otherwise it would have been unusable. As to your response, dude, this attitude of "you're holding it wrong" is iconic of Apple. I mean I don't know what people are talking about, as Steve's spirit is very much alive at Apple and within its user base and I never liked it.

lazyjones 10y ago
> I'm working on a MacBook Pro with 8 GB of RAM and it constantly swaps to disk. Thank heavens I have an SSD, because otherwise it would have been unusable. Don't get me wrong, but if you're doing this kind of serious development, perhaps a laptop isn't the best choice? The iMac 5K takes 64GB these days. Perhaps I'm just too old and can't see why a laptop is a superior development environment compared to a desktop with decent 27" display, mouse and keyboard... Are you traveling much?
- systemtest 10y ago
  Because then I'd have to buy an iMac 5K for home and one for the office. And sync all my files and preferences between the two.
  - lazyjones 10y ago
    Or, you could buy a beefy desktop at work and use Apple Remote Desktop / VNC on your laptop at home.
    - bad_user 10y ago
      If you've ever used Remote Desktop / VNC, you know that it just doesn't work. The latency of the network communication is too great within your own local network over Wifi, enough as to be a pain in the ass for work, let alone when communicating over the Internet. And you'd better not be on a metered Internet connection, because these high-resolution screens will produce data like crazy. I know it sounds cool in theory, but it just doesn't work, at all. Basically Remote Desktop / VNC is only useful for short sessions and/or debugging, not for work, unless you're in text mode with SSH, vim, screen, tools like that ;-)
      - lazyjones 10y ago
        >If you've ever used Remote Desktop / VNC, you know that it just doesn't work I wrote a DOS VNC client in 1999 for my ThinkPad 720 (to access my Sun workstation at work from home), so my mileage varies. ;-) We had lower screen resolutions and color depths then, but also slower connections. I've used VNC quite a bit over the years but admittedly, for working from home I used ssh (because it was sufficient and I use vi). FWIW, practicality greatly depends on your type of work. Typing text in an IDE and running the occasional debug session should be no problem due to the way screen updates are transmitted, anything graphics-heavy will be frustrating.

lazyjones 10y ago

> I'm working on a MacBook Pro with 8 GB of RAM and it constantly swaps to disk. Thank heavens I have an SSD, because otherwise it would have been unusable. Don't get me wrong, but if you're doing this kind of serious development, perhaps a laptop isn't the best choice? The iMac 5K takes 64GB these days. Perhaps I'm just too old and can't see why a laptop is a superior development environment compared to a desktop with decent 27" display, mouse and keyboard... Are you traveling much?

systemtest 10y ago
Because then I'd have to buy an iMac 5K for home and one for the office. And sync all my files and preferences between the two.
- lazyjones 10y ago
  Or, you could buy a beefy desktop at work and use Apple Remote Desktop / VNC on your laptop at home.
  - bad_user 10y ago
    If you've ever used Remote Desktop / VNC, you know that it just doesn't work. The latency of the network communication is too great within your own local network over Wifi, enough as to be a pain in the ass for work, let alone when communicating over the Internet. And you'd better not be on a metered Internet connection, because these high-resolution screens will produce data like crazy. I know it sounds cool in theory, but it just doesn't work, at all. Basically Remote Desktop / VNC is only useful for short sessions and/or debugging, not for work, unless you're in text mode with SSH, vim, screen, tools like that ;-)
    - lazyjones 10y ago
      >If you've ever used Remote Desktop / VNC, you know that it just doesn't work I wrote a DOS VNC client in 1999 for my ThinkPad 720 (to access my Sun workstation at work from home), so my mileage varies. ;-) We had lower screen resolutions and color depths then, but also slower connections. I've used VNC quite a bit over the years but admittedly, for working from home I used ssh (because it was sufficient and I use vi). FWIW, practicality greatly depends on your type of work. Typing text in an IDE and running the occasional debug session should be no problem due to the way screen updates are transmitted, anything graphics-heavy will be frustrating.