this post was submitted on 12 Aug 2023
427 points (95.7% liked)
Asklemmy
43945 readers
650 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You should be using the best tool for the job, even when it comes to operating systems and software. If your development workflow is this heavily dependent on Linux then I'm not surprised you find it Windows more painful compared to just running Linux itself.
For myself, mostly doing enterprise and backend development in C#, Python and a bit of Go, Windows gets out of my way and let's me get to work far more efficiently than Linux ever does for this work.
Obviously. That's literally my point.
I believe my workflow is more efficient because it's just frictionless to me. Everything makes sense and is intuitive without the need of a guide (like the GUI), if it isn't then you can change it or work around it much easier, if it doesn't exist then you can DIY. Sure it's more advanced this way, but not time-consuming when you have the knowhow.
That's why Windows isn't particularly suited for me. The same concept doesn't exist in Windows, you're fundamentally stuck with whatever Microsoft decides to be part of Windows, their proprietary software and their support for plugins or lack thereof (Vim doesn't even work well on Visual Studio), or even their open-source projects like Powertoys. Functionality used for a more efficient workflow sometimes has a proprietary solution, often paid, often enough making it yourself isn't feasible because Microsoft locked it down.
Postscript:
As a result, I ended up with a setup that's more complicated for regular Windows users vs. regular Linux users where everything seems intuitive, sometimes because the OS was designed to force you to learn using the tools it gave you at the surface level.
My colleagues that use Windows are even surprised that I'm more used to navigating and multitasking at it than they do, where I usually know some little trick or shortcut that they don't use (which is pretty confusing for me when they're not even aware that something like it exists). Not necessarily saying I know more than an average enthusiast, nor I know more than the people mentioned above when it comes to their particular field of study or job. But whenever I pull off something, they always see it as magic and start integrating that to their workflow.
The best tool for the job, for someone who treats the OS like a full-stack devbox, has always been Linux. You don't need a mouse or navigation keys, but of course there's a learning curve. You don't need external applications, you can go as bare as a simple Neovim+LSP setup, ZSH with Vi keys. The operating system is your IDE. And you can always bring it with you.
I always bring my laptop on the go, usually you can't even fit a mouse in that bag. Why not use what the laptop already comes with? The laptop has very small buttons when it comes to navigational keys. Vim works best for this keyboard layout in this case.
Linux isn't necessarily the best of everything, and it never was supposed to be in the first place. I iterate that I often find everything in Linux to be less tedious. In fact, deploying with Windows Server containers are pretty annoying, though with the added benefit that it's a simple tickbox in the Server Manager to install the feature, but actually using them compared to say Docker...you get my point.
What you don't know doesn't hurt you, nor it should. Likely to apply to me as well with things that I'm not aware yet of. Never stopped anyone as you're free to use whatever you wish, what you feel is the most efficient for you.