Slashdot Mirror
Wine Goes 64-Bit With Wine64
G3ckoG33k writes "Wine (Wine Is Not an Emulator) is a popular way to run Windows programs on Linux, and it has an impressive compatibility list. After 15 years of development it reached version 1.0 a few months ago. Now, Wine developer Maarten Lankhorst has succeeded in running 'Hello World' in 64-bit, natively! The 64-bit variety is unexpectedly named Wine64."
Meh. You can use unmodified Windows libs in WINE too.. the point, that you obviously missed, is that you can run Windows apps without Windows libs (or Windows) using WINE.
How we know is more important than what we know.
Not that impressive, unless all you want to do is game. If adding an application to its compatibility list is just a popularity contest, and it seems that is all that it is, of course the fan boys interested in games will vote the most. Others will just use the 'other' operating system to run applications that they need to use in order to make a living (since they won't be able to outvote fanatic gamers). Linux/Gnu has to relax more, not less, in order to allow people to NOT have to rely on some emulator or flaky reverse engineering to make business tools work. Relax on APIs so that it is easier to port business applications over to Linux. Until that time there will never be a 'year of the Linux desk top'. People just want to use their tools, not build them.
-- I ignore anonymous replies to my comments and postings.
most apps will run on most platforms without extra work. Or so I hope (desktop or notebook, don't see a way to make a destop app fit on a phone w/o work). They'll have an interpreted code, like lisp, which gets compiled (once, not at runtime) for whatever specific platform it's actually running on. It can be fast, doesn't have to be slow this way.
So it won't actually be like a script. Java tried to be this universal gateway, but it just never really took off for real apps like a language should. Various libraries like QT attempted to overcome the problem. Then there is the POSIX standard, which wouldn't be bad if it was really followed.
I just feel it's ridiculous in this day and age being tied to windows/unix/os x/some operating system because of an app made for it. It seems backwards. It's like being tied to route 66 because that's the only road your car will drive on.
Every time I read about Wine, I shrug and/or roll my eyes. I've tried many times to use it, but it simply does not work for the handful of Windows apps I actually need. I gave it another try just a few months ago, and I was again left high and dry, so I turned yet again to virtual machines. At this point, I have stopped caring about the project.
For the inevitable flamers among you, here's the short list of Windows apps I need, that Wine fails to support:
- Photoshop CS3
- Office 2007
- MSIE 6/7
IE6 runs, sure, but leaks memory like there's no tomorrow, so I have to kill -9 it after a few minutes lest I face a swap-spiral of doom. And don't try to tell me to use The Gimp and OO.o, I don't need "A photo editor" and "An office suite", I need those specific apps because those are the formats my peers and clients use. If it were just me in my little bubble, I'd be quite happy with unbranded alternatives, but my rent doesn't pay itself.
Now one would think that these major apps would be high on the priority list, as I'm hopefully not the only (commercial) web guy trying to use Linux as a serious desktop, and getting them to run perfectly would effectively make Windows redundant for a large number of people, not just web devs. I find it puzzling that Wine can run something like World of Warcraft, but not MS Outlook. Don't get me wrong, I loves me some Warcrack, but it doesn't pay my bills.
-Billco, Fnarg.com
I don't agree w/ Eric on this one. The shift from 32-bit to 64-bit systems has been darn near seamless as compared to previous transitions. That's a far cry from the 8-to-16 jump or the 16-to-32 jump.
Honestly, most people can't tell that they've shifted from 32-bit to 64-bit. If there wasn't a dialog box or a sticker that told them they'd switched, they wouldn't know.
Now this wouldn't be /. without a bad car analogy. Going from 8-bit to 16-bit was like going from horse-drawn buggies to the early Model Ts--a big change. Going from 16-bit to 32-bit was like going from these early, slow cars to the more recognizable cars of the 30s onward. Cars that actually had starters and drove at reasonable speeds. Each step provided a noticeable difference in the travel experience and it brought with it a whole new round of infrastructure requirements.
Going from 32-bit to 64-bit is like going from a gasoline engine to a hybrid. Sure, it's a change in the underlying mechanism, but it doesn't fundamentally change the driving experience all that much.
Program Intellivision!
For asking about something which you are unfamiliar.
Such an attitude is refreshing, usually you just run into folks like the AC below who are a-holes.
However the link provided down below in this thread is a great place to start reading. Have fun!
I am very small, utmostly microscopic.
Except that it doesn't. Let's check their compatibility database: