3 ms·
it is so fucking obvious that this idea is exactly how browsers will work in the future. A browser is going to just be something like node-webkit/webkit/electro
by vonklaus 11y ago
it is so fucking obvious that this idea is exactly how browsers will work in the future. A browser is going to just be something like node-webkit/webkit/electron etc. so compatability won't be an issue, then you just connect to a ton of different clients that are running narrow crawls of shit you are searching for. The browser will then not take you to the page, but just display the information directly without loading a shit ton of js.
You can tag or organize the data locally and cache it, or return it sorted to the nodes which serve it to others. People don't give a shit about webpages for search, they care about information. The web is a big rss feed, and our old feedreader "google" stopped doing that well, and also we pay a massive privacy tax for that now.
I see this happening in ~2 years for really techie people and being standard in 5.
edit: elastic search, webkit, real time, distributed file systems, apache spark, google tensor flow. These ingredients will be used to make the new browser which browses information and returns that information not the actual web pages.
- jsprogrammer 11y agoYes, but there is no reason to wait ~2 years. It can be built now.
- vonklaus 11y agoobviously. I think it will become mainstream with technological people in 2 years. It will take time to, of course, actually be built. Then, have enough data fed into it to actually be useful. That will take about 2 years(ish).