Wine 1.7.12 Released
winehq.org
winehq.org
Over the years I've encountered a lot of skepticism about Wine, with some people even wondering if we'd be better off without it existing. I've never been convinced.
I hear an incredible number of stories about people who wanted to use Ubuntu, but couldn't because of one Windows app. Increasingly, I hear the inverse -- people who are happily using Ubuntu now because Wine works well enough.
Data is hard to come by, but my best estimates put Wine's install base at something on the order of 10-25% of Ubuntu users. That means millions of users of my packages. Most are running games. Some use it for some sort of critical business function like a legacy app.
I've contracted with a good number of companies who use Wine for critical business purposes. Wine is quickly becoming the porting tool of choice for making Mac and Linux versions of Windows software -- often times the game will work without modification, and when it doesn't these days it is dramatically cheaper to improve Wine than to rewrite applications.
I do understand some of the skepticism though. A single bug can render an application completely unusable, so from a user's perspective it's very hard to tell whether Wine is 99% done or 5% done. But in the future, you won't even know you're using Wine -- it'll silently be powering your steam games.
Thank you. I can play skyrim on my linux machine, now. :)
Many thanks! +40 or so machines run LTSpice (and other apps) via WINE in my lab. A good portion of my students install and run Linux on their personal computers, then using WINE for Windows application support.
Without your packaging efforts, I wouldn't be able to use Linux as my primary desktop at work.
I've been a fan on Wine since I tried it, but I think this article on OS/2 from Arstechnica argues very well, on a historical basis, for why Wine unfortunately won't be helping getting people to use Linux on a large scale.
http://arstechnica.com/business/2013/11/half-an-operating-sy...
"OS/2 ran Windows apps really well out of the box, so they could just write a Windows app and both platforms would be able to run that app. On the other hand, writing a native OS/2 application was a lot of work for Windows developers."
"The second lesson of OS/2—to not be too compatible out of the box with rival operating systems—is a lesson that today’s phone and tablet makers should take seriously. Blackberry once touted that you could easily run Android apps on its BB10 operating system, but that ended up not helping the company at all. Alternative phone operating system vendors should think very carefully before building in Android app compatibility, lest they suffer the same fate as OS/2."
Linux is free. OS/2 was strictly more expensive than Windows, and required you to buy a copy of Windows to run the Windows apps.
Like it or not, Linux was effectively second to the party. We faced a chicken and egg problem, and had no first-mover advantage. We simply weren't strong enough to cajole users into defaulting with us because we could hold all their favorite apps hostage if they didn't. We had no apps, legacy or otherwise.
We tried to get people to want to migrate badly enough by excelling in other areas (like being free). But our biggest problem was that they couldn't come even when they wanted to: 80% never heard of us, 80% of those left had hardware issues, 80% of those who remained had an application with no native equivalent. 20% of 20% of 20% is 0.8%, which incidentally is the exact market share we had.
But we're solving those issues now. People are becoming more aware of the viability of the platform. Distributions with commercial backing and their hardware partners have been solving the hardware issues. But there's still that application barrier for migration. Wine is a huge part of the solution to that.
There were lots of DOS apps. A few windows apps. And no OS/2 apps.
Windows always had compatibility AND reasonable system demands. On a windows 3.0 supporting machine you could not run OS/2. On a windows 3.1 machine you could -badly- run OS/2, but not OS/2 2.0. And on a windows 95 supporting machine you could maybe run OS/2 2.1.
OS/2 is an example of why design by committee loses out to a technical person really controlling the development of an application. OS/2's code, I'm betting, is far more flexible than the windows code, and has support for all sorts of weird features that no-one but academics care about, and massively increase demands on hardware. They also constantly require rewrites to actually make use of these features.
OS/2's failure had nothing to do with application support. If anything that was one of OS/2's redeeming features.
I like to think that the first thing you should do to make something succeed is to make it possible for said thing to succeed. OS/2 did not make it possible for itself to succeed, because nobody could run it. Somebody should have stopped the software architects and forced them to change until that happened. Nobody did.
The academic community was really proud. They even pushed it into the huge IT environments, like banks. No-one ran OS/2 for fun, because that was a $5k proposition. Running a windows 95 was a $500 proposition, that also got you access to duke nukem 3d and loads of other games.
Both ran well enough to run wordperfect on a 286 with 1 meg of ram. OS/2 wouldn't even boot under 4 megabytes of ram, or with a 286 processor.
So yes, vastly more expensive hardware requirements is certainly a valid criticism. In 1992 nobody had 386 machines. Some even say IBM purposefully designed it like that, to sell more machines. But if they did indeed intend that, why not release the OS for free ?
In 1992? I think this was after for example the infamous AMD 386DX-40 was released. Granted there probably still were a lot of 286s out there back then of course, which is one of the reasons why I never suggested abandoning DOS/Win3.x immediately. Of course, as mentioned before this would cause some pain for application developers, but this would last only a few years, and even PX00307 mentioned "Porthole" (aka WLO).
By 1992, 386 machines were common, and new machines for serious work were generally 486s.
Seems like Wine will actually be even more relevant if increasing Steambox support allows more people to ditch windows (I still have a windows gaming only box).
Thoughts on integration? Wine can run steam but I wonder how far this could be taken in having a clean dual installation of native and wine based.
One solution is to just port all the old apps with Wine wrappers so that Windows steam isn't needed. Another solution is to just have both steams open together (Valve has promised multiple simultaneous login support in the near future, as it's a requirement of home streaming).
Another option would be to have full-on support for detecting Wine within Linux steam and offering to run your windows games using community-derived Wine settings (akin to playonlinux or winetricks). That would be kind of radical, but I don't think they'd be gutsy enough to go that route.
Yet another option would be to simply endorse porting with Wine and tell developers how easy it is and how much money they could make by porting the back catalog. Last time I asked Valve didn't want to endorse a particular porting technology, but perhaps they'd change their minds if one was good enough and it meant developers would be more willing to port games with it.
I wish wine could do a bit on the visual integration side - enabling themes makes it quite slow, maybe you could have a word with Mr Shuttleworth and get him to bundle and ubuntu wine theme, and fund the last bit of work to get themes rendering quickly.
Do you mean it'll be powering Windows-native Steam games, or that Wine is somehow related to the Linux version of Steam?
I was pretty surprised to see a familiar-looking wine style layout there.
I didn't really look into it, so I don't know what the exact situation is, but looks like the future might have already happened in that case.
Cider sucks, though.
Codeweavers has already moved into the porting space using their expertise around free Wine, and perhaps not surprisingly Transgaming has begun to pivot into completely different areas.
But I'd really like to know whether people are actually effectively using things like Office with Wine or whether there's some Door Number Three that I'm just not seeing.
It's a music production studio, and one of the features that it offers is to use a VST instrument. A VST instrument is a .dll file which provides a virtual instrument for the user to use in their music project. So here we have this native linux app but it is able to take advantage of .dll plugins using wine.
http://bugs.winehq.org/show_bug.cgi?id=35508
Qt file picker, I think. (The sidebar stuff doesn't work either, I suspect for the same reason.) All the code is open source, just needs someone looking at what's happening.
I tried building it with VST support once, not exactly seamless - not sure I ever got it to work.
The effort isn't complete (they didn't re-implement all the corners), but it works well enough.
It suffers from some graphic bugs (mostly in the properties dialog, for objects in PowerPoint for example; usually you can fix it by reloading the dialog), also, TrueType doesn't look perfect. I can't remember having it crash heavily.
I needed MS Office because while Open/LibreOffice is good enough for most things, and is actually more than sufficient if you write your materials from beginning to end in them and never export to proprietary formats (i.e., always keep saving in ODF), the compatibility layer with MS Office is not perfect and is not sufficient for more advanced things (such as the fancy 3D-and-the-like styling options my colleagues insist on using). The imperfections* of the document compatibility layer become a problem when working on the same document with people who use MS Office.
Using a virtual machine would probably work, too... if I had an infinite amount of Windows licenses. I can't use the license from my real-hardware install, as I still need Windows-on-real-hardware for a few things (to do with drivers and device flashing).
Using Office was the main reason why I had to reboot into Windows, and so I couldn't be happier with this setup. My productivity has increased a lot (no need to wait for reboots). Besides Office, I also use Wine to run the emulator of a platform for which I develop software (the emulator is not open source, and are not available for any Unix but OS X, which I don't have access too). So Wine does a really great job for me, doing things that I think can be called "effective usage" (in fact, I don't run any games under Wine).
* MS Office import/export is actually quite good for a FOSS piece of software, and while the "imperfections" are being perfected as new versions are released, Microsoft too keeps releasing new Office versions with more shiny features, so I understand the difficulty on keeping up with the compatibility on closed formats.
As far as Wine "catching up" to the newest stuff Microsoft releases being an ongoing game, the news is a bit better for Wine than for Libre Office. Wine only needs to implement the crazy new APIs Microsoft creates when they're actually being used by applications. At the very least this gives us considerable time leeway -- not having a Direct3D 10 implementation didn't hurt Wine much when every game kept having a Direct3D 9 fallback for a few years.
I would pay for such a packaging (separately from the key). What this gives me, is the latest compatible Microsoft Office in lockstep with a wine release. I would'nt even mind you charging a few bucks for every incremental packaging.
I daresay that this is a large enough pain point and people would'nt mind paying a few bucks. I would also argue that this would substantially improve the sell of Linux to enterprise customers who can have a decently working Excel at a click as opposed to the seriously cumbersome install on Windows.
Some games have a Linux binary as well (and unfortunately no source code), and yet the Wine one will work better. The Linux binary will be like "old-version-of-some-library.so not found" or "could not connect to X server", while Wine acts as a rock-solid stable graphics and gaming API!
The only sad thing is that relevant versions of Internet Explorer don't work in it, that would be very handy for testing something in multiple browsers.
Wow. That alone would get me to switch banks. Then again, the only thing I ever use the website for is to check my balance.
tl;dr Wine is usable for production work, anyone who claims it isn't is simply incorrect.
One Windows-only modding program is Lunar IPS (http://www.romhacking.net/utilities/240/), which patches ROM files using a custom patch format for GameBoy Advance games. Another program was Wii Code Manager (which now has a cross-platform replacement in Java), which let you select a subset of cheats from a database in a text file, then compiled those cheats into a GCT file so they could be applied to a game.
I’ve also used Wine to try out very small games, such those created in game jams. I wouldn’t want to play a game permanently like that, because the game saves might be locked into the Wine version and Wine might turn out to be too slow, but Wine is fine for trying out the game to figure out if I want to play it, or playing a simple game that doesn’t save.
Secondly to compile Python projects to .exe files using Pyinstaller. Wouldn't use this for paid projects but for fun side-projects it's great.
Also, certain Office apps work differently between Mac & Windows (in particular, Excel), and OpenOffice/LibreOffice aren't perfect replacements.
Maybe LibreOffice isn't perfect yet, but I believe it will get there.
If you find a reproducible import/export fidelity bug, ideally with a minimal test case, file a bug. They jump on those like attack dogs, and you can be reasonably sure it'll be fixed next version.
Of course, as a heavy Windows user, I want Aero. It just looks wrong to me without it. I also want my Windows to be as fast as it would be if booted natively, and I even occasionally play games inside VMs. To achieve this, VirtualBox translates the DirectX calls in the VM into OpenGL calls on the host. Rather than reinvent the wheel, VirtualBox uses libraries developed by/for WINE.
I also use WINE to run the odd Windows application or game under OSX or Linux. You can look up compatibility ratings of games on the Wine website, and for many it works absolutely perfectly. (For those where it doesn't, I sigh and reboot into Windows)
I think it's a great solution for playing old games or games that were never released for Mac OS in the first place. I used to play League of Legends using Wine until Riot released a native Mac OS X version.
OS X Wine skins for many games can be found at sites like Paul The Tall: http://paulthetall.com
1) Read files saved by thermal imaging camera (no Linux or Mac software available) 2) Extract data from OriginPro worksheet (no viewer for Linux) 3) Run Bloch solver for neutron precession in magnetic fields
powerpoint viewer
Some small programs I have developped on windows years ago
Win32 will be one of those "forever" technologies. Like COBOL and now Java.
It's clearly a long struggle with a horrible beast but they are brave souls for doing it.
I think this will all be increasingly significant with Steambox coming along so nicely.
Wine, for example, can play Planetside2 which is probably the one game that would keep me from getting rid of Windows over the longer term.
It's probably a project that is helping at least hundreds of thousands of people (maybe even millions), and it is getting quite mature, so I don't see any reason not to do it.
"cheaper"? Wine is free software, whereas to run Windows you need a Windows license.
At this stage working on something like wine seems like a misguided effort. I use windows as my primary desktop OS and it works well. For non-windows users, a vm solution would be way better than a kluge like wine.
If I still used Windows as my primary desktop OS, I wouldn't care about wine either, but then again I wouldn't be the target market, now would I?
I used Ubuntu as my primary Desktop during the stone age of Vista and even then, using Wine was a painful experience compared to just switching to Windows.
I agree on the effort part though : it's a lot of time loss on something less and less useful nowadays.
sudo port install wine
and it works! Of course I already have Macports installed, but this could be interesting to runs Windows apps alongside Mac apps.
Kidding aside, I think the world needs an iOSE on windows and linux