What is Xojo doing about Built App sizes ?
There is not legit reason for every single version of IDE to creep up App size of built applications. That is not what compilers do.
Why did the move to DesktopControls have to cost us nearly double Application sizes ?
(All tests bellow are simple hello world tests)
Some might ask if it matters. I would say it matters, its the first thing many look at, what does it produce, does it produce 70 mb Electron like app or good application.
For example then stand alone C# macOS application with no external dependencies is 7-8 mb, the move to Desktop Controls sadly put Xojo nearly double that.
48 mb for Console Linux Arm Application for example is not reasonable code app size no matter what framework you use.
I know its hard to unwind the problem with creeping application sizes, since the architecture of Xojo is not built well for real compiling and dead stripping. But Xojo could for example set them selfs goals like “If new IDE compiles bigger apps than previous ones then find something to optimize before releasing” which would be reasonable way to at least stop the everlasting size increase even if it does not unwind it.
16 posts - 8 participants