4 ms·
Tabbed browsing: a lousy band-aid over poor browser state management (2014)
- dredmorbius 4y agoSince ranting this ranty rant over eight years ago, the most significant changes I've made personally are purchasing a large-format (13.3") B&W e-ink tablet, and discovering the EinkBro web browser, which is as the name might suggest, optimised for e-ink devices. https://github.com/plateaukao/browser https://github.com/plateaukao/browser It's preferable to any other GUI browser on the device (versions of Firefox and Chrome), and even beats out apps such as Pocket which should make for improved readability of Web content on a tablet but which fails to achieve what EinkBro does, most especially in ease and consistency of navigation. (ProTip: touch regions beat gestures by lightyears.) EinkBro does not have a particularly outstanding tab-management interface (though it's markedly better than, say, Google Chrome/Android). It does have a killer feature I've mentioned previously on HN: the ability to save multiple pages to a single ePub document, including updating said document at later points in time. This means the ability to compile a single document with, say, items of current interest, a day's (or week's or month's) reading dump, research on a specific topic, etc. And: when you're done with that particular interest, you can grab and nuke the entire collection in one swell foop. A major failing of tab-based browsers is clean-up, often an all-or-nothing proposition. Or copy the compilation to (an)other device(s), email it to family, friends, or cow-orkers, post to a website itself (mindful of course of the greatest impediment to information interchange ever invented, copyright law). So, Daniel Kau is single-handedly delivering one of the biggest transformations to the browser world I've seen in over two decades, and possibly three. Not as much progress as I'd like to see (it never is of course), but far more than trillion-dollar monopolists seem interested in or capable of executing.
- mikewarot 4y agoAll of this is a lousy substitute for a Memex. At this point, I think the incentives are strongly against them ever appearing, unless someone had a strong anti-corporate bias in their view of the world... A memex would save EVERYTHING by default as it came in, putting it all into a long (month+) buffer... any links to "interesting" material would then cause it to be moved to the local archive. At any point, you'd be able to share your "associative trail" with others, along with ALL of the content referenced. You'd never be forced to deal with a broken link for static content, ever. (Which is why it can't be done... copyright law) The other worst timeline thing we got was HTML - it's not markup, and it's not hypertext. It's embedded formatting with links off the page. You can include images and other things in an HTML "document", why not portions of other documents? (Security, that's why) I want my Memex... it sounds like you're closer to one that I'll ever get, good for you! 8)
- dredmorbius 4y agoYou and me both. That's ... another project I'm working on in a state of abandonment. I've done some digging into the history of the Web browser and how and when it came to have the set of features it does today. A large portion of that seems to have chrystalised with, or at least by the time of, the ViolaWWW browser, an early though advanced application, first released in April 1992. This inludes not only graphical webpage rendering and features such as bookmarks, but frames, stylesheets, and scripting. http://viola.org/ http://viola.org/ See the features list: http://viola.org/viola/vwFeatures.html http://viola.org/viola/vwFeatures.html What Viola, and most other browsers didn't have was the notion of automatically and by default downloading and retaining copies of remote content. There was download-on-demand and caching, but neither are epecially reliable or human-usable. A large part of the reason was simply that disk storage was too expensive and small --- by the end of the 1990s my desktop system still had only 6 GB of storage (over three disks), and that was generous for the time. For text storage, the real threshold is somewhere between 64 and 128 GB, at which time a collection of thousands of books worth of content becomes viable. I'd argue that saving absolutely everything likely isn't useful, at least for specified domains, content, or other criteria, saving in something akin to the Internet Archive's URL-and-time-indexed format could be quite useful. Document embedding or transclusions (of Xanadu fame) seem ... more trouble than they're worth. Though the idea of links that can indicate the specific version and/or signature of their reference could be quite useful. Copyright stands between much of what really should and could exist, and what is permitted. This is most unfortunate.
- mikewarot 4y ago>I'd argue that saving absolutely everything likely isn't useful, at least for specified domains I strongly agree, but spinning disk space is very cheap, and you never know what you're going to want later... so at least a full month of time there before auto-purge seems quite doable for everything 8) I'd build a system such that if you refer to a given file/page in that timeframe, then the reference count goes up, and it gets moved to permanent storage. 8)
- dredmorbius 4y ago
- meesterdude 4y agoNeat! I'm building an app in this space to improve the web browsing experience. Tabs have a purpose and a place, but I think there are some browsing behaviors where tabs are a poor solution - such as when working with collections of browsers, or being able to browse bookmarks more naturally.