🎉🎉🎉
Yet another major release that fails do support basic Win32 APIs available since Windows 95 properly.
🎉🎉🎉
Instead of leaving snide comments like this, you can use your head to open up an IDE, implement the features you want, and make a pull request. Keep it to yourself
Not without getting sued, no. But you could do a double blind on it. One person reads it and describes it in freeform prose, and another reads the prose then writes code to implement it as described. In the absence of documents describing the implementation details, this can sometimes work as it will avoid the copyright argument.
Still sketchy though, and you’d really have to verify isolation.
It’s a miracle we have wine at all, reverse engineering an entire operating system isn’t easy. Be grateful for what we have (which is already enough to run a ton of software really well)
Hasn’t ReactOS been accused of using code that was not reverse-engineered multiple times? If they became too big MS would probably just sue them.
reverse engineering an entire operating system isn’t easy
Have you noticed the the NT / Windows XP source code was leaked years ago. There’s isn’t much of a need to “reverse engineering”, it’s just about reading their implementation and providing an alternative implementation that doesn’t copy code…
it’s just about reading their implementation and providing an alternative implementation that doesn’t copy code…
That sounds difficult though. Didn’t companies have to set up ethics walls to protect against lawsuits for things like that?
Too bad time isn’t refundable. Free software is only free if you don’t factor in the time you spend making it work.
Wow, you’re the most entitled user of free software I’ve met in a while. Just buy a windows license next time.
It is called free because it allows you the freedom to hack the code and make it fit your needs, not because of cost. Like you say, freedome can be expensive, so go cheap and use authentic windows with a paid license, closed code binary blobs, and blind trust to the megacorp selling it.
All modules that call a Unix library contain WoW64 thunks to enable calling the 64-bit Unix library from 32-bit PE code. This means that it is possible to run 32-bit Windows applications on a purely 64-bit Unix installation. This is called the new WoW64 mode, as opposed to the old WoW64 mode where 32-bit applications run inside a 32-bit Unix process.
🦀🦀🦀
Come on Steam, show those 32-bit libs the door!
Not the political kind. The shared object kind.
Ok but now I am curious what the difference between 32 and 64 bit liberals would be
So in the future no need to install 32 bit packages of wine in a 64 system??? 👀
Correcto. Which means Steam will probably drop 32 bit libs soon. Which means Ubuntu will stop shipping 32 libs. The era is truly coming to an end
Let’s call it “soonish”. The old proton versions still need 32 bit libs if they do not backport the feature.
X86 to arm will become easier with this as box64 could handle everything now
Does this change run the 32-bit .exe using x86_64 instructions? From the description it just sounds like it allows 64-bit Linux libraries to be used in place of 32-bit ones, but that the Windows layer still operates in native 32-bit mode. This means there is still a need to emulate 32-bit x86 instructions which I don’t think box64 can do at this time (x86_32 translates to arm32 with box86, x86_64 translates to arm64 with box64). If box86 could translate x86_32 to arm64 then this might work as Wine would handle the conversion between 32 and 64 bit addressing and argument passing into the libraries but I’m not familiar with the inner workings there.
codeweavers the true gigachad of Linux
they managed to make their anti-microsoft crusade a sustainable and profitable venture
If you meant onlyoffice, then I think it promises better compatibility with ms office stuff and also itsinterface is closer to it, compared to libreoffice.
Wine nine you say? 🧐
There is nothing “worth” running in wine, but it is good to know it exists, just to spite those choosing binary blobs.
How about this then. While your neighbors are using wine, it attracts more commercial attention to develop the open source projects that you do actually use. It’s so impactful that you measurably benefit directly from its contributions, like optimizations to the Linux kernel.
You don’t have to agree with it, but you cannot deny the increased investment in open source projects it causes.
For a painfully blatant example see: Steam Deck.
Also for the binary blob purists, how do you feel about all that closed source firmware underpinning your pure world? Isn’t it practically impossible to get completely open source firmware down to the silicon? And even then, do you trust the silicon? Are you running everything on FPGAs?
Hi! “Binary blob purist” here! Yes, it bothers us that so much firmware is proprietary, but we are working to fix that :).
It is possible to have fully free firmware on certain select devices.
The silicon is unchangeable, much like a chair is unchangeable. So being concerned about changing it isn’t really productive. But, RISCV looks promising and a good remedy to the issue of not knowing what it does.
FPGAs would be nice but they aren’t powerful enough yet.
But, at the same time, unless the silicon can make outside connections itself or modify behaviour (a la Intel ME), or has been updated with what is essentially software baked into it that can change it’s behaviour on the fly, I’d say it can be trusted to do the computing you tell it to do and nothing more (again, excluding those processors where we know that it doesn’t like those with the ME).
As a Linux gamer, I run just about everything in wine since proton uses wine.
I even run native games through Proton at this point since many native builds don’t work properly.
I have done that before as well. I had a native game that randomly stopped working after a borked update or something. I downloaded the proton version instead, and it worked perfectly.
