Basically all of the text parsing tools (awk, grep, etc). podman is critical for testing containers. Ansible. In that vein, working with git and ssh is nicer. I use VSCode with WSL workspaces and...
Basically all of the text parsing tools (awk, grep, etc).
podman is critical for testing containers.
Ansible.
In that vein, working with git and ssh is nicer.
I use VSCode with WSL workspaces and they always work better than the native Windows one.
These are the things I miss most when I'm forced to use Windows too. Stuff like helix, ripgrep, and bat. All of which actually do have Windows binaries, but installing and using them is so much...
These are the things I miss most when I'm forced to use Windows too. Stuff like helix, ripgrep, and bat. All of which actually do have Windows binaries, but installing and using them is so much more cumbersome on a GUI-oriented OS.
I've found Scoop to be great for adding stuff like that in Windows: scoop bucket add main scoop install main/helix scoop install main/ripgrep scoop install main/bat https://scoop.sh/#/
I've found Scoop to be great for adding stuff like that in Windows:
Yeah. There’s some good reason to fire someone using it seriously I’m sure, but it mostly manages to not screw up the basics that I need (or in one or two cases it wasn’t wingets fault). Still...
Yeah. There’s some good reason to fire someone using it seriously I’m sure, but it mostly manages to not screw up the basics that I need (or in one or two cases it wasn’t wingets fault).
Still it’s fasaaar from perfect but since it’s built in I start there
VisiData is a big one for me when I deal with big json dumps. It is a great tool for quickly parsing big files and getting basic information out of them.
VisiData is a big one for me when I deal with big json dumps. It is a great tool for quickly parsing big files and getting basic information out of them.
You have to be a bit deranged to use Emacs for anything, but if you are like I am then it's a cool bit of software. It runs really well in WSL2, whereas the native Windows port is kinda crappy and...
You have to be a bit deranged to use Emacs for anything, but if you are like I am then it's a cool bit of software. It runs really well in WSL2, whereas the native Windows port is kinda crappy and isn't really maintained. Personally I'm considering switching over to a MacOS + Linux dual booting setup, simply because MacOS is way closer to Linux than Windows is, since MacOS and Linus both derive from Unix. But I mostly do creative work with music and such with programming largely as a side hobby, so your needs may differ.
Yes, I find graphical Emacs (especially with the Lucid toolkit) really snappy in WSLg, compared to the native Windows Emacs. At least the version of the later that I have likes to open a console...
Yes, I find graphical Emacs (especially with the Lucid toolkit) really snappy in WSLg, compared to the native Windows Emacs. At least the version of the later that I have likes to open a console window. It just feels janky by comparison.
I prefer Linux and use Emacs for everything, but I work at a Windows shop. WSL has been a godsend. I pretty much live in a Windows Terminal interacting with WSL with a graphical Emacs window always open. It's my own little sandbox that sits outside of all the IT-managed stuff. But then I still have all the Office 365 apps that I need for the corporate stuff.
Most command line software. Even if the tool I'm using has a Windows version, I'm just more comfortable with Bash than PowerShell. PowerShell really excels when it comes to writing highly readable...
Most command line software. Even if the tool I'm using has a Windows version, I'm just more comfortable with Bash than PowerShell.
PowerShell really excels when it comes to writing highly readable scripts thanks to its syntax and verbosity, but these same qualities make it painful to use as an interactive shell.
I've yet to dive deep into powershell, but it seems mostly useful for managing Windows and other Microsoft software (like SharePoint), which requires loading in different modules. As you said, the...
I've yet to dive deep into powershell, but it seems mostly useful for managing Windows and other Microsoft software (like SharePoint), which requires loading in different modules.
As you said, the commands are very verbose, but does it have a lot of usefulness beyond MS SysAdmin?
Not necessarily, its job is to facilitate automating software deployments, server maintenance, and other SysAdmin-like stuff. They intended that the primary way to use PowerShell would be with...
Not necessarily, its job is to facilitate automating software deployments, server maintenance, and other SysAdmin-like stuff. They intended that the primary way to use PowerShell would be with PowerShell ISE or some other code editor rather than an interactive terminal.
If I have to compile something, I'd much rather it be in Terminal land than have to play around in Visual Studio, so make and gcc and the rest of the build-essential suite.
If I have to compile something, I'd much rather it be in Terminal land than have to play around in Visual Studio, so make and gcc and the rest of the build-essential suite.
Does Dolphin count? File Explorer is painful. I like Linux because it by and large lets me do a lot with the command line, generally my GUI apps are cross platform or Windows only. Edit:...
Does Dolphin count? File Explorer is painful.
I like Linux because it by and large lets me do a lot with the command line, generally my GUI apps are cross platform or Windows only.
Edit: specifically, I like Dolphin having split view and tabs, they're productivity musts, on top of a functioning search. The overall interface feels cooperative to how I use a computer as well.
Basically all of the text parsing tools (awk, grep, etc).
podman is critical for testing containers.
Ansible.
In that vein, working with git and ssh is nicer.
I use VSCode with WSL workspaces and they always work better than the native Windows one.
These are the things I miss most when I'm forced to use Windows too. Stuff like helix, ripgrep, and bat. All of which actually do have Windows binaries, but installing and using them is so much more cumbersome on a GUI-oriented OS.
I've found Scoop to be great for adding stuff like that in Windows:
https://scoop.sh/#/
Don’t know about the others but helix is just a winger install last I tried?
I always forget that winget is a thing now.
Yeah. There’s some good reason to fire someone using it seriously I’m sure, but it mostly manages to not screw up the basics that I need (or in one or two cases it wasn’t wingets fault).
Still it’s fasaaar from perfect but since it’s built in I start there
VisiData is a big one for me when I deal with big json dumps. It is a great tool for quickly parsing big files and getting basic information out of them.
You have to be a bit deranged to use Emacs for anything, but if you are like I am then it's a cool bit of software. It runs really well in WSL2, whereas the native Windows port is kinda crappy and isn't really maintained. Personally I'm considering switching over to a MacOS + Linux dual booting setup, simply because MacOS is way closer to Linux than Windows is, since MacOS and Linus both derive from Unix. But I mostly do creative work with music and such with programming largely as a side hobby, so your needs may differ.
Yes, I find graphical Emacs (especially with the Lucid toolkit) really snappy in WSLg, compared to the native Windows Emacs. At least the version of the later that I have likes to open a console window. It just feels janky by comparison.
I prefer Linux and use Emacs for everything, but I work at a Windows shop. WSL has been a godsend. I pretty much live in a Windows Terminal interacting with WSL with a graphical Emacs window always open. It's my own little sandbox that sits outside of all the IT-managed stuff. But then I still have all the Office 365 apps that I need for the corporate stuff.
Most command line software. Even if the tool I'm using has a Windows version, I'm just more comfortable with Bash than PowerShell.
PowerShell really excels when it comes to writing highly readable scripts thanks to its syntax and verbosity, but these same qualities make it painful to use as an interactive shell.
I've yet to dive deep into powershell, but it seems mostly useful for managing Windows and other Microsoft software (like SharePoint), which requires loading in different modules.
As you said, the commands are very verbose, but does it have a lot of usefulness beyond MS SysAdmin?
Not necessarily, its job is to facilitate automating software deployments, server maintenance, and other SysAdmin-like stuff. They intended that the primary way to use PowerShell would be with PowerShell ISE or some other code editor rather than an interactive terminal.
If I have to compile something, I'd much rather it be in Terminal land than have to play around in Visual Studio, so
makeandgccand the rest of thebuild-essentialsuite.Does Dolphin count? File Explorer is painful.
I like Linux because it by and large lets me do a lot with the command line, generally my GUI apps are cross platform or Windows only.
Edit: specifically, I like Dolphin having split view and tabs, they're productivity musts, on top of a functioning search. The overall interface feels cooperative to how I use a computer as well.
In my humble opinion, everything counts. I'm interested, but also for anyone else who stumbles across this thread in future :)
FSL and Freesurfer suites for neuroimaging data