Wine is usually called from the command line interpreter: wine program.exe.  Wine implements the Windows Application Binary Interface (ABI) entirely in user space rather than as a kernel module. Wine largely mirrors the hierarchy, with services normally provided by the kernel in Windows rather than provided by a daemon called wineserver, whose job is to implement basic Windows functionality as well as integration with the X Window System and translation of signals into native Windows exceptions. Although Wineserver implements some aspects of the Windows kernel, it is not possible to use native Windows drivers with it due to Wine`s underlying architecture.  Bob Amstadt, the original project leader, and Eric Youngdale started Project Wine in 1993 to run Windows applications on Linux. It was inspired by two Sun Microsystems products, the Wabi for the Solaris operating system and the Public Windows Initiative, which was an attempt to completely reimplement the Windows API as an ISO standard, but was rejected in 1996 under pressure from Microsoft.  Wine originally targeted 16-bit applications for Windows 3.x, but as of 2010 it focuses on both 32-bit and 64-bit versions, which have become the standard on newer operating systems. The project grew out of discussions on Usenet in comp.os.linux in June 1993.  Alexandre Julliard has been leading the project since 1994. Preliminary support for 64-bit Windows applications was added to Wine 1.1.10 in December 2008.  As of April 2019[update], support is considered stable.
The two versions of Wine are built separately and, therefore, simply building wine64 creates an environment in which only x86-64 applications can run.  Wine staging is a set of aggressive, independently managed patches that are not considered ready to be merged into the Wine repository by the WineHQ developers, but are nonetheless considered useful by the wine-compholio fork. It mainly covers experimental features and bug fixes. Since January 2017, the patches in the wine staging have been actively integrated into the WineHQ upstream, as wine-compholio transferred the project to Alistair Leslie-Hughes, a key developer of WineHQ.  I would say that wine tricks are completely legal, the responsibility lies with you. There`s the winecfg utility, which launches a graphical user interface with commands to customize the basic options.  This is a GUI configuration utility included with Wine. Winecfg makes setting up Wine easy by eliminating the need to edit the registry directly, although this can be done using the included registry editor (similar to Windows regedit) if necessary. Wine depreciated the libwine library. Applications that explicitly call libwine functions must be modified to call equivalent Win32 or Unix APIs instead. As a result, the wine/library.h header has also been removed,” says the Wine project. It asks for winetricks that download the original Windows code, not Wine itself.
In a 2007 desktoplinux.com survey of 38,500 Linux desktop users, 31.5% of respondents reported using Wine to run Windows applications.  This majority was larger than all x86 virtualization programs combined and higher than the 27.9% who reported not running Windows applications.  By default, Wine uses special Windows versions of Gecko and Mono to replace Microsoft Internet Explorer and the .NET Framework. Wine has built-in implementations of JScript and VBScript. It is possible to download and run Microsoft installers for these programs via winetricks or manually. I would like to know if it is legal to install the msttcorefonts package and also if installing the Windows software with Wine is also legal? I currently live in Brazil and don`t know what specific rules apply here. Just a “basic” question. If we upload things like .net and vcrun on winetricks without a proper Windows license, isn`t that piracy? The choice of “Wine is Not an Emulator” as the name of the Wine Project is the result of a discussion over the name in August 1993 and was attributed to David Niemi.
There is some confusion caused by an early FAQ with the Windows emulator and other invalid sources appearing after the Wine project name was defined. There is no code emulation or virtualization when you run a Windows application on Wine.  “Emulation” generally refers to the execution of compiled code for one processor (e.g., x86) by interpreting/recompiling software running on another processor (e.g., PowerPC). Although the name sometimes appears in the forms WINE and Wine, the project`s developers agreed to standardize the form Vin.  I`m not a lawyer, but in general, packages included in Ubuntu`s official repositories are not burdened with copyright or patent restrictions that would make installation a misdemeanor or crime.