I'm curious to hear how well Platform Uno works in practice with real world projects. The demos are quite impressive.
I always thought that UWP was a much nicer platform to develop for than Android. It's a shame that Microsoft's mismanagement pretty much killed Windows Mobile as a viable platform.
dev here - this app is based on mono-wasm, which uses the very young support for AOT compilation from .NET IL to WebAssembly. There are limitations in WebAssembly (namely the lack of support for exceptions) that force the mono codegen to add a lot of weight to respect the .NET semantics. The rest is what it is because mono-wasm still is in the "make it work" phase.
23s, especially if it is the second run where the wasm is cached, to start the application is very high though. It should be below 4s (which is still high) on a desktop class machine. Was that on an Android phone by any chance ?
11 comments
[ 4.3 ms ] story [ 22.0 ms ] threadI'm curious to hear how well Platform Uno works in practice with real world projects. The demos are quite impressive.
I always thought that UWP was a much nicer platform to develop for than Android. It's a shame that Microsoft's mismanagement pretty much killed Windows Mobile as a viable platform.
- 84 HTTP requests
- 10.2 MB transferred
- 51.9 MB in decompressed assets
- 23.44 seconds to start the application.
For a calculator, these are pretty extreme numbers.
23s, especially if it is the second run where the wasm is cached, to start the application is very high though. It should be below 4s (which is still high) on a desktop class machine. Was that on an Android phone by any chance ?