4 ms·
I'm in the middle of installing Windows for business purposes, and this is far from my experience. I've yet to see it "just work." Installation was a hassle! T
by cybernautique 5y ago
I'm in the middle of installing Windows for business purposes, and this is far from my experience. I've yet to see it "just work."
Installation was a hassle! THREE hours just staring at a various setting-up screens. And then it has the gall to bully me for using an offline account; it screeches about my "diminished experience" because I refuse to accede to its native advertising. Want to uninstall Edge? Sorry, your moral superiors at Microsoft decided it's better for your own good that you don't.
Now I'm having to jump through hoops to figure out how to get it to use a shared directory, all because Microsoft decided they _just_ had to cut its own path through the CLI jungle as opposed to just using bog-standard bash.
The ecosystem seems user-hostile and full of more bullshit than any amount of Linux. I just don't see it.
- lavabiopsy 5y agoNit pick: Bash is only standard on GNU, it has never been standard anywhere else. You may be thinking of the Bourne shell, although neither bash nor the Bourne shell include a standard for shared directories, so I'm curious what you mean is bog-standard there.
- cybernautique 5y agoI'll have to review my shell terminology; however, I'll assume you're correct here, and in that case I'll eat crow on both points. I appreciate the nit-pick! It's good information, and an obvious blind-spot that I should improve upon. The "bog-standard" I'm referring to is my ability in various Linux distros to easily find and mount network-shared directories. I assumed this was some power of bash, but if not then I'll reflect on that and find whichever utility enables the ease of my workflow.
- lavabiopsy 5y agoAre you mounting them on NFS or using samba? That wouldn't be bash. Under windows you would just type the SMB path name.