Skip to main content

Visual FoxPro, SQL, Linux and Windows - What the first LinuxOnly store reminds me of...

(ok - so I couldn't get a good title for this post)

Interesting article from Linspire about Linux trying to break into the big-box chain support for Microsoft and Windows.

It sounded really good until you see the picture of the place. I'm sure it's a nice place but it would have been better to get a bit nicer picture. I was expecting to see the comparison between a Microsoft aisle and a Linux aisle. Anyways...

The store is here: Sub300 and I'm sure it will do very well.

I also read an interesting post in the Wiki about comparing Visual FoxPro and the other MS databases. Of course, Microsoft doesn't make money on Visual FoxPro applications like it does on SQL Server (that's what happens with a royalty free runtime) but I draw the comparison (and it's a very big stretch of a comparison) to Linux/Windows and their costs. The Visual FoxPro community has always been extremely vocal (so much to the point that it's great to see that members of that community doing well in the other MS areas (kudos Yag and Ken) and inspiring that type of community spirit. The entire blog community is also huge and growing. I'm not being all "touchy feely" about the community idea - but rather that it's GREAT to see positive enthusiasm in both camps.

And so what I see in Windows and Linux are two different communities, and the louder and more complimentary group to date are certainly the Linux people (I won't even begin to talk about the Apple community which has always been more vocal and greater than both). People like Scoble and others are certainly trying to change that at Microsoft - ensuring that people see Microsoft not just as the big target, but as people who are genuinely excited about their technology.

Enough of nay-sayers, put the products out there and let the best win.

Linspire.com - Michael's Minutes

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