Michal Migurski's notebook, listening post, and soapbox. Subscribe to this blog. Check out the rest of my site as well.

Jan 21, 2006 6:21pm

ning blah

I was wondering the same things as TechCrunch:

What happened to Ning? It was the perfect service at the perfect time. Mashups are hot right now. Really hot.

Not sure I agree with the second part, though - Ning didn't seem like the perfect serice for any time. The kinds of people who know what mashups are and how to build them are already conversant in Javascript, PHP, or Ruby. They don't need a Fisher-Price sandbox to play in, especially one that doesn't appear to be as easy as it claims.

How many webservice permutations can there be? Do people even use mashups once the initial wow-factor rubs off? Does Ning's potential developer audience simply realize that the way to independence for a service is to control its own database, and rightly avoid the padded play area?

October 2018
Su M Tu W Th F Sa

Recent Entries

  1. planscore: a project to score gerrymandered district plans
  2. blog all dog-eared pages: human transit
  3. the levity of serverlessness
  4. three open data projects: openstreetmap, openaddresses, and who’s on first
  5. building up redistricting data for North Carolina
  6. district plans by the hundredweight
  7. baby steps towards measuring the efficiency gap
  8. things I’ve recently learned about legislative redistricting
  9. oh no
  10. landsat satellite imagery is easy to use
  11. openstreetmap: robots, crisis, and craft mappers
  12. quoted in the news
  13. dockering address data
  14. blog all dog-eared pages: the best and the brightest
  15. five-minute geocoder for openaddresses
  16. notes on debian packaging for ubuntu
  17. guyana trip report
  18. openaddresses population comparison
  19. blog all oft-played tracks VII
  20. week 1,984: back to the map