Slashdot Mirror
Wine 1.2 Release Candidate Announced
An anonymous reader writes "After evolving over 15 years to get to 1.0, a mere 2 years later and Wine 1.2 is just about here. There have been many many improvements and plenty of new features added. Listing just a few (doing no justice to the complete change set):
many new toolbar icons; support for alpha blending in image lists; much more complete shader assembler; support for Arabic font shaping and joining, and a number of fixes for video rendering; font anti-aliasing configuration through fontconfig; and improved handling of desktop link files. Win64 support is the milestone that marks this release. Please test your favorite applications for problems and regressions and let the Wine team know so fixes can be made before the final release. Find the release candidate here."
15 years to get to 1.0? That is seriously slow development.
"There is a way that seems right to a man, but its end is the way of death." Proverbs 16:25 (NKJV)
huh when did we get to v1.0?
he who controls the spice controls the universe
Maybe it helped some who wanted to run Windows app on Linux, but you know, you know, it's the wrong way to go about. Linux has now become a force in the industry. Encourage them to write "native" software.
* frowns at emulator tag *
That's a 0.1 version increase every 18 months, no?
So they've got a year to get rid of that darn "Candidate" tag if they wanna stay on schedule!
...to about 2500 people who actually use this stuff. All the rest of us are just, "ugh".
One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be the Amazing Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood.
FreeBSD is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.
Let's keep to the facts and look at the numbers.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS dilettante dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.
Fact: *BSD is dying
It's supposed to provide better emulation, everything redesigned. Now for the first time, WINE/BEER will be 100% Italian free and protected from Italian code execution attacks.
UNITE with the Campaign for a Free Internet because today, our future begins with tomorrow!
Pulling numbers out of your ass sure is a fun way to troll isn't it?
That's what me and my 1,337 friends on facebook think anyway.
Does it run Linux?
That Anonymous Coward guy is pretty annoying. Can we have the government censor him or something?
There was a time and place when I was hoping for WINE to get solid. I hated Windows XP, and I hated Windows Vista. I used CrossOver Office hoping for the day that WINE would finally work. But now I have Windows 7 x64. It has been the best operating system I have ever used. It's compatible with all the programs I use. It is stable, and when there's a crash, it's usually only the apps crashing. I use Microsoft Security Essentials, MalwareBytes Anti-Malware, and Norton Internet Security 2010 to keep my computer free of spyware. But aside from a sketchy program I downloaded and ran with administrator privilege, my computer hasn't been compromised. Other than doing that, my computer has been fine. It works really well with multiple monitors and outputting stuff to my TV via HDMI. The GUI toys are nice, of course.
Long rant short, WINE is solving a problem I don't need an answer for anymore.
A NYC lawyer blogs. http://www.chuangblog.com/
... a tad late. :( ); these days thanks to SUN Microsystems (anyone remembers??) I fire up my Virtualbox, and chances are, the application works.
While I was fiddling with some Windows applications over the last 10 years, to make them work in wine (not too high a success rate,
Has one made some comparison of speed, resource usage, of major applications between running in wine and running in Virtualbox? Google has a few hits, though of old age.
What does OS X have now? 10 times the marketshare of Linux?
Yeah, keep talking smack dipshit.
15 years to get to 1.0 means a speed of a 0.0666 increase in the version number per year. This extrapolates to 3 more years to get to 1.2. So it's not surprising to see a RC only two years later.
(this post just nominated for the "worst use of extrapolation 2010" award)
My first program:
Hell Segmentation fault
the third option is to make Portable Executables (aka windows executables) native to linux. WINE doesnt make PEs native, it runs them in userland.
so the solution is to make a binary format loader for the linux kernel and shared libraries so that it runs like the real deal.
there's a new project doing this too: binfmt_pe
A $200 retail copy of Windows for virtualization on a desktop PC is not much cheaper than a $200 Acer Aspire Revo PC running Windows. Yes, you need to buy a KVM switch, but the Revo comes with a spare keyboard and mouse to make up for that. The best part: your Windows apps won't slow down your native apps.
Software cannot be implemented without adhering to a set of defined rules.
There are two sets of defined rules. One of them is the MSDN documentation for the Windows platform. Another less defined set is that a specific suite of programs, which by 1.0 included Office 2007 viewers, has substantially the same behavior on Wine as on Windows.
well, it's emulating a platform API (as opposed to hardware)
Any more than a Linux PC's X server "emulates" the X API? Or your Qt library "emulates" the Qt API? If you use the term "emulator" to refer to anything that doesn't involve interpreting or dynamically recompiling machine code, that cheapens "emulator" to the point where every library on your system is an emulator. Where I come from, Wine is called a "subsystem", just like Qt and Gtk+ are "subsystems".
I wouldn't mind helping, but: I'm not going to update from Jaunty just to test something "better" than Wine 1.0.1, the synaptic pkg in Jaunty. I would like to see Many Faces of Go work right (no screen artifacts, especially in drop shadows), but JellyFish Lite 3.5 works. Fallout and Fallout 2 used to work under the previous Wine. The only things I want to run are the Windows versionx of SmartGo and Rosetta Stone. Everything else does just fine in Sun's Office. Is Wine 1.2 going to be great? Depends how fast they get it to Ubuntu. And whether Canonical thinks it matters to support anything older than Lucid.
``Tension, apprehension & dissension have begun!'' - Duffy Wyg&, in Alfred Bester's _The Demolished Man_
I use Wine myself and it seems to work for a lot of the games (albeit, sometimes its quirky).
I always wondered if Wine devs are taking the wrong approach to this: Instead of rewriting all the win32 DLLs, why not first write all "non-portable" DLLs, then worry about rewriting rest of the DLLs at later time.
What I mean is, most of us have a copy of windows somewhere (its almost impossible to buy a notebook without windows preloaded :-/ ), so instead of rewriting files like mfc42.dll, why not just copy those files from win32 for the time being, and first worry about just writing the stuff that one cannot copy.
The advantages are two fold:
1) wine would work for everything much sooner
2) as more people use it, more devs would sign up to help
Look at it logically: if you have a win32 app that you want to run, that means that you already have a copy of windows that the app runs on.
So,
1) Write just the necessary components
2) Copy missing win32 DLLs
3) Run application
4) Rewrite "portable" DLLs as time sees fit
5) profit
The only reason why I have windows even around is because I play games on occasion :-/
If I could pop in my windows CD and copy few DLLs off of it when I want to install a windows game, I would buy beer for all the wine developers.
http://bugs.winehq.org/show_bug.cgi?id=6971
This bug causes a large number of games to be unplayable. Basically, your mouse leaves the Wine window when you try to turn 360 degrees. It applies to all Unreal II engine games that I've tried and others as well.
Just consider that one of the BIG targets, namely Windows XP was a sitting duck for something like 6 years (XP Released in 2001, Vista released in 2007 to the general public)... And WINE was not able to get there...
Also, remember the metafile fiasco?.
WINE had excatly the same error. And I will take none of that "they are replicating the functions" crap.
If the WINE team had recognized this metafile crap as a security vuln themselves, they would have boasted about it from here to mars and back, and then added a line in the config files of the form:
WinMetaFileFlaw=x;
[X=0 -> Vuln allowed; X=1 -> WINE team Fix; X=2 -> Reserved to emulate Microsoft fix if and when they release it].
So yes, They had the target sitting still for 6 years and could not catch it. Long live wine!!!!
PS: Now that the folks at ReactOs saw the light and did the changes, maybe we can expect more of both ReactOs AND WINE. First ordder of the day, find a big corporate sweet daddy (like Symian, Eclipse, Xen, et al)!
PS2: Well, I have some good karma I can burn today.
PS3: I am not beein a troll, is my long standing opinion, so if you want to mod me down do it, but not with troll.
*** Suerte a todos y Feliz dia!