26 ms·
You're right, we should all write software exclusively for Linux, and then only on RISC-V CPUs! :)
by Wowfunhappy 6y ago
You're right, we should all write software exclusively for Linux, and then only on RISC-V CPUs! :)
- acdha 6y agoA better way of looking at this is from the perspective of where they make money: targeting Windows makes sense because it's core to Microsoft's business, their reputation is heavily linked to it via all of those enterprise contracts, and their revenue scales directly with the number of people using Windows. In contrast, Flash was an Adobe acquisition which they never had a clear vision for and the model of selling tools but giving away the runtime for free meant that your app being popular didn't make more money for them. Anything security-exposed like this needs substantial amounts of ongoing maintenance funding but from Adobe's perspective that was mostly overhead or something Google would subsidize for them.
- RandomGuyDTB 6y agoThis but unironically. I can get C code from the 70s to compile in GCC but I can't get Windows programs released twenty or so years ago to run in Win10. Open software will always be easier to support and always be more stable than proprietary software, because one invites a free community of maintainers and the other one tells them that they aren't welcome. In the short-term, writing for proprietary systems is fine, but if you want your application to be use-able after you die you should probably open-source your stuff and make it compatible with free platforms.
- yjftsjthsd-h 6y agoI mean, you joke, but that would make you immune to this kind of problem.
- Wowfunhappy 6y agoRight, and that's why I phrased it as I did. I agree with the great grandparent, kind of—if you have the ability to use 100% open technologies, you absolutely should, and power to you! But at the same time, proprietary technologies rules much of our world, back then, now, and likely in the future.
- shadowgovt 6y agoThe difference between SWF and code written for RISC archtiectures is options. The "single-company-owned" part is what killed SWF. If there had been multiple SWF engines out there, to a common interpreter protocol, SWF content might have had a better chance of outliving the death of Adobe Flash.
- yjftsjthsd-h 6y agoThat's a fair point. I suppose it's not even guaranteed with FOSS, but open source makes it much easier to not have one company totally control the software/ecosystem, if nothing else because it keeps forking as an option.