To be clear: yes, this is a bit of flamebait and a rephrasing of https://news.ycombinator.com/item?id=5404719 https://news.ycombinator.com/item?id=5404719 . Th

To be clear: yes, this is a bit of flamebait and a rephrasing of https://news.ycombinator.com/item?id=5404719 https://news.ycombinator.com/item?id=5404719 . The thing that rubbed me the wrong way was that we see far too many comments that follow a pretty obvious scheme: * Criticizing the viability of whole platforms based on generalizing details without good discussions of the whole thing. * Application bugs are often blamed to a general unfitness of underlying frameworks. * Tricky interactions of Framework bugs with Applications even more so. And, even worse: * Based on the "flavor of the week". Or: we're all victims of our own perception and we are not willing to recognize it. For example, No one here really knows why this bug specific happened - it could be that Samsung triggered an Android bug, or they just flat out built something wrong. Its a detail that - by itself - holds absolutely zero information about the Galaxy S line, Android or Samsung. I believe that both Rails and Android (and almost any other platform) have systematic problems, but rarely anyone ever discusses them, because its far to hard to find people that actually do have enough knowledge and are willing to dig into multiple implementations of the same. Rails is in a pretty obvious phase of downwriting by a lot of people, Android is very well liked by many. For the record, I am not very attached to both, I maintain a different Ruby web framework and I cannot really get pumped up about mobile stuff.