5 ms·

http://news.ycombinator.com/item?id=2061877 http://news.ycombinator.com/item?id=2061877 "The obvious answer is to rewrite WordPress with Django" Done.

by yan 16y ago

skbohra123 16y ago
Ease of installation is one of the biggest SOP of WordPress. I am sure anything written in Py would not have that level of ease for common developers, at least for a few years to come and it become more tough in shared hosting environment.
- Ixiaus 16y ago
  Au contraire - it is the implementation details (create database tables for you? handle install exceptions gracefully? blablablabla) and not the platform (in the case of PHP/Python/Ruby/Perl from personal experience) that makes installation "easy". There are a large set of shared hosts that boast Python and Ruby support - fact of the matter is, WordPress exists and it was written in PHP and nobody from the other language camps has cared to do anything like it in x language. No need to go sowing seed like this!
  - alloallo 16y ago
    The platform does make a difference in this case. With the way PHP is set up on most servers, you can have static files and dynamic files (PHP files) in the same folder (although you'd probably separate them into subfolders). This makes everything easier installation-wise. 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.
    - Ixiaus 16y ago
      I still disagree. I don't use Django so I actually don't know what you have to go through in order to install it but a python app can be packaged and installed on a shared host with mod_wsgi installed. All you need is an index.wsgi to act as your front controller. Setting that up? You just have to install a python egg in the app directory and you should be good to go. Like I said, it's implementation details - a python application could be made easy-to-install. It's just that no one has built a special purpose application with a single minded install path (Django can be self-hosted, mod_python, or mod_wsgi but it is a framework and not an application in the sense that WordPress is an application and CakePHP is a framework) that is relevant to WordPress, closest probably being Plone.
      - jdunck 16y ago
        Your level of knowledge in administration is not common. PHP wins on deployment because every $5 host your average beginner programmer uses already has PHP on it, and deploy is just ftp/sftp. By comparison, a beginner in python will probably also need to learn some *nix and/or get a root account. When wide acceptance is the goal, even small frictions can be material.
        jrockway 16y ago
        Uh, nope. You definitely don't need root to use Django.
        jdunck 16y ago
        I know. I think you're missing the point. The fact that one may make an informed decision does not change the fact that many make uninformed decisions and judge the situation based on their perception rather than independent reality. This matters, facts or no.
        Ixiaus 16y ago
        In a previous comment I conceded the fact that some trappings of an excellent Python deployment solution would require more knowledge than is common to the average "I want a site that I can post content to" user. However. I still think a well engineered application that could cater to many of the $5 hosts' python setups could be just as easy to setup as a PHP app.
      - alloallo 16y ago
        Since the framework and the server(s) can be set up in a multitude of ways (including two-server setups with Apache serving Django and nginx serving static files), I'm finding it really hard to believe that you'd be able to distribute a one-size-fits-all Django-WordPress egg. 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.

http://news.ycombinator.com/item?id=2061877 http://news.ycombinator.com/item?id=2061877 "The obvious answer is to rewrite WordPress with Django" Done.

by yan 16y ago

http://news.ycombinator.com/item?id=2061877 http://news.ycombinator.com/item?id=2061877 "The obvious answer is to rewrite WordPress with Django" Done.

skbohra123 16y ago

Ease of installation is one of the biggest SOP of WordPress. I am sure anything written in Py would not have that level of ease for common developers, at least for a few years to come and it become more tough in shared hosting environment.

Ixiaus 16y ago
Au contraire - it is the implementation details (create database tables for you? handle install exceptions gracefully? blablablabla) and not the platform (in the case of PHP/Python/Ruby/Perl from personal experience) that makes installation "easy". There are a large set of shared hosts that boast Python and Ruby support - fact of the matter is, WordPress exists and it was written in PHP and nobody from the other language camps has cared to do anything like it in x language. No need to go sowing seed like this!
- alloallo 16y ago
  The platform does make a difference in this case. With the way PHP is set up on most servers, you can have static files and dynamic files (PHP files) in the same folder (although you'd probably separate them into subfolders). This makes everything easier installation-wise. 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.
  - Ixiaus 16y ago
    I still disagree. I don't use Django so I actually don't know what you have to go through in order to install it but a python app can be packaged and installed on a shared host with mod_wsgi installed. All you need is an index.wsgi to act as your front controller. Setting that up? You just have to install a python egg in the app directory and you should be good to go. Like I said, it's implementation details - a python application could be made easy-to-install. It's just that no one has built a special purpose application with a single minded install path (Django can be self-hosted, mod_python, or mod_wsgi but it is a framework and not an application in the sense that WordPress is an application and CakePHP is a framework) that is relevant to WordPress, closest probably being Plone.
    - jdunck 16y ago
      Your level of knowledge in administration is not common. PHP wins on deployment because every $5 host your average beginner programmer uses already has PHP on it, and deploy is just ftp/sftp. By comparison, a beginner in python will probably also need to learn some *nix and/or get a root account. When wide acceptance is the goal, even small frictions can be material.
      - jrockway 16y ago
        Uh, nope. You definitely don't need root to use Django.
        jdunck 16y ago
        I know. I think you're missing the point. The fact that one may make an informed decision does not change the fact that many make uninformed decisions and judge the situation based on their perception rather than independent reality. This matters, facts or no.
      - Ixiaus 16y ago
        In a previous comment I conceded the fact that some trappings of an excellent Python deployment solution would require more knowledge than is common to the average "I want a site that I can post content to" user. However. I still think a well engineered application that could cater to many of the $5 hosts' python setups could be just as easy to setup as a PHP app.
    - alloallo 16y ago
      Since the framework and the server(s) can be set up in a multitude of ways (including two-server setups with Apache serving Django and nginx serving static files), I'm finding it really hard to believe that you'd be able to distribute a one-size-fits-all Django-WordPress egg. 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.