Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'm actually going one step further.

For _text_, tabs and such somewhat make sense.

For audio/video, they almost never do. I can _listen_ to one stream at a time. I might be able to watch 2-3, but only one's going to be getting any attention, the others are, say, monitored for intrest (something software should be able to do far better than I).

I've argued for some time[1] that "the browser" should be divided into about 4 distinct apps. It's already partway there.

1. Reading / commenting / research. Essentially _no_ remotely-imposed style. Support front/index, gallery, article, and discussion formats, possibly a few others, _whose rendering properties are defined locally_, by the user. Pocket, Readability (which appears all but dead), Instapaper, and Pinboard all fit this model. Arguably emacs as well.

2. An app framework. This is where Chrome is headed, possibly Firefox too.

3. A dedicated commerce app. Privacy, security, feedback, etc., within it. We've got a few candidates in iTunes / Apple Store, Google Play, and Amazon Store. I'd prefer an open version, not sure we'll see it.

4. A multimedia app. Podcasts, streams, and media downloads, with scheduling, queue management, high-level and consistent playback controls (fast/slow, fwd/back, skip), etc. The idea being that only one damned item at a time would be played, and you could control your media from one damned place.

I've been exceptionally dissatisfied with the State of the Web since ~2009.

_______________________________

Notes:

1. https://www.reddit.com/r/dredmorbius/comments/256lxu/tabbed_...



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: