Skip to main content

David Stevenson's Talking Fox: Sedna and the Future of Visual FoxPro: Interview with Ken Levy and Alan Griver

David Stevenson has posted his entire interview with Ken and Yag on Sedna (no longer the tenth planet) and the future of Visual foxPro.

Great stuff David.

I find it interesting that Alan Griver is referring to the decision to support Vista with Sedna to be akin to shifting from DOS to Windows or from 16 to 32 bits.

I hope that is to do with the XAML support that Ken showed in his Channel 9 video.

My favorite part of the Interview:
"People always talk about programming languages being written in themselves. The .NET framework was written in C# and in VB. More and more parts of Visual Studio are now written in the managed (.NET) languages. It’s the same reason that anything that we add for ourselves benefits our customers. This means that if we add new extensibility capabilities in Sedna and we prove how much can be done – you know, if we can do half the things we defined in Sedna without touching the core product, you know what, Fox is a hell of a product."


David Stevenson's Talking Fox: Sedna and the Future of Visual FoxPro: Interview with Ken Levy and Alan Griver

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