My point was: When running a 5GB protools session with say 150 native plugins, the 32 bit system pretty much shuts down as protools can only access up to 4 gb of ram on 32 bit. With 64 bit, I can access all 16GB of my ram and I can run the same session with 10x as many native plugins without causing any delay in the session that I cannot internally compensate for.

For web design, you want the smallest files you can for load time, this is completely backwards from film or audio or photography because, generally, you want the highest resolution raw files you can get, that what I meant by lightweight. And sublime text/python launcher/idle doesn't fuck with protools/ableton/logic/cubase as far as ram/processor demand goes(also my point to lightweight). Maybe adobe's coding software is more demanding...? Most DAWs recommend a minimum of 4GB of ram, and if you run a session with a lot of vsts/plugins, 4GB does not go very far.

If you think you can design better software for recording audio that would be less demanding, you should, you could make a ton of money off it. But I am assuming the past 20+ years of software development that have gone into programs like protools and cubase probably are doing about as good as they can, and the 64-bit processing addition was the next step. PT is starting to do cloud stuff so we'll see how that goes.