Skip to main content

Wine Released - after 15 years

Ted Roche noted over on Twitter that Wine has been released. Wine as in the open source implementation of the Windows API for X, OpenGL and Unix.

This is interesting more in passing for Fox developers as Wine was one of the tools that allowed FoxPro applications to run under Linux (among other environments). It also brought the entire FoxPro EULA (and likely any other MS product) to the raging issue stage (most MS Dev EULAs state that Apps can only be distributed on the Windows platform).

In my interview with Christof, he had noted that his Guineu project allowed FoxPro code to run on Linux environments thanks to the Mono project, which is a DotNet client for those environments.  Wine is something different although if you look through the app list, you may get a poor feel for it as it would appear that the only apps people really wanted to run on those environments were games (with the exception of PhotoShop CS2, all on the Platinum, Silver and Gold lists were games).

Wine

The developer world has certainly changed from when Wine was first conceived but congrats on hitting a 1.0 release. That does make me wonder - what version is gMail? It still says "Beta" to me but what is Beta anymore? (and on that note, take it away Rick!)

Comments

Ted Roche said…
Thanks for the linkage. Do recognize, though, that "Version 1.0" means something different in a product that has been freely available for over a decade. It's a statement of stability and a notation of very specific milestones, and not the meaning it has in many commercial circles of "these were all the features we could stuff in, and get past QA, before the shipping date." WINE is the development of an Win32API-compatible set of interfaces, a target that moved pretty regularly from Win95 through 98, ME, NT, 2000, XP and so forth. To achieve binary compatibility with that target is a pretty remarkable feat.

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…