Well, there can really only be "betamax" problems when you have a winner-take-all economy. Since these frameworks are just code that outputs (JS|HTML|JSON|etc), there isn't really a way that any framework could become a betamax.
That said, for myself, the Django 1.0 isn't that exciting. What will be exciting is the development from now on. I mean, I've been tracking SVN and so 1.0 doesn't offer me cool new things. It's also just a different community. DHH is great at getting the word out and getting the hype up there. Django is more subdued.
You can't go too wrong with either Rails or Django. Don't worry. Be happy. Be productive.
Attention is zero-sum.
That's the way we like it.
I don't think Django == Betamax, but I do agree it certainly was a quiet release. Hopefully the improvements and the quality of the release will be sufficient to generate some buzz.
There's a conference and party this weekend.
Also, blackjack and hookers.
There are 10500 subscriptions to django-users.
Betamax?
Django just released and that's all.
On the one hand I'm happy because over hyped products tend to be constantly flooded by new users. On the other hand, if a project is too quiet, it tends to lose users to more sexy technologies, and sooner or later, nobody is using it.
I don't want it to turn out that I put my bets on the betamax of the the frameworks.