Selecting a platform to write for and worrying about how easy it will be to port to another platform is a sign of unintelligent design. It’s a sign you have no idea who your target market is. It’s a sign you, or your developers, have no grasp of reality when it comes to developing, shipping, and supporting a project.
You shouldn’t worry about portability, but that doesn’t mean you shouldn’t take it into consideration. You should worry about the core pieces of your project to ensure that they follow widely accepted industry standards. Those standards are there for a reason. Use them wherever possible.
Both Flash/Flex and WPF/e represent vendor lock-in. Tough. That’s the way the free market works. You are most definitely empowered to build your own toolkit, push it to the point where it has a huge developer-base, and user-base, and bring it up to the same level as Flash/Flex and/or WPF/e (or .Net 1.*, Java, etc.) Go ahead. You’ll probably get some help, but the vast majority of us will be picking a side and actually writing the coolest software applications ever possible.
Let Microsoft and Adobe duke things out, spend their enormous sums of money to build up their nuclear arsenals. Ajax-based toolkits have their hands in all of this too, but they’re playing with much lower yield weapons when compared to Microsoft and Adobe. In the end, we, developers and users alike, win.
Filed under: Coding