Re:The Huawei Disaster Reveals Google’s Iron Grip on Android
by pizza on Friday May 24, 2019 @03:39AM
(#19999321)
Makes me think whoever comes up with a mainstreamed way to do cross-platform mobile apps in Python will easily capture a large share of recent college grads, too, then.
Re:The Huawei Disaster Reveals Google’s Iron Grip on Android
by oblio on Friday May 24, 2019 @04:14AM
(#19999513)
> cross-platform mobile apps
Against platforms actively fighting you? Good luck with that!
Re:The Huawei Disaster Reveals Google’s Iron Grip on Android
by Iolaum on Friday May 24, 2019 @03:59AM
(#19999424)
There is the beeware project trying to do just that. I don't think it has enough people contributing to get there at a reasonable pace though.
Re:The Huawei Disaster Reveals Google’s Iron Grip on Android
by tokai on Friday May 24, 2019 @04:38AM
(#19999636)
Kivy already does that?
Re:The Huawei Disaster Reveals Google’s Iron Grip on Android
by dvhh on Friday May 24, 2019 @03:58AM
(#19999423)
What about webasm ?
Re:The Huawei Disaster Reveals Google’s Iron Grip on Android
by pvinis on Friday May 24, 2019 @01:19PM
(#20003538)
Ah that's easy. Just get python to js with wasm, then use react native.
That would be interesting to see!
Re:The Huawei Disaster Reveals Google’s Iron Grip on Android
by pjmlp on Friday May 24, 2019 @12:56PM
(#20003380)
Symbian supported Python actually.
Re:The Huawei Disaster Reveals Google’s Iron Grip on Android
by DeonPenny on Friday May 24, 2019 @04:24AM
(#19999558)
The did and called it kotlin. Those people were Google and Jetbrain.
Re:The Huawei Disaster Reveals Google’s Iron Grip on Android
by RhodesianHunter on Friday May 24, 2019 @05:58AM
(#19999995)
Except Kotlin isn't Python, it's Java with modern syntax and coroutines.
Re:The Huawei Disaster Reveals Google’s Iron Grip on Android
by sametmax on Friday May 24, 2019 @03:46AM
(#19999353)
Jolla did and failed.
Re:The Huawei Disaster Reveals Google’s Iron Grip on Android
by baybal2 on Friday May 24, 2019 @03:54AM
(#19999402)
Well, Jolla was a meme company. The best shot a normal Linux had on mobile was during N9 era, and late Meegos.
After that things went sour:
- GTK+/glib dev community began to wither simply because of older members retiring, and no new blood
- DRM flamewar with record labels
- Android diverted a great amount of community resources
- Monopolisation of smartphone SoC market.
- Elop...
Re:The Huawei Disaster Reveals Google’s Iron Grip on Android
by abdulmuhaimin on Friday May 24, 2019 @08:11AM
(#20000655)
RIP the late Meego OS. Im still salty with how Nokia murder it. Its like a healthy beautiful baby just born and then the parent buried it alive to focus on their terminally ill older brother.
However, the parents cant handle the debt and commit suicide, entrusting older brother to his rich uncle. Sure enough, the older bro didnt live long either. After a long coma, the plug was pulled on the older brother's life. Even his rich uncle cant save him.
What a waste of resource
Re:The Huawei Disaster Reveals Google’s Iron Grip on Android
by ahartmetz on Friday May 24, 2019 @06:16AM
(#20000059)
Not Elop really. The Nokia board had already decided to sell to MSFT and brought in Elop to do it. If the N9 hadn't been delayed by years, things could have gone very differently. In retrospect, the biggest surprise was that the years delayed N9 actually turned out to be very good. Extremely delayed products are more often bad than good when they are finally released.
Google's biggest trick was developers. They leveraged the decaying state of Java, and it being the default CS language in a lot of places. They simple showed a more attractive opportunity to tenths of thousands of Java devs stuck in ungainful employment in "enterprise software" sector.
Nobody else in the world managed to get so much of developer mindshare overnight ever.
Developers, developers, developers, developers... Balmer got the idea, but did not know how to get it.
Jobs realised it too late, and spent too much effort toying with Internet only apps in time when most of USA was on class 2 GPRS.
Andy Rubin, well I'd say, got the right solution almost by accident, and only realised its value later in Android's life.