To all the people wondering: "why is this better than Flask" or "why should I pay XXXXX$ for something I can get for free". The huge difference is the fact that by purchasing this you have a right to ask for support and if it doesn't work out maybe even sue them. If you are running Battlelog XX thousand dollars is nothing. Imagine what it would cost them if Battlelog was down for a day. If they used Flask they may depend on Armin being available to fix a critical difficult bug. That is why these companies pay the big bucks: support and accountability.
Accountability eh? I'll remember this next time I'm using a paid web service, it goes down, and they put up a Status page saying "Don't worry folks, our lawyers are on it."
There seem to be two approaches when a problem occurs:
- Find someone to blame (sue them)
- Fix it (myself or pay someone to fix it)
I like to use tools that give me the second option (and planet probably does, but I disliked the "maybe even sue them" - better to have the freedom to fix than the freedom to sue).
Planet Framework is designed from the ground up to be real-time and scalable, but it also uses a lot of existing open-source projects.
For Planet Framework customers, we offer "partner source". Meaning, that customers will get full access to source code and also submit their own patches.
IANAL, but I would think that if downtime that is not covered by an SLA occurs (and you can prove monetary loss because of it) you should be able to sue. Maybe a lawyer can pitch in...
Not sure what to think about this. Seems very well documented and thought out, and the developer tools seem great. However, the price is very steep. It's a bit unusual to see Python frameworks with this kind of pricing. Perhaps I'm too used to open source, though.
This looks very interesting, though it definitely needs a free edition for developers to play around with. Perhaps limit the maximum number of concurrent clients or other artificial scaling limits. At €99/month there's no way I'd try this out even for 1 month; these prices are definitely targeted at the enterprise.
The video runs into an edge/problem case inside of the first 60 seconds, the solution to which is apparently something you have to memorize or get used to.
"...to add a component I do this... you see the error here saying that... to fix it, just click on this word and hit alt+enter.."
The video was showing how to use the IDE to add support for their DB migration tool to a specific model class. Initially, the class did not have the XML metadata required to track migrations so the IDE underlined the class name. This wasn't a edge/problem case, just the IDE being helpful.
What I was pointing out was bad defaults and a lack of polish. The very first introduction should not start with a warning or an error case. When I'm learning "yet another server technology and IDE", I don't expect to walk through a bunch of exceptions just to get started. It's a big turn-off.
Check out any of the recent string of popular technologies and see how much effort people put into making smooth first impressions.
I wonder if the timing of this release (and the relation to the Battlefield 3 web presence) is a poke at Activision's infrastructure/scaling problems of the Call of Duty Elite web platform?
The problem of large dynamic (to avoid "real-time") distributed web applications with big teams of developers that have to scale quickly sometimes during crunch or for emergency scaling post-launch, is not the easiest thing to solve so it's nice to see products aimed specifically at that space.
The reason behind "yet another template language" is that we compile down to both Python and JavaScript. Allowing us to render templates both on the server-side and client-side.
Sharing templates between these two gets very important when you develop real-time web sites.
(I'm one of the developers behind Planet Framework)
Ah. That makes sense. Both Jinja2 and Mako are very much tied to Python. (Though compiling a subset of Jinja2 AST's to JavaScript would be an interesting exercise...)
Ok, nice fancy IDE. I use vim, how is this different to me compared to flask/django? If it is repetition of code in the templates you want to avoid, what about noir+hiccup?
Someone has recently mentioned that this framework is soon going to be "released". Was it meant as in "free to use"? The pricing is quite steep, but otherwise it looks amazing.
[1] http://lucumr.pocoo.org/2011/11/15/modern-web-applications-a...
[2] http://news.ycombinator.com/item?id=3236820