3 ms·

I'm not crunching big data in development or doing much with graphics (other than occasional faffing on some image editor). What I'm running is a lot of local s

I'm not crunching big data in development or doing much with graphics (other than occasional faffing on some image editor). What I'm running is a lot of local servers. Each server has overhead even if you are only storing one byte of data. ie I'm running Rails, MySQL, Elastic, Redis, Nginx, Memcached, and in some cases, multiple instances (dev, test, and multiple shards) And then the usual OS requirements - Vim, 250 browser tabs, Slack, Hangouts, etc. I'm sure there are all manner of optimisations and assumptions that could cut things down, but I'd rather the big manufacturers upgrade their RAM capacity every few years so I can focus on a dev environment that's a good approximation for prod.

wooter 9y ago
Dev-Prod parity is probably the best reason to want the extra power, but then you're just limiting your software to the lowest common denominator between mobile computing and a server farm. At the end of the day, if you want to take advantage of the big guns, you will have to sacrifice mobility or parity and spend some good time on devOps. And even an extra 16GB won't get you around that. Also, 250 tabs? dayum. I don't know how anyone could effectively use that many tabs. I don't think thats what browsers/laptops are designed for. My mind memory of just the tabs would be saturated long before the laptop's.
- StillBored 9y ago
  I frequently have that many tabs open because I use them as lighter one-shot bookmarks (although see onetab). Basically things that I need/want to refer back to once or twice but don't want to bookmark. So they tend to stack up until I go through them and close out the stuff I'm no longer interested in. Really I think FF/etc should probably just garbage collect most of them if they haven't been active for a few days.

3 ms·

I'm not crunching big data in development or doing much with graphics (other than occasional faffing on some image editor). What I'm running is a lot of local s

by mmahemoff 9y ago

wooter 9y ago
Dev-Prod parity is probably the best reason to want the extra power, but then you're just limiting your software to the lowest common denominator between mobile computing and a server farm. At the end of the day, if you want to take advantage of the big guns, you will have to sacrifice mobility or parity and spend some good time on devOps. And even an extra 16GB won't get you around that. Also, 250 tabs? dayum. I don't know how anyone could effectively use that many tabs. I don't think thats what browsers/laptops are designed for. My mind memory of just the tabs would be saturated long before the laptop's.
- StillBored 9y ago
  I frequently have that many tabs open because I use them as lighter one-shot bookmarks (although see onetab). Basically things that I need/want to refer back to once or twice but don't want to bookmark. So they tend to stack up until I go through them and close out the stuff I'm no longer interested in. Really I think FF/etc should probably just garbage collect most of them if they haven't been active for a few days.