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?


Sorry, no new comments on old posts.

October 2021
Su M Tu W Th F Sa

Recent Entries

  1. Mapping Remote Roads with OpenStreetMap, RapiD, and QGIS
  2. How It’s Made: A PlanScore Predictive Model for Partisan Elections
  3. Micromobility Data Policies: A Survey of City Needs
  4. Open Precinct Data
  5. Scoring Pennsylvania
  6. Coming To A Street Near You: Help Remix Create a New Tool for Street Designers
  7. planscore: a project to score gerrymandered district plans
  8. blog all dog-eared pages: human transit
  9. the levity of serverlessness
  10. three open data projects: openstreetmap, openaddresses, and who’s on first
  11. building up redistricting data for North Carolina
  12. district plans by the hundredweight
  13. baby steps towards measuring the efficiency gap
  14. things I’ve recently learned about legislative redistricting
  15. oh no
  16. landsat satellite imagery is easy to use
  17. openstreetmap: robots, crisis, and craft mappers
  18. quoted in the news
  19. dockering address data
  20. blog all dog-eared pages: the best and the brightest