How Satya Nadella is taking on Apple and Amazon
afr.com
afr.com
Coding for UWP (aka WinRT) is a pleasure compared with the Android chaos, specially having a common OS OO ABI for multiple languages and tools that don't feel permanently in alpha stage, regardless of the amount of PhDs able to game the hiring process.
On the other hand VS runs properly on a HDD with 8GB.
As for Android, since you only installed Studio for the first time, let me explain it how it goes:
- Data binding introduced at Google IO 2015, still doesn't work in all use cases;
- The new layout constraints introduced for Android N, are still work in progress. In some cases blueprints and actual UI get out of sync, crash or don't expose certain attributes;
- Between the Camera and Camera2 API, I am not sure which one is worse;
- During two years anyone using the NDK was left unsupported, only after InteliJ announced CLion, did Google announced it would add its plugins to Studio. It took two more years to finally have some decent support for the NDK;
- Which since the move to Gradle had only the ndk-build documented, with some information scattered around how to use the new unstable Gradle plugin, followed by another plugin on the stable Android. But actually the way forward is to use cmake;
- There is hardly a Support Library release that doesn't have regressions;
- The Java fork, that is increasingly causing friction with Java libraries;
- The Jack compiler still doesn't support all of the Android own tooling;
- Fragments and activities, oh well....
- Gradle execution speed measured in minutes;
- The deprecated API between releases;
- Hardware accelerated 2D actually depends on how the APIs are used;
Stopping here even though I could easy add a few additional ones, but any Android developer can happily add some more bullet points here.
Then there is the mess of manufacturer bugs, but that isn't strictly google's fault.
I also have the latest Visual Studio Community Edition installed and it's "only" 1.25GB, but I don't have any extras installed, just the base plus some extensions.
>the problem is that the Android ecosystem is brutally fragmented.
Looks like Android now has company.
http://www.zdnet.com/article/ios-also-has-a-fragmentation-pr...
Android would be my preferred os, if it actually worked properly. Most lay people I know feel the same. A new Android device is a joy for the few months before it falls to pieces, then it's a necessary headache, much like windows was a decade ago.
If you dominate a market with a product no one loves, you better be a locked-in telecom. Otherwise, as Microsoft learned, your dominance may be surprisingly fragile.
Obviously, it wouldn't be an iPad Pro form factor, and Surface already runs Windows 10. But I'm sure you're following.
A Windows Phone with the ability to run ("native") Windows software would be an incredibly interesting play.
Asus ZenPhone houses an Intel Atom... Windows also has their little Linux thing... Android is Linux-based... Project Astoria was a thing...
This could be really fun to watch.
The duopoly is being abused. I am a iOS developer and I hate the 30% cut they take off my income. Their appstore algorithm favours established actors even when their product is far worse. I have seen apps that doesnt even boot on iOS9 ranking higher in the search results page than mine.
And lets not forget the Spotify vs Apple case.
The consumers need a third mobileOS to bring some competition. It is becoming stale with Apple and Android.
I think the big problem a new OS will have is compatibility with existing iOS/Android software stacks. You need to be able to run one or the other until you get market share for your own applications, because the majority of the populace wants their bread-and-butter Facebook, Snapchat, et al and these companies will not give your upstart OS any love until you have users.
I was a Palm Pre user from day 1. I loved everything about WebOS. I still do. I agree with your points completely.
The Pre was a fantastic device and did a lot of things right from a UX perspective, IMO. The hardware was terrible and there wasn't any mind paid toward securing anything really, but it was a breath of fresh air in the duopoly.
Intel killed its smartphone x86 chip project in April[0] so that's unlikely to happen anytime soon. There are reports of MS planning to attempt to do x86 emulation on ARM but that strikes me as a long shot. Getting good compatibility and decent performance would be challenging to say the least.
[0] http://www.anandtech.com/show/10288/intel-broxton-sofia-smar....
[1] http://arstechnica.com/information-technology/2016/11/x86-em...
Processor improvements are mostly going to efficiency rather than raw power these days, so time is on their side. Being able to carry your computer around and put it in a "desktop dock," or "laptop dock" would be amazing. It will make having separate phone apps and computer apps seem as kludgy as carrying an iPod, a computer and a flip phone was.
They're really close too. Shrink the surface a bit, make it cooler and put a cell radio on it. Boom!
And, if they ever get to the point of having something that is much better than what their partners have, I imagine there will be a lot better support for Linux on the market.
Regardless of what will happen with this Surface phone, at least from the consumer computer stores in some European countries, it is clear to me Windows 10 is the current winner for hybrid tablets and netbooks reborn, given that they replaced most of the Android ones that used to be on display.
Continuum, done right.
I'd call it a click-bait, YMMV.