3 ms·
sure, you can compile an application, but if you want to target everyone, you have to do it on at least 3 architectures (linux, mac, windows) and as a user, i
by em-bee 7y ago
sure, you can compile an application, but if you want to target everyone, you have to do it on at least 3 architectures (linux, mac, windows)
and as a user, i am either lucky if my architecture is supported, or i am scrambling to find an alternative.
in my case i actually have all three. so when i see a new application i want to try, i check which one is best supported and then pick that.
several apps run only on windows. some on mac and windows, some others on mac and linux. occasionally there is a mac or linux only application. and once in a while an application binary is available on all three.
this is not even an issue of portability. even if the application is easily portable, i still depend on the developers choice of which OS they support. and i can't blame them. unless i am going to make money off the application i am not going to bother with supporting windows or macos. and most others will continue to ignore linux because the smaller market is still not always worth the effort.
with webassembly we finally get a unified binary architecture.
if an application run on webassembly, then the OS no longer matters. as someone that prefers to use linux. webassembly is like the holy grail. because if it manages to take hold, then hopefully the days of needing windows or a mac will be gone.
that's the point.
- ScottFree 7y ago> sure, you can compile an application, but if you want to target everyone, you have to do it on at least 3 architectures (linux, mac, windows) Is that really a big deal, though? From what I understand (and I could be wrong, so correct me if I am), most of the headaches involved in multi-platform development is the OS specific UI. Video games, for example, don't find porting to multiple architectures all that challenging because 1) they design for it and 2) they're not expected to adhere to OS UI guidelines.
- runevault 7y agoGames are also expected to be battery pigs, so doing 60+ FPS GPU rendering instead of however native UIs are rendered helps. Everyone certainly COULD just write their apps as 2d OpenGL but laptop battery life would suffer for it.
- billti 7y agoIt really depends on how complex your code is and what you're targeting. For example, the V8 JavaScript engine has a ton of ifdefs depending on OS (Windows, Mac, Linux, Fushia), bitness (32 or 64), chipset (ARM, ARM64, PPC, x64, etc.) and combinations thereof. For example, see some of the defines in https://github.com/v8/v8/blob/master/src/common/globals.h#L154 https://github.com/v8/v8/blob/master/src/common/globals.h#L1... and their uses throughout the codebase. EDIT: I forgot Android, and all the compiler specific flags. (https://github.com/v8/v8/blob/master/include/v8config.h https://github.com/v8/v8/blob/master/include/v8config.h is probably a better reference).
- em-bee 7y agoat this point it is mostly a problem of perception, and apparent complexity. portability is not the problem, but you still need to learn how to package for each different system, you have to maintain at least 3 sets of build-to-package instructions and understand each ecosystem. for example, i only develop on linux. yet, packaging for all linux distributions is still a hurdle. why can't i just compile and upload to my website? i have never packaged for windows or mac, and the thought having to learn those alone makes me turn away in disgust. i am probably wrong, and packaging for both is way easier than i think. but that's exactly the point of the problem being based on perception and apparent complexity. in order to package for all three systems, i need to first of all want to do that. and i find that i don't care enough to want it.
- tracker1 7y agoExactly this... I use all three as well, and tend to favor apps that run everywhere. Even if that means browser/electron apps. It's just less hassle for me. My single biggest issue is windows-isms for bash on windows. In the end, as long as it works, I'm very happy. Also, it doesn't preclude a given platform from AOT optimization/compile for WASM code to platform native code. I think getting common runtime interfaces is currently the paramount point... being able to use sqlite, and SDL/OpenGL adapters to canvas or webgl are also big. Not to mention audio, and various input devices (gamepads etc). There is a lot of existing code that could be readily ported/shimmed out if we can get some common interfaces working.