Conversation

The boundary between Web1 and Web2 was so subtle and incremental most people outside of tech didn’t even notice when it was crossed: when IE7 supported XmlHttpRequest in 2008, paving the way for rich UIs, JavaScript supremacy starting with jQuery, and what was then called Ajax.
4
71
I’d jumped onboard just a year earlier, dumping printer research at Xerox to starting the Web2 research at the Webster lab in 2007. HTML5 was a utopian dream, Ajax was a poorly supported design pattern, jQuery was brand new, Rails was viewed with suspicion, Java ruled the lab.
1
21
Again really lucky timing. I hired a student of the creator of jQuery from RIT (dumb luck) and a hardcore Rails guy (a couple of others at the lab dabbled in rails but for fun; serious work was in Java) and between them they really took my half-ass product ideas to the next level
1
18
Compared to that — really a sustaining evolutionary level-up in hindsight — Web2 to Web3 seems like a brute revolutionary disruption accompanied by massive mutual cultural hostility. Everything sacred in Web2 is profane in Web3 and vice versa. Web 1 to Web2 was barely a ripple.
3
25
In hindsight, the 2 products I led (RIP both) were both too early. One would be great for the metaverse today (html5 visual trail maps), the other would fit Web3 perfectly (recursive multilevel services auctions). If I were younger I’d take another run at both.
3
16
Replying to and
My key insight in context to curation and a search engine built on top is that browsing history can be curated more easily with subtraction than something which involves addition. Each person's curated browsing history can become private/public trails.
1
2