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

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

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...