Skip to main content

Microsoft goes cross-platform with .Net - why not FoxPro?

Since Microsoft is going cross-platform with Silverlight and DotNet, it seems that instead of only encouraging Microsoft to reconsider VFP development, some energy might be better spent encouraging them to open up the VFP Eula to allow running on other platforms (such as done via the WINE project).



Some reasons to consider this:



1. It would not require Microsoft to deploy additional development resources into FoxPro - instead, it would require some legal resources to make a fairer licensing agreement.



2. Developers who have been looking for ways of deploying their local data applications on Linux have had to ignore the Microsoft name. If VFP applications were able to run on Linux, it could offer more credence to other Microsoft's initiatives on those platforms.



3. You can do it already - save for the EULA. Whil Hentzen has shown this years ago. At that time, Microsoft then re-did their EULA preventing you from running VFP apps on anything other than a Windows desktop. But if Microsoft wants to go to great lengths in showing how "open" they are to other platforms, what better way than to free-up the current licenses that prevent this openness from showing forth.



Note: the issue in the EULA is under Distribution Restrictions which says "you may not....



distribute any distributable code that runs on any platform other than the Windows platform"



(as noted here)



I know there are many reasons why Microsoft will not do this - BUT, I bring it up simply as an alternative to attempting to persuade Microsoft to re-develop FoxPro - to allow a rich development tool be available everywhere it can be. Just a thought.



Microsoft Silverlight: Light Up the Web



Powered by ScribeFire.

Comments

Popular posts from this blog

Merry Christmas

Whether you celebrate now, have already celebrated your past holiday, are planning to, or not, I hope you find yourself surrounded by family and those you love during this holiday season and are able to remember fondly those who are not with you. We often find ourselves buried in work, or too distracted by other problems, to share and remember a few moments with those closest to us. So many of us are separated by huge distances, we often find it easier to focus on those who are out of arm's reach yet so easy to connect with online, instead of those who are right beside us. So do yourself a favour, put down the keyboard (stylus, mouse, etc) and spend that time. I know I will. Merry Christmas. Powered by ScribeFire .

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...

From Writing to AI: the pattern repeats itself

When I was ten years old, my dad bought a computer and, thanks to an advertising supplement in a Superman comic I read, it was a TRS-80. A month later, he dragged the entire family (my mom and brother were not the most enthusiastic) to a class at Radio Shack teaching how to use microcomputers. At the time, I understood why my mom wasn’t that excited: the computer was yet another gadget in the house. But today I find it fascinating. My mother went to Vassar in the 50s. She learned how to type — not a common skill at the time — but it opened doors. Her ability to communicate effectively led her to a career in adult education and later communications work with the CBC (Canadian Broadcasting Corporation). This isn’t a nostalgia post. Today, the ability to use artificial intelligence, be it through Copilot or simply writing the right prompt, is becoming a critical skill. But is it really that novel? In the 1500s and 1600s, the printing press gradually made reading accessible beyond cler...