Where's the line?
For example, I know several non-technical users who use the built-in dev tools to remove the annoying overlays that some sites show, but that don't allow to be hidden without logging in or something dumb like that.
These users don't really know what the DOM is, but they do know that they can open the dev tools, click the node selection button, click on the overlay they want to get rid of, press the Delete key, and now they're able to use the site again.
I think you missed the GP's point. Bookmarks can also be very useful to average users. One man's trash is another man's dev tools or whatever.
Drawing a clear line between what's essential for a browser and what's bloat probably isn't possible for any decent sized group of users.
And, as an (occasional) i3 user, I would not want this, because two browser windows seem to use up far more resources than one window with two tabs. Browsers are almost unusable once a certain number of tabs are open; I can only imagine how badly my computer would operate were the 100+ tabs I have open each consuming the resources required by a separate window.
One person's bloat is another person's feature.
I find this "Give me only what I want" attitude quite frustrating. Perhaps you could argue for a more modular system that disables any given feature, but I would challenge you 8 days a week that bookmarks are a useful tool for most.
And really, bookmarks? How is that a performance hit? Maybe one would say that the "awesome bar" takes cycles to auto-search bookmarks when typing a URL, but you can disable that already.
No bookmarks? You mean one would have to type in every website address you want to go to?
It's so much easier to click on bookmark in the list, and with today's wide monitors, horizontal space is wasted anyway so I keep the bookmark sidebar open all the time.
Browser history search via the address bar is much faster than searching through bookmark folders for a particular page. Even nicer with Vimium where I can just hit "o" and search for what I want. For everything else, I just Google.
History wasn't part of kgwxd's specification (https://news.ycombinator.com/item?id=12442292), though, which just brings back to the central point: when you try to build a browser with the absolute minimum set of features required, you'll find that everyone's minimum set of features is different.
As an aside, I'm looking for this on Android (address bar, tabs and viewport). Habit Browser comes close but is not open source. Basically just a WebView with an address bar and tabs. If anyone has ideas, let me know.
Anyway, you can already use uzbl[1] if you want something minimal.