4 ms·
What's so well integrated with atrocious IO speeds between boundaries?
by eviks 3y ago
What's so well integrated with atrocious IO speeds between boundaries?
- ActorNightly 3y agoI think you mistook this for reddit.
- mardifoufs 3y agoWasn't that mostly on wsl1?
- eviks 3y agovice versa, wsl2 is the true VM that truly suffers https://vxlabs.com/2019/12/06/wsl2-io-measurements/ https://vxlabs.com/2019/12/06/wsl2-io-measurements/
- baq 3y agonot a problem if you don't cross them - my wsl2 disk image took more space than the windows install. I basically used windows as a web/email/chat client and a terminal to the real system, which was wsl2.
- eviks 3y agoBad integration is a problem with integration even if you personally do no integration
- baq 3y agoTo each their own. I consider it great at what it does. It has limitations but what doesn’t? It’s a tool, use it, or don’t - I use it, it works for me.
- eviks 3y agoGood for you, but also irrelevant to the argument
- baq 3y agoAbsolutely not - the integration is perfectly fine, for me.
- eviks 3y agoit's not the integration that is perfectly fine for you, but the lack thereof since you simply don't use it
- baq 3y agoI use the \\wsl$\ to get an occasional file out of wsl2 super easily, vscode remote wsl, the shared localhost interface and a wsl2 gui app every once in a blue moon. Don't think it's nothing. What I don't use: files on the windows fs from wsl2 for continuously or vice versa.
- eviks 3y ago> What I don't use: files on the windows fs from wsl2 for continuously or vice versa. Exactly, your "occasionally and once in a blue moon" is close to nothing (but I agree, it's not nothing)