dschwartz88

I can't wait until there are Sinatra and Rails equivalents for Swift (once they open source the Linux bindings later this year).

This isn't surprising news.

Isn't this one of Apple's main goals in their Activity app (w/ the Apple Watch)? To get around and move for a couple minutes each hour at least 12 times a day? Lots of other fitness bands have done this as well (Jawbone Up comes to mind).

This is an awful oversimplification, but in my experience, there are two different kinds of applications:

- User-centeric (think: an e-commerce site): your costs are going to grow somewhat linearly with your userbase/traffic. Do a load test to figure out how many concurrent users each dyno supports and then model your costs with that in mind.

- Data-centric (think: an analytics platform): your costs are to going to grow linearly with the amount of data points each customer is going to be using. Figure out how many data points a single worker dyno (running 24x7) can process and then model your costs with that in mind.

I realize that this took a huge amount of time, so asking for an open source version of this might be asking a bit much. But, I would absolutely be willing to pay for a SaaS product, or a licensing fee for the code. It's absolutely beautiful, and as someone who does this in a gross spreadsheet, moving to something like this would be unbelievable.

It's been proven these arbitrary restrictions don't actually enhance security. We need to see the TSA move to behavioral analysis for them to actually make a difference.

While I haven't personally used seed-fu, it seems to solve a different problem. There are two main problems we're trying to solve here:

- Having the seeds.rb file mirror the records you need from production. You wouldn't want to to register your User model, since you don't want all your production users. You would want to register a model like Product.

- Being able to easily migrate data on our production systems. Being able to easily migrate (and rollback if something goes wrong) is key to having predictable deploys (for us at least).

It's key to migrate seeds on a "clean" database. Any models you register will be exported from the database into the seeds file, so we usually rake db:reset before running rake seed:migrate on development systems. We actually built this gem almost a year into our current system, so our first bootstrap of this loaded all the records from our production database for the models we needed (products, shipping types, etc.), which gave us a clean seeds file to use on development and test systems.