3 ms·
How would 2) be dealt with? Python is handicapped to a much more meaningful degree than current mobile options, e.g. while Kotlin isn't as fast as Swift (and Sw
by BigBathtubLobby 5y ago
How would 2) be dealt with? Python is handicapped to a much more meaningful degree than current mobile options, e.g. while Kotlin isn't as fast as Swift (and Swift's syntax is a strange PITA), Python is much slower than both, the only boon being the larger community surrounding it + legibility. OTOH, with the performance headroom on current devices, I suppose the performance loss matters less. Then again, Electron applications seem to inspire frustration across the spectrum with PC's and Macs.
As for 1): I agree.
As a tangentially-related rant, I do wish more resources were spent providing UI kits and easy integration of API's to third-party developers. IIRC Google still doesn't provide the same high-quality UI resources as Apple does, which is partially to blame for an app quality disparity moreso than disparate user bases.
- BiteCode_dev 5y agoPython the language != Python the runtime.
- VWWHFSfQ 5y agopractically it is
- nine_k 5y agoJython exists, and is in the same performance ballpark as CPython. Python does so much highly dynamic stuff that even writing a good JIT compiler for it is hard, OTOH these exist. On top of all, it has GIL. I suppose the plain bytecode interpreters are as fast as possible.