Re:Planet - Python realtime framework, the framework behind ...
by o1iver on Wednesday November 16, 2011 @08:47AM
(#3243071)
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.
Re:Planet - Python realtime framework, the framework behind ...
by hkarthik on Wednesday November 16, 2011 @01:02PM
(#3244218)
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."
Re:Planet - Python realtime framework, the framework behind ...
by kbutler on Wednesday November 16, 2011 @09:12AM
(#3243141)
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).
Re:Planet - Python realtime framework, the framework behind ...
by cgbystrom on Wednesday November 16, 2011 @09:35AM
(#3243219)
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.
Re:Planet - Python realtime framework, the framework behind ...
by o1iver on Wednesday November 16, 2011 @03:29PM
(#3244919)
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...
Re:Planet - Python realtime framework, the framework behind ...
by vetler on Wednesday November 16, 2011 @07:40AM
(#3242885)
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.
Re:Planet - Python realtime framework, the framework behind ...
by ozataman on Wednesday November 16, 2011 @10:52AM
(#3243546)
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.."
Re:Planet - Python realtime framework, the framework behind ...
by csears on Wednesday November 16, 2011 @12:32PM
(#3244055)
You totally missed the point.
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.
Re:Planet - Python realtime framework, the framework behind ...
by ozataman on Wednesday November 16, 2011 @12:37PM
(#3244088)
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.
Re:Planet - Python realtime framework, the framework behind ...
by smountcastle on Wednesday November 16, 2011 @11:01AM
(#3243598)
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.
Re:Planet - Python realtime framework, the framework behind ...
by sbarre on Wednesday November 16, 2011 @08:51AM
(#3243083)
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.
Re:Planet - Python realtime framework, the framework behind ...
by cgbystrom on Wednesday November 16, 2011 @07:53AM
(#3242923)
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)
Re:Planet - Python realtime framework, the framework behind ...
by LeafStorm on Wednesday November 16, 2011 @11:45AM
(#3243824)
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...)
Re:Planet - Python realtime framework, the framework behind ...
by viandante on Wednesday November 16, 2011 @07:25AM
(#3242853)
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?
Re:Planet - Python realtime framework, the framework behind ...
by candlll on Wednesday November 16, 2011 @07:30AM
(#3242862)
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
The third option is, just pay the team to finish up for you, which is what EA did, I guess.
- 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).
For Planet Framework customers, we offer "partner source". Meaning, that customers will get full access to source code and also submit their own patches.
https://github.com/esnme/ultrajson - Super-fast JSON serializer.
https://github.com/esnme/locust - Scalable load testing tool capable of simulating millions of users.
https://github.com/esnme/amysql - 100% async/event driven MySQL driver.
https://github.com/hjlarsson/gevent-memcache - memcached driver for gevent.
We've been building our own load testing tools on python, and it will be quite helpful to learn from the implementation of locust.
Yeah, that would work...
Like when AWS or GAE are down, and we sue and get our money back.
"...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.."
I couldn't continue after that.
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.
Do you expect them to explain all the concepts and underlying code in one video?
Also, the click+fix it thing actually showcases a very helpful IDE feature.
Check out any of the recent string of popular technologies and see how much effort people put into making smooth first impressions.
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.
(I'm one of the developers behind Planet Framework)
(He's the author/maintainer/we_need_a_new_word_for_this of jinja2, btw)
I don't know, am I missing something?
ref:http://www.planetframework.com/documentation/1.10/Licenses/
[1]: http://www.planetplanet.org/
I believe that would be a novel and very interesting use of Python, possibly even requiring a new interpreter...