sorted by: recent | see :
popular
Content Tagged with django + Google
New foundation for Django
opensource: del.icio.us tag/opensource
Development
Google
opensource
django
autopublishing
socialtracking
Google's Appengine - some initial thoughts
Google has just announced their alternative to Amazon’s s3 called ‘App Engine’.
I think that if this is successful it will provide a shift in some of the basic web development economics and practices, even more than Amazon’s s3 has.
why?
- Small hosting providers (ones that offer a shell account for $12/month) will be marginalized. why pay for something when you get it for free?
- M&A. It will create a 3rd platform to develop on. you currently have LAMP and Windows. The google app engine provides a 3rd. The major difference is you can’t buy it. If we acquire a company who runs on this platform we have 2 choices. continue paying google for the infrastructure, or redevelop it onto LAMP. of course this suits google as their integration costs are lessened. Google might provide a ‘open source’ version of their infrastructure.. but I doubt it.
- Language choice. currently it only runs one language, python. They say they might support others in the future, but if not there will be a lot of people learning python (to the detriment of PHP, perl, and ruby), as well as new tools and utilities written in it. It’s going to give python a huge boost in usage
- Database choice. Google’s App Engine will be using ‘bigtable’ which is not a RDBMS, and uses a hacked up version of SQL. This impacts companies like mysql. you don’t need to worry about replication here Krow ;-)
- Applications are integrated into Google’s authentication system by default. you don’t even have your own list of users.
As a python developer I love it. It even has django out of the box, but I would be a bit cautious to base my startup on a infrastructure which can only be provided by a single company.. when I get a invite I will be porting my applications over to it.. hopefully by then someone would have ported their blogging software to it so i won’t have to.
django-google
Updates from the Django Sprint
More than 200 people around the world devoted their time and brainpower to improving the Django Web framework this weekend, during a scheduled Django coding sprint. On Friday, September 14th, the first day of the sprint, some Django developers gathered at Google's offices in Chicago and Mountain View for the benefits of in-person communication, camaraderie and, yes, free food.
17 people showed up at Google Chicago, which was a sort of ground zero for the sprint, with the project's BDFLs Adrian Holovaty and Jacob Kaplan-Moss in attendance. Another 7 people participated from Google's Mountain View office, which was linked with Chicago via videoconference.
Python creator (and Google employee) Guido van Rossum even stopped by via videoconference to give a pep talk about Django version 1.0 and share some of his experience running a large open-source project.
The sprint was intensely productive, with more than 400 tickets closed in the Django issue-tracking system, 300 new patches/ticket attachments and more than 200 commits to the Django code base. All told, there were more than 2,440 changes, including wiki changes, ticket changes, patch uploads and code check-ins.
Overall, the consensus was: "We should do this more often!"
The Chicago sprinters, hard at work (photo by Jacob Kaplan-Moss)
Updates from the Django Sprint
More than 200 people around the world devoted their time and brainpower to improving the Django Web framework this weekend, during a scheduled Django coding sprint. On Friday, September 14th, the first day of the sprint, some Django developers gathered at Google's offices in Chicago and Mountain View for the benefits of in-person communication, camaraderie and, yes, free food.
17 people showed up at Google Chicago, which was a sort of ground zero for the sprint, with the project's BDFLs Adrian Holovaty and Jacob Kaplan-Moss in attendance. Another 7 people participated from Google's Mountain View office, which was linked with Chicago via videoconference.
Python creator (and Google employee) Guido van Rossum even stopped by via videoconference to give a pep talk about Django version 1.0 and share some of his experience running a large open-source project.
The sprint was intensely productive, with more than 400 tickets closed in the Django issue-tracking system, 300 new patches/ticket attachments and more than 200 commits to the Django code base. All told, there were more than 2,440 changes, including wiki changes, ticket changes, patch uploads and code check-ins.
Overall, the consensus was: "We should do this more often!"
The Chicago sprinters, hard at work (photo by Jacob Kaplan-Moss)
