2,014 karma · joined July 31, 2008
Maybe its because I was trying to setup a deploy step after testing but it shouldn't have been that hard...
EDIT: That said I want to be convinced otherwise, or be pointed in the direction of a better way to do it. In the mean time I've been using heroku for one off apps and planning on moving to a vps. I would like a similar setup as heroku. Its hard to go back to manual pushes/pulls/restarts.
Obviously their will need to be a collision penalty but one would think this kind of behavior would be easy to do.
2. Good Question.
[1] http://peter.sh/2012/01/css-selector-profiler-source-mapping...
But I guess since I'm using a cookie-based sessions its less of an issue for state changes since the state stays mostly on the client.
Otherwise I've been very happy and content with my 100%[1] restful webservices.
[1] According to this article, the one it linked to, and a medium skimming of the original dissertation.
I know they aren't the only ones who do this but they are vocal about it, and when your living/working in enterprise land (MKE/Midwest) its good to remember it doesn't need to be this way.
I would find the results to be fine, and the interface to be good but the fact I had to wait slightly longer drove me absolutely up the wall.
Otherwise is 100% completely agree.
- We all met weekly for presentations, half the advisors knew what was going on the other half did not. Right before demo day the other half of the advisors were shocked that we had pivoted and planned on selling our OLD idea. Those same people then pitched our OLD idea to the few investors as a possible pivot, which was a huge WTF.
- They brought more politicians then investors to the demo day presentation.
- The investors they did bring focused on healthcare companies and companies further along(profitable, paying customers, large user bases etc)
- The entire operation was paid for by a single guy, who subsequently was the only investor in most of the companies in their "Accelerator" round.
- Most of the companies accepted had non-technical founders/co-founders. Most of the companies could not even launch a product, yet alone MPV, in 3 months because of this, and some had trouble launching a product after 1 year.
Overall we turned down money from their "Accelerator" which ended up being a great decision. If you are going to use an incubator make sure to heed the advice this article gives.
I do think the SOPA Drama was a bit delayed and overblown here on HN.
EDIT: grammar
Thanks for all the great work! I use and love BB, CS and _ everyday.
http://documentcloud.github.com/backbone/#Model-fetch
explains in a paragraph that it updates the object and fires a 'change' event. Right below in
http://documentcloud.github.com/backbone/#Model-save
the text explains how the backbone.sync handles the save function. What's sets me back is that the backbone.sync strings "change" and "update" are both quoted and highlighted just like an "event". It is not apparent from the method call if an event is ever fired. Upon careful inspection you notice it also calls set if the values are passed or values are returned differently. The set method triggers a change event.
Eventually these things become second nature and you just know them. The tricky part is finding a good place to start from. Maybe a list of good practices, maybe a good up to date tutorial showing a simple app that uses models, collections, views, routes, and a real backbone.sync.