Google very much cares about chrome. Chrome, especially when you have syncing enabled, sends a huge amount of data about your web usage back to google. That data is worth a huge amount of money to them.
the problem is that all the compatibility stuff in msys2 just doesn't quite work right. it's not that it's buggy, it's due to what it's trying to do: provide a compile-time windows/posix compatibility layer. which, of course, is impossible. it has to make tradeoffs.
wsl is the better cygwin. it's kernel-mode. it's distro-agnostic. and the compatibility is excellent.
no. if you edit wsl distro files with windows tools, you might mess things up if you're not careful. but similarly if you mess with a native linux distros system files and you're not careful you can also mess things up. i edit my own wsl files in both ubuntu & wsl tools all day long and i have never run into any issues. i even have some files open in editors in both environments and i see updates in one tool (eg ubuntu vim) appear in the other tool (eg win32 vscode). but i don't edit sensitive system files in notepad, for example, because i'm not an idiot.
wow, your use case must be really different from mine. i have never needed to do any of these things from ubuntu/wsl and i have been using it since it was made public. the only thing i have found that doesn't work correctly is openconnect, and that's because they haven't implemented the TAP interfaces yet. it doesn't really matter as i can just run the win32 version of openconnect just fine.
If you mount your file system in vbox so both machines can see the same file and you modify it at the same time with programs on both machines then youâ(TM)ll get corruption.
Same thing in wsl.
I recommend thinking a little more before posting.
Itâ(TM)s a single operating system, remember, windows. It just happens to be able To run elf binaries. The same issues arise if you run any two applications that mess with the same files without adequate locking.
The point is that wsl uses zero ram when youâ(TM)re not running anything in it. Whereas a vm is either using ram doing nothing, or is taking time to boot. Why bother with that unnecessary nonsense?
Thatâ(TM)s because they encoded the Operand types into the Opcodes, thus limiting them to a fixed set of native types.
CIL, on the other hand was designed with a validating JIT in mind so the type of every stack location can be statically determined at JIT time making it unnecessary to encode those types in the opcodes.
Slashdot Mirror
One has to wonder, if such regulations were in place in the 90â(TM)s, would to world-wide-web ever have been born?
Maybe you should try teaching c++ without ânewâ(TM)?
Britney Spears.
Popularity does not equal quality.
Bad languages make good code more expensive.
there's a difference between forcing the creation of new keys and bricking the device.
âoeVarious reasonsâ are bugs in the drivers. Itâ(TM)s quite clear in the article.
1971 will be the year of the Linux desktop!
Google very much cares about chrome. Chrome, especially when you have syncing enabled, sends a huge amount of data about your web usage back to google. That data is worth a huge amount of money to them.
Remember: if you walk without rythm, you won’t attract the worm.
the problem is that all the compatibility stuff in msys2 just doesn't quite work right. it's not that it's buggy, it's due to what it's trying to do: provide a compile-time windows/posix compatibility layer. which, of course, is impossible. it has to make tradeoffs.
wsl is the better cygwin. it's kernel-mode. it's distro-agnostic. and the compatibility is excellent.
no. if you edit wsl distro files with windows tools, you might mess things up if you're not careful. but similarly if you mess with a native linux distros system files and you're not careful you can also mess things up. i edit my own wsl files in both ubuntu & wsl tools all day long and i have never run into any issues. i even have some files open in editors in both environments and i see updates in one tool (eg ubuntu vim) appear in the other tool (eg win32 vscode). but i don't edit sensitive system files in notepad, for example, because i'm not an idiot.
wow, your use case must be really different from mine. i have never needed to do any of these things from ubuntu/wsl and i have been using it since it was made public. the only thing i have found that doesn't work correctly is openconnect, and that's because they haven't implemented the TAP interfaces yet. it doesn't really matter as i can just run the win32 version of openconnect just fine.
Why would you want to run a whole other OS with all its overhead just to run a few user-mode programs once in a while?
It doesnâ(TM)t use hyper-v. Itâ(TM)s not a VM.
If you mount your file system in vbox so both machines can see the same file and you modify it at the same time with programs on both machines then youâ(TM)ll get corruption.
Same thing in wsl.
I recommend thinking a little more before posting.
In many cases, the ting that makes the most sense is backwards compatibility.
Itâ(TM)s a single operating system, remember, windows. It just happens to be able
To run elf binaries. The same issues arise if you run any two applications that mess with the same files without adequate locking.
The point is that wsl uses zero ram when youâ(TM)re not running anything in it. Whereas a vm is either using ram doing nothing, or is taking time to boot. Why bother with that unnecessary nonsense?
More complete? Err, not even close, son.
Why should it be up to one person? The mandatory min/max represent the will of the people (via their elected representatives in legislature).
can someone do a study to see if there's a link between teen aggression and having assholes for parents?
maybe we can pass legislation to ban those?
Microsoft doesnâ(TM)t make a C compiler. VisualC++ is just that a C++ compiler (that just happens to compile some C programs).
Thatâ(TM)s because they encoded the Operand types into the Opcodes, thus limiting them to a fixed set of native types.
CIL, on the other hand was designed with a validating JIT in mind so the type of every stack location can be statically determined at JIT time making it unnecessary to encode those types in the opcodes.
Works great for me.
Chocolatey for win32 apps, apt for Ubuntu/wsl.