Skip to main content

Wake up call to the Fox community.

Looks like the VFP community needs to give some Microsoft PMs a good shake or at least remind others that when speakers write an abstract, they are told to try and "spice it up" and thus say as many inflamatory things as possible. Sound familiar?

Not necessarily Milind, mind you - but when they give conference sessions that have blatant inaccuracies like this "VFP suffers shortcomings in the modern business environment in areas such as disconnected data, security, mobile devices, and more" - then someone should be doing better proof reading over at the MS Teched site.

1. Vista doesn't use DotNet - not as much as everyone was led to believe.

2. VFP (FoxPro) supports Vista - perhaps even moreso than Microsoft would want, if you look at the stuff that Craig et al are doing it.

3. DotNet STILL ISN'T the best solution for everything that developers need. Don't get me wrong - it does some really cool things - but the more MS keeps on pushing, the more push-back they will get.

4. VFP can do security, disconnected data and more. (I believe this article and this article talks about) Yes - it does require some work but no more work than trying to get people to call 5 lines of code instead of 1 to do the same thing.

No - Microsoft doesn't get the extra cash they would get if people were using SQL Server all the time - but hey, you'll get more cash than if you were pushing people to Ruby or another environment.

I know this is only one speaker's session but still, it's this kind of crap that hurts Microsoft's credibility, especially in the FoxPro community.

Where is the session on converting from VB 6 to Dot Net?
Oh I forgot - Remi Caron (the speaker in question) started in Fox but then moved to VB 6 only to jump over to DotNet.

Is there a session on strongly recommending VB 6 developers to move to DotNet because VB 6 is NOT a good platform? Somehow, I don't think so but if there is, please correct me.

At least the session does note that you can stay in VFP - but "...in Vista, .NET is a pragmatic necessity for VFP developers" - that's just not true. At least the Delphi session states it more obviously - "Staying with Win32 may be viable in the short term, but not the long term."

But hey , by that time, I'm sure we'll be up to DotNet 5.0 and a whole new RNWPF (Really New Windows Presentation Foundation). Fact is - most offices still run on machines that can fly by with Windows 98 and survive on Windows XP. I really don't see Vista being that huge an impact for at least another 2 years. And yes, there will be interoperability with DotNet and Visual FoxPro - like there is today. Scare mongering from former VB developers is just a way to try and attract people to their session.

Kevin Ragsdale : Microsoft Urges FoxPro, Delphi Developers to Move to .NET

Comments

Anonymous said…
Oddly enough, Remi's Software Developer Network website has a headline on the front page for a FoxPro Developer's Event, with YAG doing the keynote!

FoxPro Developer Event

Kevin

Popular posts from this blog

Well, that explains CodePlex...

In a move that will be sure to anger open source (or rather anti-paid software, anti-Microsoft open source)  zealots, Microsoft is planning to buy GitHub.

A year ago, I mused about why Microsoft would shut down CodePlex and how the world needs competing source code repositories to be strong. I'm not the only one per this Slashdot article :
"...people have warned about GitHub becoming as large as it did as problematic because it concentrates too much of the power to make or break the open source world in a single entity, moreso because there were valid questions about GitHubs financial viability...." - Jacques Mattheij

I will be interested in seeing this play out - whether developers jump ship or not. Have all the efforts Microsoft has made in pushing towards open source be seen as genuine or will all the zealots jump ship or maybe even attack?

Microsoft's comment about why they shut down CodePlex referred to how spammers were using CodePlex. Well, GitHub has its own …

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site:

http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html



What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older.

Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments.

But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward.

Attending Southwest Fox 2019 could change your life - Find out how

Southwest Fox is coming up in October and as I do every year, I spoke with the organizers Rick, Doug and Tamar on the FoxShow.

Deadlines for Southwest Fox:
Super-saver price (before July 1): $695
Early-bird price (before August 1): $770
Regular price (August 1 and later): $820
This year, I took a different approach with separate shows for each organizer but the main message is still the same : July 1st is their Go/No-Go date.

Conferences don't talk about this very often. I don't think developers really question if Apple will hold their WWDC in June or Microsoft will hold their Build conference - but that's because those conferences are vendor-led.

Southwest Fox is a community-driven conference - it's not driven by a company with an agenda. Listen to the interviews and you can hear how important each of the organizers feel the live connection between speakers and among attendees.