As Pigeon support is experimental for Windows and doesn’t exist for Linux, you have to not only write your platform-specific code in a language you possibly don’t understand, but also your binding code. To implement native functionality, you have to use C++. On Windows and Linux, this is a completely different proposition. Kotlin and Swift will manage your memory for you, disposing of objects when they are no longer accessed, so it’s harder - though not impossible - to introduce memory leaks. In these cases, it’s not so hard to search StackOverflow for an implementation and try to guess your way through. That means that there’s a chance that some people writing Flutter apps will not have encountered a bona fide platform-specific language, like Kotlin or Swift. Drawbacks of working with platform-specific languagesįlutter, by its very nature, is a cross-platform language. It’s not an unmanageable amount of work, but it is still an amount of work. This can become a chore if you’re writing an app that targets a lot of platforms, especially if your app targets a platform where Pigeon support is experimental or nonexistent. And for Linux or the web, you’re back to writing your platform bindings by hand anyway. If you’re hoping to take your app to production, using an experimental generator doesn’t feel like a good idea. Pigeon support for Windows is experimental, and support for Linux doesn’t exist. However, desktop and web apps are another matter. This allows you to leverage the generated Pigeon code within your app. That’s not such a big deal for mobile apps, as you can call Java code from Kotlin and Objective-C code from Swift.
0 Comments
Leave a Reply. |