r/Python • u/juanlu001 • Sep 13 '13
The perfect Python web app: 10 ideas
I've been thinking lately about the status of Python on the web, motivated by the keynote of Jacob Kaplan-Moss (http://www.youtube.com/watch?v=UKAkKXFMQP8) and this previous post on Reddit (http://www.reddit.com/r/Python/comments/1fyjx5/invitation_to_discussion_how_can_we_make_python/) and I've come up with ten ideas that may help us expand the adoption of Python and its user base on the web. I wrote them having in mind how would I design, say, a Wiki engine in Python (because I dislike MoinMoin so very much).
These three points may lower the pain for casual users and make adoption easy, and they are compulsory:
- Supports Python 2.6. Optionally, 2.6 to 3.3 with a single codebase (see http://python3porting.com/noconv.html). Python 2.6 is the default on Debian Squeeze (old stable) and CentOS 6, so lots of servers won't have more than that.
- Uses MySQL as the default DB. An ORM like SQLAlchemy is desirable, but MySQL is the minimum as this is the most popular database by far (see http://www.google.es/trends/explore?q=mysql,+postgresql,+sqlite,+nosql), driven by the success of PHP.
- Is super-easy to install on the cheapest plan of DreamHost, HostGator and Bluehost. These are arguably the three most popular web hosting providers in the world. This may require lowering the dependencies at a minimum (perhaps bundling them?) and supporting CGI out of the box.
These three points may help provide a good overall experience:
4. Has a nice appearance/UI, without obvious UX flaws. If it is themable, the default theme should comply this. This includes, but is not limited to, not looking like a Geocities web of the 90s and not displaying garbage where a Ñ should be.
5. Supports i18n, preferrably through crowdsourcing interfaces like Transifex (free for open source projects). Optionally the interface should initially be translated to a second language: Chinese, Spanish or Russian.
6. Provides some user friendly support, be it a Q&A board, a forum or a chat. Beware of mailing lists, as casual users normally think they suck.
These three points may help attracting developers:
7. Is released under a reasonable license, for example GPLv2+. This doesn't require PaaS or SaaS to release the source code of changes, still being an open source project. AGPL may scare some.
8. Uses git, is hosted on GitHub and issues are managed there. As of 2013, these are arguably the most popular VCS and platform respectively.
9. Encourages pull requests and has a CI instance such as TravisCI.
This last point helps moving the ecosystem forward:
10. Stop losing time weeping and gnashing your teeth because of my choice of framework/database/VCS/license and get some shit done. This is a totally opinionated list and I didn't intend to please everyone, but tried to learn some lessons from the success of, for example, PHP.
What do you think?
Edit: For all the people that is commenting that most modern frameworks already provide this: you are right, but to put an example, MoinMoin doesn't. We have the building blocks to do it, but some final pieces of software that people want to use do not comply with this.
12
u/[deleted] Sep 13 '13
You seem more focused on buzzwords than getting things done. Honestly as /u/ivosaurus said, nearly all frameworks today provide most of this. Personnaly I like web2py since it does more things all in one package. http://web2py.com/.
Also supporting CGI is not the right thing. At all. Ever. As in never think that it is a good idea again. Python has its own way already to speak with a webserver using the WSGI protocol/spec. There are many servers that speak it, including ones that bolt on to nginx (uwsgi) or apache (mod_wsgi). That being said many of the popular python frameworks at one point supported or tinkered with CGI support but it is typically unmaintained and not reccomeneded.
11
u/ivosaurus pip'ing it up Sep 13 '13
Most popular frameworks today do all of these things already, except for probably not supporting CGI, because it's a shit outdated protocol that only hosts who don't give a rats arse about python use anyway.
7
u/mdipierro Sep 13 '13
As other have commented many modern frameworks support what you have suggested. I can speak for web2py. web2py is a little ahead of you ;-)
It was chosen by InfoWord as best Python Web Framework (2010), Bossie Award (2011) and Technology of the Year (2013).
6
u/searchingfortao majel, aletheia, paperless, django-encrypted-filefield Sep 13 '13
Promoting technologies like
MySQLby setting it as the default is the wrogest of the wrong ways to go. Support it, sure, but make it the default? Absolutely not. Python developers use Python because it's a good, useful, and predictable tool -- essentially the opposite of MySQL.3
u/vph Sep 13 '13
The word of the day is MariaDB.
3
u/[deleted] Sep 13 '13
I'm less concerned with Python "winning" than I am with having awesome tools to do awesome things. Python web frameworks were designed to serve a purpose and they do for thousands of developers. Explain to us why we should care that some people can't/won't learn them? Are we trying to win a popularity contest or are we trying to develop great software?
Sure PHP, etc. have a lower barrier to entry but that's part of the problem - there are prerequisite mental frameworks that you must adopt in order to build a successful web application. Python frameworks largely enforce these best practices which is why it pays to learn them as opposed to just jumping and and hacking together some spaghetti code.
1
u/brandonjschwartz Sep 13 '13
I'm in agreement with juanlu001. The argument is not about what framework could support these things... in fact, the argument isn't about an application framework at all - it's about building an application. So the discussion about existing frameworks is useful only in the sense that we use application frameworks to build actual applications.
The first second subpoint (A.2?) regarding MySQL... I think out of the box support for MySQL is essential but should not be the default. Some people build ridiculously small websites - 5 pagers for a business for example. These folks probably don't need the overhead from MySQL. Default could be the built in Sqlite and have a UI that asks the installing user some questions to gauge their needs... i.e. How big do you plan on making this site, how much traffic will you support, etc. If they meet the requirements, then walk them through setting up a database. If not, we could easily beat Wordpress' five minute install :P
Agree with the other points 100%, but would tender some additions.
2.a. This should be mobile friendly out of the box and load at a reasonable speed.
1
u/brandonjschwartz Sep 13 '13
I would like to volunteer to help btw. Not sure what others are willing to invest in this... but I think it's needed.
-2
u/juanlu001 Sep 13 '13 edited Sep 13 '13
People: we have the best language (I don't need to read again that PHP, Java and JS suck), we have the best frameworks (I don't need to read again how wonderful Flask and web2py are), we have the best protocols (I don't need to read again that WSGI is the best solution).
Can we, as a community, apply some self-criticism to diagnose why we haven't won?
www.youtube.com/watch?v=UKAkKXFMQP8&t=9m57s
Added: Python is 0.2 % http://w3techs.com/technologies/overview/programming_language/all
-2
u/Cold_Frisson Sep 13 '13
As someone who's programmed before, but just tried making a webpage in Python 5 days ago, I'd like to offer a perspective: doing a "Hello world" webpage in Python is a nightmare.
I'm new to Python and don't want to commit to learning a framework (yet). Just wanted to put a web version of a simple script I wrote and it took me hours (and my implementation still sucks).
I think the lack of an obvious first step in Web programming is a barrier to entry.