8 ms·
ahem MorkDB. There's tons of code in Mozilla that isn't necessary to do the one job the browser was built for. I don't need code that manages bookmarks. At al
by mondoshawan 11y ago
ahem MorkDB.
There's tons of code in Mozilla that isn't necessary to do the one job the browser was built for.
I don't need code that manages bookmarks. At all. I don't need code that stores history for years. Honestly, I don't /want/ cookies persisted /at all/. I don't need themes to browse the web, and a reorganizeable UI is /never/ what I'm looking for in a browser.
I don't need WebGL. I don't need Canvas. Hell, I definitely don't need syncing of all this extra bloated data around to services somewhere in the 'net, either. Frames? What about floating frames?
Half this stuff is better left to tools that are built for it, the other half is junk I don't need, or is junk that actually creates more problems than it solves.
- ZenoArrow 11y agoThen use something else. It's not like you don't have a choice. https://en.wikipedia.org/wiki/List_of_web_browsers https://en.wikipedia.org/wiki/List_of_web_browsers Based on your stated requirements, perhaps you'll like Dillo. http://www.dillo.org http://www.dillo.org
- mondoshawan 11y agoI think you misunderstand. The parent was asking for examples of bloated code. I was providing examples. I actually /do/ use other browsers like Midori, w3m, and surf. The problem doesn't disappear, though, because it's up to all of us writing code to be better at it.
- ZenoArrow 11y agoNot all code bases need to be minimal to be valid. Some people like having the features you class as superfluous. So long as you have the option to choose software that suits your taste there's not really much of a problem. I, for one, am glad that the web continues to evolve beyond its original design, clearly that's not something you're as interested in, both viewpoints are valid.
- mondoshawan 11y agoSo my point here isn't that I feel those features are superfluous, but that that including them wholesale into the web browsing application directly is bloat -- it would be better served to produce separate applications specialized for those features. Bookmarks, for instance, can be handled in a much cleaner and portable way than isolating them to the specific browser implementation. The same can be said for history, authentication, and so on. Also, to be fair, I wasn't arguing for minimal codebases -- that was your point. I was providing examples for the GP.
- XorNot 11y agoAnd this is where I'm bored with bloat rants. "Software X is bloated! <lists 5 common features everybody uses daily>"