4 ms·
If people are using that much for web dev, it scares me, because I don't know if the websites they're building will be useable on a modest machine.
by TazeTSchnitzel 10y ago
If people are using that much for web dev, it scares me, because I don't know if the websites they're building will be useable on a modest machine.
- adamors 10y agoQuick math for you: - Chrome alone eats 2-3GB of RAM - Windows 10 needs at least 6GB allocated in a VM - Slack, Skype, an editor, Firefox etc. take up another 2GB easily. That's just 10-11GB for boring stuff. If you have Photoshop open or sites like Zeplin that consume a lot of RAM you can reach 16GBs easily. No need to be dismissive.
- Ralfp 10y agoIt shouldn't. This is mostly shaving time from assets pipeline, doing more at single time eg. editing design in graphics software that autoexports it to your frontend where its grabbed and served by locally running instance of an web app you are working on, shorter times needed to recreate your data to initial state, shorter times needed to populate your database with test dataset, shorter times needed for you to run your test suite, etc ect. Stuff thats manageable, but you never can't make fast enough.
- randallsquared 10y agoI imagine that most web devs run a version of the server on their local machines, which these days might mean one or more of mariadb, mongodb, couchbase, postgresql, rethinkdb, cassandra, together with redis, rabbitmq, ELK, all the backend services and the API gateway that manages them, consul and/or etcd/kube and/or swarm... It's easier to run the full environment in development than it is to worry about bugs introduced by differences between development and production.