Recognizing that it is not politically correct in these parts to pose this question, I sometimes wonder if the Samsung team (which seems like a highly-skilled, competent team) regrets building on Android...
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.
FTA:
This does not occur on stock Android from Google. This flaw only seems to be present on Samsung's version of Android. I have only tested it on a Galaxy Note II running 4.1.2 - I believe it should work on Samsung Galaxy SIII. It may work on other devices from Samsung.
"Recognizing that it is not politically correct in these parts to pose this question, I sometimes wonder if the Github team (which seems like a highly-skilled, competent team) regrets building on Rails." [1]
Samsung should stick to making hardware. Their software is either buggy or gimmicky.
http://iphone.appleinsider.com/articles/13/03/19/apple_relea...
"Apple has released the latest update for iOS, version 6.1.3, which fixes a bug that allowed for bypassing of the phone's lockscreen security feature"
"The update fixes an exploit activated by making and then immediately canceling an emergency call on a passcode-locked device. A malicious user with access to the device could use the exploit, plug the device into a computer via USB, and potentially access the data stored on the handset. "
I think it's funny.
Sarcasm maybe? In which case you don't deserve the downvotes [1] https://news.ycombinator.com/item?id=5404719
Samsung's development teams in virtually every industry is lackluster at best. Their phone and TV UIs are painful to look at, and built with features are often broken or incomplete. They are huge fans of animated loading screens, tacky lit logos, annoying systems sounds, and flashing lights. The fact that their flagship TV ships heavily touting voice commands which almost completely don't work, and visual gestures that absolutely don't work, is pathetic. The cherry on top is anyone trying them, looks like complete tool.
Their screens are industry leading, and their phone hardware are also pretty amazing. I would say the problem is the Samsung dev team, and is not Android.