Just middle-click to open the "your vote was counted" in a new tab.
But anyway, having Javascript in your browser is not what makes it bloated; Emacs had an embeddable programming language many years before anyone even thought to embed Javascript in a web browser. It is quirks mode + the DOM + bad programming. (Bad programming == using raw C++. A few years ago, Firefox used a lot of memory because of heap fragmenentation. Garbage collection or double-indirection pointers would easily have solved that problem.)
OK fair enough. But bad programming by browser makers has nothing to do with the markup used for web-pages, which is what you were praising with BH's homepage. Quirks mode also has nothing to do with markup and everything to do with browser makers' failure to implement w3c css standards. And wasn't the DOM developed to accommodate demands for client side scripting such as javascript.
So two of the things you cite as contributing to bloat have nothing to do with page design, and without the third (the DOM) we'd give up a lot of client-side scripting functionality, which is exactly the functionality I am arguing isn't worth giving up.
But anyway, having Javascript in your browser is not what makes it bloated; Emacs had an embeddable programming language many years before anyone even thought to embed Javascript in a web browser. It is quirks mode + the DOM + bad programming. (Bad programming == using raw C++. A few years ago, Firefox used a lot of memory because of heap fragmenentation. Garbage collection or double-indirection pointers would easily have solved that problem.)