31–38 of 38 posts
Earlier quoted context omitted.
JavaScript is also an impedance mismatch.
> JavaScript is also an impedance mismatch. Yet both Android and iOS allow embedding a Javascript engine in an native application with no effort whatsoever.
Earlier quoted context omitted.
> JavaScript is also an impedance mismatch. Yet both Android and iOS allow embedding a Javascript engine in an native application with no effort whatsoever.
I wouldn't call manually exporting Java methods to the WebWidget "no effort whatsover", plus the performance hit of doing cross-language, inter-process calls, in a dynamic language while the platform languages are static.
Well like it or not JS is first class on both platforms as they both have a JS engine at the developer's disposal, Kotlin or C# aren't.
Earlier quoted context omitted.
I wouldn't call manually exporting Java methods to the WebWidget "no effort whatsover", plus the performance hit of doing cross-language, inter-process calls, in a dynamic language while the platform languages are static.
> I wouldn't call manually exporting Java methods to the WebWidget "no effort whatsover", plus the performance hit of doing cross-language, inter-process calls, in a dynamic language while the platform languages are static. Well like it or not JS is first class on both platforms as they both have a JS engine at the developer's disposal, Kotlin or C# aren't.
If it was first class, there would be official Android APIs for JavaScript, debugging support on Android Studio, project templates on Android Studio.
Instead it is a web widget with its own little island of HTML 5/CSS 3, hardly first class.
The support is not much different than getting chromium and compiling it with the NDK.
The only mobile platforms where JavaScript is first class, alongside the other platform languages is on ChromeOS and UWP.
Earlier quoted context omitted.
> I wouldn't call manually exporting Java methods to the WebWidget "no effort whatsover", plus the performance hit of doing cross-language, inter-process calls, in a dynamic language while the platform languages are static. Well like it or not JS is first class on both platforms as they both have a JS engine at the developer's disposal, Kotlin or C# aren't.
I don't know about iOS, but on Android it surely isn't first class, the development experience is even worse than using the NDK. If it was first class, there would be official Android APIs for JavaScript, debugging support on Android Studio, project templates on Android Studio. Instead it is a web widget with its own little island of HTML 5/CSS 3, hardly first class. The support is not much different than getting chr…
Earlier quoted context omitted.
I don't know about iOS, but on Android it surely isn't first class, the development experience is even worse than using the NDK. If it was first class, there would be official Android APIs for JavaScript, debugging support on Android Studio, project templates on Android Studio. Instead it is a web widget with its own little island of HTML 5/CSS 3, hardly first class. The support is not much different than getting chr…
First class because there is no need to deploy your own JS engine on both these platforms, you can argue all you want, both have a webview/js engine API that are part of their respective SDK.
A language is first class when the complete SDK stack tooling has support for it.
IDE, debugger, docs, project templates, profiler, OS APIs.
Earlier quoted context omitted.
First class because there is no need to deploy your own JS engine on both these platforms, you can argue all you want, both have a webview/js engine API that are part of their respective SDK.
That is not what first class means. A language is first class when the complete SDK stack tooling has support for it. IDE, debugger, docs, project templates, profiler, OS APIs.
That's not what first class means to you. You can't just make up the definition you want just because it's convenient for your. First class means it runs on the platform without any form of external or third party runtime.
Earlier quoted context omitted.
That is not what first class means. A language is first class when the complete SDK stack tooling has support for it. IDE, debugger, docs, project templates, profiler, OS APIs.
> That is not what first class means. That's not what first class means to you. You can't just make up the definition you want just because it's convenient for your. First class means it runs on the platform without any form of external or third party runtime.
Hey, by your definition even web pages are first class on mobile devices, as they don't require any form of external or third party runtime, maybe we can even call them native apps!
If JavaScript doesn't require any form of external or third party runtime, then why does React Native bundle JavaScriptCore?!?
Seems like a gimmick to me. In a nutshell this has the same limitation has Xamarin. The Business Logic is shared , but the UI Logic and the Technical Logic aren't shared or not completely. The Xamarin community has been struggling with this issue for half a decade and they ended up re-writting their own rendering engine[0] (similar to Flutter) in C# on top of Xamarin to obtain truly MVVM Cross-Platform Framework. My…
Part of the issue when evaluating frameworks is expectations and not understand the plusses/minuses. If you are looking for a framework that will do 1 codebase for all logic and UI, without sacrificing any UX or capabilities, you'll probably be let down. Kotlin Multiplatform will be great for sharing logic and architecture. UI is somewhat of a different case. Why Xamarin wasn't great here is you need to do EVERYTHING in Xamarin, and write custom bridge code when not. It's an entirely different world, which bad IDE support for most of it's history. Jetbrains makes excellent tools, and if you understand that the UI will be "native", then there's a lot of efficiencies you can leverage here. If you get frustrated because you can't make one thing do all things, then yeah, it'll let you down.
Anyway, yeah, they're different.