I forgot to turn debug off. Yep. And i'm using sqlite3 to accept email addresses. Yep.
I can assure you the quality of the ACTUAL project is far better :-)
I have a working prototype and am working my ass off to get something scalable up and running asap. keep checking back for details!
Seriously though, best of luck, and godspeed.
I think what we're seeing here is an email/hype-grabbing attempt with an interesting vision, using the Heroku name for leverage.
Would like to see it materialise, but they really should have hardened something as simple as a signup form. I've emailed the admin telling him to lock it down.
I tried SQLite for a few things, and it has always come out a champ. I would not hesitate to use it for most of the semi-static websites I make (web apps would be pushing it), if I were sure it can handle more than one connection (I'm not, sadly).
I am very, very impressed by it. Seriously solid database.
Oh dear.
I hope that usability of djangy service will be better. Can't wait to try it :)
Btw, isn't Heroku itself planning anything for Django?
Has that ever been mentioned or rumored before? Is that even feasible given Heroku's technology stack?
The response was quite clear that they had no plans to enter the Django market.
The only thing really wrong with App Engine is the datastore:
- It's very different than anything you've come across before - The docs are not sufficient for it's complexity. You end up having to read lots of blogs and watch lots of videos to figure it out. - It is ridiculously difficult to learn (one of the hardest things I ever had to do) - Important parts of your stack won't work, like Admin - You can't just add the fields you like to an object. Instead you need to meticulously plan _how_ your data is going to be accessed. This is exactly the wrong thing for a startup, since you can't get up and running fast. - You can't iterate fast, because any schema change is very risky and very slow. - If you don't get everything exactly right, your app will be very slow. - There isn't much in the ecosystem.
By contrast, none of these are true for Heroku.
There are some things that are pretty good about App Engine:
- the tools are pretty good. Not as good as Heroku, but good. - the billing is spot on. They give you about $1 per day of free stuff, which can maintain a site with hundreds of thousands of users. And it's pretty cheap from there on. - They scale it automatically. On Heroku, it's really hard to tell how many "dynos" (whatever the hell that is) you need, except by trial and error. I would expect that nearly all Heroku apps are overprovisioned. App Engine just nails the scaling - it happens automatically, and you specify a maximum amount to pay per day, with lots of different dials to control it more precicely if you like.
I hope Djangy takes the best of both worlds.
Or maybe they'll enable more stacks? Pylons shouldn't be that hard to plug in once you have Django deployments working. And since they reached 1.0 lately...
If you guys can pull this off, I will be a very happy customer.
another, https://www.playapps.net/ for play apps., those written using the playframework.
I used Stax during beta, and it's nice, but it's no near the Heroku ease of use (puls it's little helper Nezumi http://nezumiapp.com/ when on the way). With very small restrictions, one can install anything on Stax, so it's very flexible, but just not that easy to use as Heroku'.
> another, https://www.playapps.net/ for play apps.
Unfortunately Play framework is not based on a servlet container (something that 99% of java webapps are using).
My number one goal is to provide a deployment environment with as few additional restrictions on the developer as possible.
(Disclaimer: same thing happened to my company when we pre-launched.)
