←back to thread

62 points hiAndrewQuinn | 2 comments | | HN request time: 0.619s | source
Show context
Waterluvian ◴[] No.44392689[source]
An assumption I’ve been revisiting is if I really do need to be writing to disk all the time. I can’t remember the last time I actually had a crash or other event where I would have abruptly lost my work.

I’m wondering if I can completely hide away the detail where I can work exclusively in memory (even when I habitually save my code) and “reconcile” as some task I do before shutdown.

In fact, that doesn’t even feel necessary… I git push my day’s work a number of times. None of that needs a local disk. And 64GB of memory was surprisingly affordable.

replies(4): >>44392724 #>>44392748 #>>44392754 #>>44398922 #
1. Jhsto ◴[] No.44392754[source]
I've been running my daily development laptop on 64GB of RAM for 1,5 years. My anecdotal experience is that no, you don't need persistent storage for most things. In fact, often it's in your way -- it clutters the system over time by causing configuration errors and weird undefined program states. When you can just reboot and all works again it's great. Never going back.
replies(1): >>44393137 #
2. pm2222 ◴[] No.44393137[source]
64g ram here as well I mount chromium/firefox cache dir as tmpfs