This is not really abuse, it's very natural.
Tabs, bookmarks and browser history should be one and the same thing.
This is not really abuse, it's very natural.
Tabs, bookmarks and browser history should be one and the same thing.
I have a really hard time getting back into things. Any state a thing remembers is the opposite of helpful.
For example, I don't suspend laptops, I turn them off. It'd be a waste of time closing what I was doing before because I don't remember where I was earlier and it's easier to start over.
Browser tabs are a current state. If I will want to use it multiple times, I use a bookmark. History is for the rare time I think "wait, I swear I read that earlier".
It isn't just computing, I forget where I was in books and games sometimes and start over too. I can't be the only one.
It's useful too. One time I remembered doing something, found the tab. Sure, it was a 6 year old tab, but it was helpful.
That might be useful some day. toss
I get why it'd be useful, and stretching the capabilities like that means that browsers get more and more useful and efficient. It just doesn't work for me, and that's alright. If you can open 1000 tabs, my 10 are no problem!
I expect a tab to stay in memory, at least in virtual memory, and not need to hit the server if it's in the background for a while and then I click on it again, unlike history or bookmarks.
I expect history to not be loaded in memory, it would be a waste of memory.
I expect bookmarks to show up in search. Searching history is different, history has a ton of useless garbage in it. "Bookmark" means "When I type this, show this one URL before all the other ones that seem relevant".
> I expect bookmarks to show up in search. Searching history is different, history has a ton of useless garbage in it.
There is truly no difference except that some URIs are bookmarked (and maybe also in recent history) and some are not. Either way searching these is just a SQL query against the SQLite3 DB. You really need not worry about the efficiency of the search -- it's fast enough. The table(s) that store these things have enough metadata to enable the kinds of searches you might want to do. Among such metadata is "this is a bookmark" and "this is not a bookmark".
> "Bookmark" means "When I type this, show this one URL before all the other ones that seem relevant".
That doesn't preclude treating it not that differently from history. You really need not worry about those details.
Also, a "bookmark" is more than that: it also has a name, it may be in a folder, it may be in the bookmark toolbar, it may have tags to help you search for it, etc.
I'm also in the group that never keeps more than 10 tabs open, much fewer usually. The idea of having all my bookmarks displayed in a long sequence of tabs sounds horrific to me personally. It would just be an overwhelming amount of information.
I would love it if bookmarks and history were easier to search and retrieve. Having them displayed in a thousand tabs on my screen constantly not so much.
Tabs, I donno, I'm not the target audience for Tabs. I'm on somewhat limited resource hardware, so keeping 100 tabs open is simply not feasible. All browsers run like slugs with 100 tabs open from personal experience.
With four tabs open on Firefox Developer 125.0b9 I have (6) main process groups with (8) further subprocesses for 1075 MB of memory while doing ... nothing.
The tabs are Not impressive. HN (2,text), WP (text), Gmail (text). Adding only Redfin and Facebook jumps me up 500 further MB in resident memory. Two tabs, no actions. How do the landing pages for two major companies eat 500 MB of resident memory statically?...
I'm actually a bit shocked that almost 20 years later and the browser interface is pretty much still the same.
It seems to me in this day & age you have media organization tools (jellyfin? I think it's called?) that just handle everything. I'd love to see some basic AI language model (more of the BERT/gensim flavor likely) that can similarly auto-organize trounces of bookmarks, I have way too many.
The other interesting and increasingly relevant feature towards bookmarks would be the concept of saving them for posteriority, as we know the internet is not forever, whether this means a local save or a ping to archive.org as to say "someone bookmarked this maybe you can hang onto it". The trick of it there is not just capturing all the content of a webpage including videos, but if we say "tabs are bookmarks" then maybe you want to capture the back/forward button pages to a degree.
Anyway that's what my dream browser might look like. Also dream browser powerfully denies browser fingerprinting.
It's pretty opinionated. "Archives" tabs after a pre-set amount of time, uses pinned vertical tabs instead of bookmarks…
[0] https://arc.net/