Skip to main content

Python: Google App Engine

I just found out about Google App Engine. Does anyone else feel as overwhelmed as I do? This changes everything for us Python Web guys.


Ian Bicking said…

This could make Python the next PHP. (And maybe in the bad ways too ;)

Open source web applications could, like, really work. Normal people could install a web application like they install normal applications.
Anonymous said…
I don't see what's overwhelming. They've put out Yet Another web system with some odd constraints. Unless you want to use another database over the web, your app will be locked into a proprietary database system that you can't run (or even test with) anywhere else.

For GAE to change the game, I would think they'd have to make it a lot easier for people to create web apps (not "here's some of django and some other CGI you can use").

GQL is especially weird, since it's a limited SQL-ish thing that no one else supports or necessarily will support. I'm a fan of the new SPARQL language for querying RDF, partly because SPARQL is the kind of standard system that google *could* map to their database. RDF predicates (aka google datastore 'keys' aka SQL 'columns') are more precise than any of the other systems, so it's never lossy to adapt an existing DB system to RDF.

Doesn't facebook have an FBQL that's also an arbitrarily reduced version of SQL? Maybe it's not for the same purpose at all, but just the presence of these things is training everyone to accept a new, proprietary query language for every system we deal with :(
jjinux said…
Drew, very, very well put.
Noah Gift said…
I do think it is a big deal. Having Google throw it's massive infrastructure and support around creating Python web applications is going to change everything...IMHO.
Anonymous said…
Have to agree. Google don't do things by half. I just hope the Emacs lads integrate it properly :-;

Popular posts from this blog

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p