49 karma · joined February 22, 2011
Even before the current Libyan revolution there were problems with using .ly domains. E.g., Gadhafi recently made it illegal to use .ly domains for things deemed against Islam.
Sure you could have RPMs or Debian packages tailormade for a specific distribution, but WordPress has the advantage that it's a downloadable package that can easily be (S)FTP'd into a folder on a shared host and run, and it'll work with most hosts. You just can't do that with Django-WordPress.
Again, I use Django/Python more than PHP these days, so it's not a PHP versus Python thing.
But my main point is that, while I understand that the Django Software Foundation has a trademark on the name Django in a specific content, it ought not to be possible to trademark a common name at all.
I'm a big fan of Django, but you'd have to admit that Django's "one virtual host for Python, another for static files" would over-complicate installation. Even on a made-for-Django host like WebFaction it would still be easier to install PHP-WordPress than Django-WordPress.
WordPress certainly doesn't own the name Django, but the Django Software Foundation shouldn't have any particular right to it either if things were fair.
(Oh, btw., I'm a happy Django user - but I'd still be pretty upset if someone decided to trademark my name).
Anyway, didn't mean to give you bad press or anything - I like your product, and as a Dane I think it's great to see Danish startups doing well. Good luck with your product.