2 ms·
I don't think there's any correlation at all between whether a startup gets called a "web 2.0" startup and how hard the problems are that they have to work on.
by pg 19y ago
I don't think there's any correlation at all between whether a startup gets called a "web 2.0" startup and how hard the problems are that they have to work on.
Look at Loopt. Seems like a classic, frothy social app. And yet beneath it are very difficult technical problems and horribly tedious negotiations with carriers. Or Justin.TV. What could me more frivolous, right? And yet to get it to work they had to build their own CDN for live streaming. They spent 6 months working round the clock building infrastructure (including custom hardware) before they could even launch.
- cstejerean 19y agoI agree that there are several web applications that require solving hard messy problems. I'm not sure if I would call Loopt a Web2.0 startup, but I agree with the point about Justin.tv The problem however is that a good number of startups that call themselves web2.0 companies are building facebooks apps, Yet Another Social Network, or roll your own web app with Ruby on Rails in 15 minutes.
- pg 19y agoa good number of startups that call themselves web2.0 companies are building [things with no substance] That's no different from Web 1.0. In 1998, people thought all they had to do was create a "portal" for some special interest, and it would be a company. Replace "portal" with "social network" and it's 2008.