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

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

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

I’m Supposed to Know

https://programmingzen.com/im-supposed-to-know/ Great post for developers who are struggling with unrealistic expectations of what they should know and what they shouldn't. Thirty-forty years ago, it was possible to know a lot about a certain environment - that environment was MS-DOS (for non Mac/UNIX systems). . There was pretty much only a handful of ways to get things going. Enter networking. That added a new wrinkle to how systems worked. Networks back then were finicky. One of my first jobs was working on a 3COM + LAN and it then migrated to LAN Manager. Enter Windows or the graphical user interface. The best depiction of the complexity Windows (OS/2, Windows NT, etc) introduced that I recall was by Charles Petzold (if memory serves) at a local user group meeting. He invited a bunch of people on the stage and then acted as the Windows "Colonel", a nice play on kernel. Each person had a role but to complete their job they always had to pass things back to h...