I'm currently trying to buy a pair of shoes on amazon, and many reviewers are calling out the fact that after giving the shoes a five star, they go to buy a second pair of the same shoe to find that it is completely different and of terribly quality.
I actually owe my programming career to MTM. When I was ~10-11 years old, I held many tournaments. At some point, my tournament grew to the point where I couldn't manage signups day of, and tried to make a website using frontpage + some form of extensions (angelfire? tripod?) to have early signups. I eventually learned javascript and a tiny bit of perl.
Looking back at that point in time, I did a horrible job of managing those tournaments (Sometimes my pre-teen responsibilities took priority and made me miss some tournaments. Oh and I seem to remember storing passwords in clear text). However I look at myself today and am extremely happy to be a successful developer, which may have never happened if it hadn't been for the MTM1/MTM2 games and websites, which I am certain I probably copied a ton of "codes" from back then.
You hit my opinion exactly. I love to hate/hate to love meteor because of how easy it is, but I just can't come up with an easy testing scheme outside of full out integration test, or making some separate modules that are injected. Thanks for the link.
If you are worried about cost, just run it on a subset of your servers. 10-20% of your servers should be enough to gather most information you need... unless you are using new relic as the only aggregator of server status/monitoring... and that should be heroku's job.
There are cases where startups, social impact organizations, or any fast moving team would pick rails for its fast movement, accessibility, and support, even if they thought that there were even more security issues than that have happened.
Yes. I have played with many js frameworks, including derby, meteor, tower, and several more while attempting to build my toy app http://retr.us . While it is built in meteor, I have concluded that I liked socketstream the best because of the level of control, especially on the server side. It also was the easiest to write unit tests for.