Kind of a tangent, but I am a fan of dynalist using a lot of RAM. It means everything from the document is in the lowest latency state. The extremly low latency of operations is one of the top features that keeps me with Dynalist. Even short millisecond delays from paging data out of RAM would get on my nerves, personally. I know not everyone, or even many, might agree with me here, butthe absolute latency-free flow of using dynalist really helps my productivity. Most software gets on my nerves with those tiny little waits and stutters. People don’t complain when a blockbuster videogame uses a ton of RAM, because they enjoy the experience it enables.
BUT totally agree, if you open 4 tabs, it’d be nice to find a way to use 1x the memory rather than 4x the memory. Not sure how a web developer would do that in Chrome. I know Chrome tabs are notorious for being independent memory spaces.
A blunt solution you can do now is split your document in 4 docments, one for each tab. That would solve the issue. The memory use is proportional to document size.