Skip to main content

In 21st century development, separate runtimes appear to be more popular than ever

Mike's post about the "Business Decision" to kill VFP reminded me I had this older post that was still stuck in drafts. As Mike says "Microsoft was hell bent against dynamic languages. But now? Microsoft is investing in creating versions of Python and Ruby for .NET and of course already has Jscript. If these dynamic languages can be developed for .NET, there's no reason VFP can't be ported to .NET."

I recall a time when the promoted disadvantage of FoxPro applications was that it required a separate runtime. "True applications don't need additional runtimes" was the mantra of many a developer, usually C at that time, but then when Visual Basic received native support as well, its developers joined that group (even though their support typically consisted of bundling the runtime directly with it).

Of course, it also made it easier to distribute VB applications when standard Office applications installed it by default as well. I even recall some discussion among FoxPro developers that all Microsoft had to do to make FoxPro applications more "acceptable" was to include the VFP runtime as a standard part of the OS.

No one makes those statements anymore. After all, Java requires a runtime (thankfully typically installed with your web browsers), DotNet requires a massive runtime (but since Vista, WinXP SP2 and Win2K3 all install it by default, no one notices) and now, Adobe's work with their platform independent Apollo will also require a runtime.

At least Adobe calls it a runtime - Java's Virtual Machine and DotNet's Framework all mask the fact that it's exactly what users have had to do with most applications for years. No one complains about this anymore.

But as FoxPro developers, we were often the ones who got crucified for having a separate runtime, until it become fashionable to do it.

Comments

Ted Roche said…
Yes, it's true. FoxPro was ahead of it's time in several directions. I've been doing a lot of research on ORMs lately (what a mangled field - everyone who's got a method on a object that reads data thinks they've got an ORM!) and the good ones look an awful lot like business objects from Codebook days, mixed with Andy Kramek's Data classes. And very little beats the 15-year-old architecture of Firefox! for reporting. What's old is new again, in some cases.

VM's are a little different, though. VFP's runtime allowed developers to poke through to the underlying operating system without restriction, and also could run into problems when multiple applications were running at the same time and sharing information, especially in DLL form. A VM ideally sandboxes the application from the underlying OS, abstracts what access there is for more uniform operation across heterogenous OSes, and isolates applications from each other.

But VFP was way ahead of its time.

Popular posts from this blog

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.

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 …

The World of Updates Today

I just received an update for Office 365. It certainly includes some cool features - including starting in one environment and picking it up in another environment. In recent years, I've certainly enjoined the use of Continuity on a Mac and in fact, I feel spoiled being able to start a message in one environment (even Google) and then finish it off on another.  This has become some pervasive when we were reviewing our most recent backlog at a client site, a similar feature was added to the current workload.

But with web applications, the trend is to reduce the amount of software on a client machine. I used to have automatic backup for all of my machines (thanks Carbonite!) but these days, many of my machines don't need anything beyond the core OS and some basic applications. Certainly that's the feeling with Chromebooks and even the lightweight aspect of many iOS apps. The functionality is mostly in the cloud.

When you upgrade your system, you expect it to a big update. So…