Re:Why you should build an application (even if it already e...
by mkramlich on Thursday November 26, 2009 @01:12AM
(#962343)
patio's comment made me think of Google Wave.
from everything I've heard about it, I still don't understand what problem it solves that isn't already solved. It feels like a really esoteric use case for hyper-geeky people who for some reason aren't smart enough to use one of the 1000 other hyper-geeky fluffy techno-web-gizmos to do the same thing with already.
Now that I've said this, I'm sure in a year I'll be wave-ified. :)
Re:Why you should build an application (even if it already e...
by derefr on Thursday November 26, 2009 @05:13AM
(#962507)
Think of it this way: pretend email, wikis, and IM clients don't exist. Now, given you can pick between any one of those, or Wave as well, which one thing would you rather come into existence to best solve each of the otherwise-already-solved problems you actually have each day?
Re:Why you should build an application (even if it already e...
by miloshh on Wednesday November 25, 2009 @11:49PM
(#962261)
You have a few examples of the oversupply of solutions for the technically inclined? No offense, I'm sincerely interested...
Re:Why you should build an application (even if it already e...
by tptacek on Thursday November 26, 2009 @12:01AM
(#962272)
I'll try: hosting solutions, bug trackers, wikis, music sharing, "simple" web-based file sharing, "web operating systems", project management products (incl. to-do lists), anything built on Twitter, anything with "platform" in the name, automated testing tools, blogging systems.
Re:Why you should build an application (even if it already e...
by miloshh on Thursday November 26, 2009 @12:16AM
(#962291)
OK, some of these are really meant for technical users (hosting solutions, bug trackers, automated testing tools) but are the companies selling them actually doing badly because of oversupply? Or comparably worse to companies addressing the general public?
This contributes to the perpetual oversupply of solutions from problems suffered by technically-inclined male twenty-somethings. Then you get to try shouting louder than all the other startups so that instead of the technically-inclined male twenty-somethings not paying for the thing the other guy makes they're not paying for the thing you make.
I built something I wanted: a business. It solves problems which were actually experienced by Real People. They also actually pay money for things, which is a nice feature to have in a customer.