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

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

Respect

Respect is something humans give to each other through personal connection. It’s the bond that forms when we recognize something—or someone—as significant, relatable, or worthy of care. This connection doesn’t have to be limited to people. There was an  article  recently that described the differing attitudes towards AI tools such as ChatGPT and Google Gemini (formerly Bard). Some people treat them like a standard search while others form a sort of personal relationship — being courteous, saying “please” and “thank you”. Occasionally, people share extra details unrelated to their question, like, ‘I’m going to a wedding. What flower goes well with a tuxedo?’ Does an AI “care” how you respond to it? Of course not — it reflects the patterns it’s trained on. Yet our interaction shapes how these tools evolve, and that influence is something we should take seriously. Most of us have all expressed frustration when an AI “hallucinates”. Real or not, the larger issue is that we have hi...

Friend vs Therapist vs LLM: Shades of Grey

The conversations with AI series brings up a single point and then compares it between different LLM engines. These types of conversations were one of the many contributing factors to my writing of " Towards Consciousness " that explores the benefits and issues of creating a conscious AI. In this scenario, I was interested in seeing how an LLM might differ from a friend or therapist on issues that may have nuanced responses or contexts. In doing so, I came up with an interesting discussion on shades of grey. My Premise: Is it a bit strange to be using an LLM as a sober second thought? Every time I walk down this path of “why use an LLM to do certain things”, I come back to the alternatives that people like to say. “Why not bring it up with a friend?” A friend typically has your back or will say whatever to support their own agenda. “A therapist?” That’s someone who is “trained” to be impartial. But a computer? A computer is impartial based on two logical outcomes. If you say ...