psgibbs's comments

I don't get it, why are you afraid of scooping yourself?

In the same way that HN frowns upon stealth startups, shouldn't we frown upon 'stealth theories'? If your thoughts are novel and deep enough, revealing something about them will only increase interest in your future talks, since you are definitionally the foremost thinker in your unique worldview. If the idea fails scrutiny in some way, you should want to hear about it now so you can strengthen your position.

What's the downside, outside of using mystery to create artificial hype?

I'm not saying people aren't still choosing Backbone/variants today, just that 2 years ago, Angular was (1) not a nearly as viable an option and (2) not nearly as well known; so any time /company-size correlation will push the results in one direction.

edit: although interestingly, looking at the respective wikipedia entries, AngularJS has an initial release listed in 2009, Backbone.js is listed as October, 2010

I wouldn't draw a strong conclusion about 'larger' startups using Backbone instead of Angular based on this data.

There is probably some high correlation between a startup's size and age... Older startups are likely to be larger, and are likely to have started their stack using the popular framework of the time (Backbone). Newer startups will be smaller, and were founded at a time when new frameworks (e.g. Angular) are much more mature.

edit: grammar

If you don't have a specific reason not to, I'd highly recommend using the unstable branch today. I've had no problems with it since I switched several months ago, and any breaking changes have been pretty well documented in the release notes.

What this is missing is the amount of listeners each play counts for. On Pandora/Spotify/Youtube, a 'play' is typically one listener. For these, it's mainly worth noting that Spotify is about an order of magnitude more profitable per play ($1e-4 vs $1e-5).

Sirius is at ~$1/play, commercial radio is $0.07/play.

For Sirius XM, the breakeven number of listeners/play for the pricing structure to be comparable to Pandora is 70K. For Commercial Radio, the breakeven number of listeners/play is 5,000.

*edit: added the price/play numbers

Really, only in the sense that this source pushes out the aggregate supply curve, delaying the point in time when prices get higher.

Practically, once prices become 3x of current, that's what everyone will pay on average, it just means (in this thought experiment) that some miner sourcing from America is marginally profitable, while some miner from South America is very profitable.

I think typically people start them out in 'services.js' since effectively models in angular are constructors that are created, and then injected whenever you need a certain type (so you have a service that returns the constructor function).

A good example of this is how the tutorial treats the restful 'Phone' resource, creating a service that injects the resource where necessary. I've started calling them 'models' rather than 'services' internally as well, so it's interesting to me that others are too.

http://docs.angularjs.org/tutorial/step_11

I added 'evil' because particularly in this community, the connotation of 'hacker' is not necessarily negative. Many here esteem hackers as people who get things done by taking cleverly manipulating the system, or, alternatively, value results over process (I'd actually really appreciate a proper neutral definition of the term).

So all cops are 'agents of state violence'?

Just like all developers are 'evil hackers'.

If people realistically want the situation to get better, they need to embrace the 'good' police officers, rather than automatically ostracizing all police officers equally. Many still really do want to improve their communities.

I think there's a much simpler way to do fix it - force users to anonymously unendorse in such a way as to maintain a fixed ratio of endorsements to unendorsements. Don't show unendorsements or a negative endorsement level.

Suddenly incentives are much better aligned.

I totally get this sentiment for a lot of early project. My point is that at this point in the cycle, they know they have market support and are focusing on making a lot of people a great product, so the incremental sale doesn't necessarily change that dynamic.

I didn't realize there would be a price difference (as mentioned by Paul below), which changes the dynamics somewhat – product execution risk + getting it a few months early vs ~$50.

I honestly don't get the drive to reserve one of these early. The way I see it, you won't get it for a year and they're making 15K of these. What's the harm in waiting until they launch? Assuming it all works out, they'll have all the production lines tooled up and ready to go, so you can get one much faster a year from now (and with much better understanding of how they work in practice). If it doesn't work out, then what are you missing out on?

Result number 4 for me, after Armageddon Racing, Omega Drive, and Worms 2: Armageddon

I think this idea that every product Steve Jobs released was 100% quality is largely wrong – people just choose to only remember the hits. Apple has always released early - largely polished, but rough around the edges. Remember the early days of OSX? tons of loose ends. The first iPhone? definitely had stability issues, missing huge core features e.g. MMS. AppleTV? Ping? XCode 4?

Interesting observation, any data behind this to get the magnitude of the effect?

I'm surprised this is buried by people suggesting Rails or Postgres or what have you. SQLAlchemy as good a SQL ORM as there is, and it isn't married to a framework, or a SQL backend.

If you like Python and want to use a SQL backend, SQLAlchemy is a good place to start.