4 ms·

Vertical tabs in tree structure is currently the best way to use web, especially when you pair it with auto-unloading of inactive tabs. I'm also disappointed th

Vertical tabs in tree structure is currently the best way to use web, especially when you pair it with auto-unloading of inactive tabs. I'm also disappointed that nothing better appeared in last few years. Developers seem to be extremely conservative about UI. With WASM it seems that browsers will take over most of OS functionality and the UI is getting in the way. IMO we should ditch tabs, bookmarks and history. They all implement the same thing - a way to reach a place you've visited before. And they all require to be micromanaged in specific ways. The browser already knows which sites I've visited recently, and all the backtracking and branching I did. This information could be visualized as tree so that I can backtrack to any node and resume browsing on a new branch. The browser should also be doing memory management so that revisiting recent site is as fast as switching to another tab. And while we are at it, why not allow full text search across recently visited sites?

posterboy 9y ago
"the best" is an exageration. The web is named so for a reason: it's a graph, not strictly hierarchical. Which is rather difficult to represent in a list format. For wikipedia e.g. I really want to have a graph instead of a linear history view, in at least 2 dimensions: ordered by time of visit and connection to related articles. I'm kinda ashamed I never got around to make this in 10 years.
wyuenho 9y ago
> MO we should ditch tabs, bookmarks and history. They all implement the same thing - a way to reach a place you've visited before. And they all require to be micromanaged in specific ways. The browser already knows which sites I've visited recently, and all the backtracking and branching I did. This information could be visualized as tree so that I can backtrack to any node and resume browsing on a new branch. The browser should also be doing memory management so that revisiting recent site is as fast as switching to another tab. And while we are at it, why not allow full text search across recently visited sites? Yes! This! Essentially, something like Emacs's undo-tree, but representing the tree in a more compact form, using some variant of D3 or Graphviz's tree layout algorithm.

posterboy 9y ago

"the best" is an exageration. The web is named so for a reason: it's a graph, not strictly hierarchical. Which is rather difficult to represent in a list format. For wikipedia e.g. I really want to have a graph instead of a linear history view, in at least 2 dimensions: ordered by time of visit and connection to related articles. I'm kinda ashamed I never got around to make this in 10 years.

wyuenho 9y ago

> MO we should ditch tabs, bookmarks and history. They all implement the same thing - a way to reach a place you've visited before. And they all require to be micromanaged in specific ways. The browser already knows which sites I've visited recently, and all the backtracking and branching I did. This information could be visualized as tree so that I can backtrack to any node and resume browsing on a new branch. The browser should also be doing memory management so that revisiting recent site is as fast as switching to another tab. And while we are at it, why not allow full text search across recently visited sites? Yes! This! Essentially, something like Emacs's undo-tree, but representing the tree in a more compact form, using some variant of D3 or Graphviz's tree layout algorithm.