2 ms·

> Because it's a fucking website You seem to be aware that web developers need to use, pardon my French in kind, fucking tools to develop a fucking website. Th

> Because it's a fucking website You seem to be aware that web developers need to use, pardon my French in kind, fucking tools to develop a fucking website. The tools—in many cases the very same tools used by non-web developers—don’t magically become lighter weight just because the end product ought to be. Web developers don’t need those tools any less than non-web developers. Chrome (or equivalent) and Slack (or equivalent) and basically any IDE are just as prevalent in many non-web development workflows, and account for just as much demand for resources for those developers. In what other profession would it be a “sad commentary” that the resources needed to do one’s job differ from the resources needed by the product of that job?

nvy 3y ago
What I'm getting at is: unlike running LLMs, 3D modeling, rendering 8K video, or similar tasks, there's nothing inherent to working with html and javascript that demands such huge amounts of memory. Editing a few hundred (even a few thousand) lines of code is not a memory-intensive task. The only reason we are in this current sorry state of affairs is because They(tm) have decided that the proper way to deploy apps is to ship it atop an entire Chrome instance, itself being a notorious resource hog. The web sucks. Desktop apps are now just web apps, and they also suck. It didn't have to be this way.