Yep, just the main national tracking polls. We email every one out so at the state level it might get overwhelming. And we can't really put too much into a filtering setup since it's a product that'll autodeadpool in 2 weeks :)
Developer here. I helped build this site after noticing I was checking presidential polls like 12 times a day and really wanted a quick disposable tool for the next 2 weeks to get them as soon as they are released.
On Nov 6th, we'll shut the site down and permanently delete the entire list.
Luckily great tools have been built for this. We use Opscode Chef and it's life changing. After an admittedly painful learning hump, we're able to completely power our sysadmin via code.
DeployButton is just the trigger button, not the missile :)
Hey guys, thanks for the feedback. As you may already know, this was built for the 48hour Rails Rumble hackathon. So it will definitely have quirks and there's a ton of stuff we had to cut (like collab git access instead of full oauth which i believe would have solved most security concerns).
Dropbox let us set things up nicely, where we opt for only a single folder (Apps/DeployButton) and we can only see stuff you place directly inside.
The main appeal of DeployButton for me was to have a service I could easily connect to Campfire/Hipchat to script out deployments from there. It's not that deploying is "hard", it's that it's tedious and I believe should always done as a collaborative experience instead of solo.
More feedback greatly appreciated. Site and workers are already overloaded (we didnt anticipate an HN post). So apologies in advance.
Awesome writeup! Rails asset management can get pretty complex for newbies, but with a few good strategies like described in the article, it can be tamed and managed without too much trouble.
Completely agree, it should be emphasized that nReduce isn't trying to compete with existing accelerators. I think it's actually a great first step for companies to get to the point where they can join one (since the good ones tend to require serious traction just to get in).
Personally the best thing our team got out of being an nReduce participant is the weekly checkins. Having 12 video checkins that document our progress has been really useful for showing investors the amount of progress our team can make week by week. We intend to continue this habit throughout the life of the company.
Actually, App.net is quite useful already with it's 17k users (as was twitter when it had that many people).
It doesn't have to compete with Twitter, just provide a growing self sustaining user base of paying customers. Seems like an ok business strategy to me.
I would pay (prepay) for this. OmniGraffle has been painfully slow to improve, and just doesn't seem to cater to web or app ui design. Unfortunately it's the best thing out there so far. Need something better.
Build this as a native app and charge $monthly. That way people can get started with it for cheap and if you keep making a good product, they'll keep paying you for it.
I really feel like the 1 time app charge model is severely broken for consumers. Omnigraffle gets my $200 bucks and all of a sudden there's nothing I can do to influence them anymore as a customer. The product stays pretty much the same for 4 years, as they move on to find the next pot of gold app to build.
Sorry, I just meant compared to Rails in terms of impact. Ember is nothing like Rails architecturally. There's a good comparison here: http://emberjs.com/guides/ember_mvc/
So yeah. Ember's problem is convincing people there's a problem (hint: there definitely is).
Perfect article and explanation. After having bought into Ember a couple months ago and using it heavily, it's been really hard to express to others why it feels so revolutionary.
Ember really changes JS development in ways that the other frameworks don't even attempt. And in a way this hurts it in the perception of developers, since it more often than not is just tagged as "too complicated" or "too much to learn".
The more great articles like this, and I think there'll be a solid chance Ember catches on in a big way the same way Rails did. With 1.0rc, the tech seems to be solid enough now and it just needs a push on the other stuff (education, marketing, etc). And most importantly: some more successful Ember apps out in the wild (I'm working on that one).
Another simple idea (that you've no doubt thought of): using Twitter (or App.net) authentication. That way people are a bit less anonymous and more accountable. I can imagine people would hate this, but they might be the same people who are the haters to begin with.
I don't think this phenomenon is just on Hacker News. I believe the recent negativity shift is an actual change in the startup community's perceptions of the world.
When things are "hot" in our industry, and seemingly trivial companies are exiting for billions, the people who are still struggling start to develop a somewhat bad attitude. I see it all the time particularly from people who are working on "serious stuff" and then lash out when they see Instagram's success (which they've been saying for years: "sure, but what's their revenue model??").
I don't condone it and honestly think it's genuinely strange. Now is as amazing a time as any to be founding a startup. Success of others (no matter how trivial) only makes things better.
To clarify, I'm not affiliated with App.net in any way (aside from being a backer). Just an idea I had that I thought would be cool, and make App.net really useful to me as a user and developer.