3 ms·
> Yes, one's entitled to that opinion, but it's slightly misplaced sentiment. How do you figure? How long have you been using/developing with Google products?
by monkmartinez 8y ago
> Yes, one's entitled to that opinion, but it's slightly misplaced sentiment.
How do you figure? How long have you been using/developing with Google products?
Microsoft had the same reputation a few years ago. They learned the hard way what happens when you piss off developers. They are now making great strides to right those wrongs. What is Google doing to assuage those fears?
The way they have managed Android itself should give all mobile developers some consternation. It is an absolute mess with a ridiculous amount of cognitive overhead. Its a utility OS now and a really bad one at that.
My gut tells me that Android will be abandoned soon. Samsung could kill Android if it wanted to...
- nevi-me 8y agoGoogle Maps: 5 years Android: 3-4 years GCP: <2 years gRPC: 2 years (Kotlin, Python, Node, Rust, Scala) From this and your other reply, you seem to have been burnt by something in Android. The mobile market for which I develop products is made up of over 80% Android. Whether Sundar Pichai decides to kill Android tomorrow or now, I'm not going to let that get in the way of me making a living from a platform that currently exists with a significant market share re. my target market.
- pjmlp 8y agoAndroid APIs get partially rebooted at every Google IO, and the NDK is what it is, no need to add extra immature tooling into the mix, which isn't even officially endorsed by the Android team. In that regard one is safer (CV) using Qt or Xamarin, given JavaScript, C++, C# and F#.