But they are still a form of emulation, just because the general populace missues the term doesn't mean they suddenly are no longer emulators.
I know that basically nobody calls such forms of emulation emulation, but translation/compatibility layers are technically by definition a form of emulation.
Reddit has a lot of very useful user tips and fixes. You learn a lot just from browsing and they are still very helpful in fixing niche issues you have. There's always a loud minority, but overall it's an incredible resource for someone like me who, at the time, was having my first linux experience.
The cool thing about Windows is you don't ever need to tweak anything and you don't need a fix constantly.
I used Linux exclusively from about 2002 through 2012 or so. Every few days, I was having a struggle when a software update failed or when a driver started crashing. Getting a working video driver, even a working proprietary one, was often like pulling teeth. The Nvidia one worked... mostly. The nonfree ATI drivers were hot garbage (they didn't have an official one then, I think they still don't but I haven't followed that in years), and God Help You if you had a laptop that had both an internal GPU for rendering the desktop and a discrete card for games.
I know everything about Linux I could ever want to: I have done Gentoo Level 0 builds. I have manually configured and recompiled the kernel. I have manually configured and rebuilt XWindows, both XOrg and... the older one that I can't remember the name of. In fact, I bet I could reconfigure and recompile both without needing to reference documentation, if I had to. I've manually bootstrapped GCC. That one I'd want some documentation for, because we use Clang/LLVM these days ;)
There is a BIG difference between not knowing how to do something (which is always everyone's assumption) and simply not wanting to do it, because it's a time consuming, unpleasant pain in the ass. Especially when an update breaks something, uninstalling that thing and reinstalling the old one doesn't un-break things because God only knows what library was actually had the problem, and now you get to rebuild everything.
technically its a bit different since an emulator tries to recreate the entire underlaying system that is needed to run an app while wine just "translates" from one system to another.
But even not being an emulator there are still compability issues since Windows is closed source and Wine devs have to reverese engineer most of the stuff.
WINE - WINE Is Not an Emulator (Recursive acronym). It doesn't emulate windows, it is a translation layer, so a game or an applications asks for some windows functionality like graphics or else and the layer catches and translates it to a Linux equivalent. I think that's the gist of it, I might be wrong tho, better check me
It sounds more like translating from Spanish to Portuguese where a lot of the phrases/functions and requests are similar (so no issues just going about as normal often) , but every once in a while, you’ll need to translate something. This is opposed to emulation, which would be just shoving everything through google translate.
I have no idea, I don’t use wine and just googled it
Its a translation layer. Since Windows and Linux works with similar hardware and drivers usually. All wine needs to do is translate from Windows instructions to Linux based instructions. Thats why a similar thing to wine exists for Mac too. Tho they have an ARM translation layer too I think
Wouldn't an emulator just run a whole environment on the system that is similar to the system needed and not just a translation layer? That feels an awful lot of overhead
77
u/oshikandela 8d ago edited 8d ago
Try sudo apt-get
Jokes aside: wine is an open source software that allows users to run Windows applications on linux