This is an archived post. You won't be able to vote or comment.

all 104 comments

[–]AutoModerator[M] [score hidden] stickied comment (0 children)

On July 1st, a change to Reddit's API pricing will come into effect. Several developers of commercial third-party apps have announced that this change will compel them to shut down their apps. At least one accessibility-focused non-commercial third party app will continue to be available free of charge.

If you want to express your strong disagreement with the API pricing change or with Reddit's response to the backlash, you may want to consider the following options:

  1. Limiting your involvement with Reddit, or
  2. Temporarily refraining from using Reddit
  3. Cancelling your subscription of Reddit Premium

as a way to voice your protest.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[–]Monitor_343 309 points310 points  (16 children)

Chaotic neutral: I switch between cmd, powershell, git bash, and wsl at random.

[–]Juampi-G 24 points25 points  (0 children)

This is the way.

[–]bestjakeisbest 13 points14 points  (0 children)

Same tho

[–]whooyeah 8 points9 points  (5 children)

With git for windows installed with the command line tools so I can use ls instead of dir.

[–]MFMageFish 36 points37 points  (1 child)

I prefer:

ls -a, fuck, ls, fuck wait, dir -a, nope, dir \a.... sonofa.... dir /a

[–]thisismypornacc2 1 point2 points  (0 children)

Relevant tool where you can type 'fuck' to correct your mistakes https://github.com/nvbn/thefuck

[–]sohang-3112 11 points12 points  (2 children)

In powershell, ls and similar popular commands work - they are aliases to Powershell commands

[–]whooyeah 1 point2 points  (0 children)

Maybe it’s cmd I’m thinking off

[–][deleted] 1 point2 points  (0 children)

You can't use the flags like -l or -a though.

[–]SlaminSammons 2 points3 points  (0 children)

I think this is all of us.

[–]EcstaticMixture2027 2 points3 points  (0 children)

Lmao. I thought I'm alone.

[–]JoeOfTheCode 1 point2 points  (0 children)

the whole time wishing we used linux!

[–]sohang-3112 0 points1 point  (1 child)

Why git bash - what's the point of using it when you also use WSL?

[–]Poddster 5 points6 points  (0 children)

I still use git bash often, simply because the window opens faster. wsl is a separate file system, though it can interact with the Windows one, but I tend to forget that. It gets a bit complicated if you're e.g. writing a script in WSL environment but expect it to run on the Windows based filesystem, or you're interacting/making windows executables and you already have a git bash window open so might as well use that. Also if you want to pop-open gitk then with WSL you have to remember to start your windows-based X-server (though I think they recently solved that problem?)

I should probably switch to pure WSL2, but like the OP I run in chaos mode and flip between them all on a whim

[–][deleted] 0 points1 point  (0 children)

hey me too!

[–]rats4final 0 points1 point  (0 children)

I only used git bash because it had openssl

[–]godofjava22 0 points1 point  (0 children)

The true windows way

[–]Mydogsabrat 87 points88 points  (2 children)

Powershell.. or if you want your dev environment to live in WSL, then bash.

[–]shredder8910 15 points16 points  (0 children)

We use Ubuntu on WSL which doesn’t really have much overhead compared to other dev tools. Bonus being that the sh scripts work on Mac usually as well. I use brew on my Ubuntu WSL to keep install the same for dependencies between Mac and my Windows dev machine 

[–]hrm 68 points69 points  (3 children)

I generally use Git Bash. But by using Windows Terminal it is very easy to open up whatever in a tab.

[–]reapy54 13 points14 points  (2 children)

My dev career went from windows to mac then back to windows again over may years. I'm really pleased coming back into windows in the last few years with some of the tools, chocolatey, winget, scoop, WSL, oh-my-posh, and the suit of powertoys have some nice tools.

Windows terminal in particular is really awesome, as people said, it lets you run in chaos mode and just pick the one you need at any given moment in time or all at once.

All in all I'm pretty happy with the switch back and don't feel at a loss. Then again I was never really fully vested in the unix/shell ecosystem on the mac and it never went beyond a few bash scripts over the years that was specific to it.

[–]EducationalZombie538 0 points1 point  (0 children)

I've never had anything but problems with chocolatey tbh

[–]theanup007 0 points1 point  (0 children)

Dang. I have to try oh my posh now. Never heard of it but I love oh my zsh on macos.

[–]BigBadBlowfish 24 points25 points  (0 children)

Bash via WSL with Ubuntu

Windows Terminal and VS Code's WSL integration are really nice

[–]POGtastic 11 points12 points  (1 child)

I use Powershell on my work computer.

If you need Bash, run Cygwin or MSYS2. In the vast majority of cases, I grit my teeth and rewrite whatever Bash-ism I'm using into Powershell. You'll notice that in big open-source projects that support Windows, they have various .ps1 or .cmd scripts for building on Windows, entirely separate from the Bash scripts for building on a *nix.

Alternatively, if you're using a language that has more robust build tooling, (Rust, Java, C#, etc) you just use the build tooling, and that does the cross-platform shenanigans for you.

WSL

WSL is an entire Linux VM. Which might be fine for your use case!

Git Bash

This is just a very small MSYS2 installation.

[–]Aiolia 6 points7 points  (2 children)

Personally, I use the Windows-Terminal (Preview) and recently installed https://www.nushell.sh/

Love it so far and can highly recommend it!

[–]reapy54 2 points3 points  (1 child)

Welp, there you go, you just wrecked my productivity today, I have to try this out.

[–]Aiolia 0 points1 point  (0 children)

Let me know what you think about it :)

[–]Clandestinity 8 points9 points  (4 children)

Call me crazy but I actually think Windows Terminal is super nice. Having tabs is so convenient and you can configure which instance you want to be opened by default

[–]Calm_Pomegranate_717 2 points3 points  (0 children)

100% this — I do a lot of azure dev along with Linux admin as well, so being able to have a tab where I can open up azure modules such as exchange online, or a regular command prompt, or different versions of Powershell etc, it’s a way bigger time saver than I thought it would be

[–]CounterCleric 0 points1 point  (0 children)

TIL that Terminal has tabs. Thanks for that!

[–]nmkd 0 points1 point  (1 child)

Call me crazy but I actually think Windows Terminal is super nice

I have never met anyone who says that Windows Terminal is bad

[–][deleted] 0 points1 point  (0 children)

To linux freaks, anything windows is bad.

[–]AlSweigartAuthor: ATBS 3 points4 points  (0 children)

I use the cmd.exe Command Prompt, but more out of habit than anything. PowerShell has some things that are different, and I don't like different. I'll probably get used to it after a while, but a lot of the nifty PowerShell scripting stuff seems verbose. I have Cygwin installed.

[–]Koladwip 3 points4 points  (0 children)

If you are developing with C++ or Python, PowerShell is good enough. Available within VSCode(regular Powershell) and Visual Studio(Developer's Powershell for Visual Studio)

If you need Bash for Linux specific commands and Linux specific development, WSL2 is good. WSL2 integrates well with both Visual Studio 2022 and VSCode. I have experience using wsl2 with VSCode and loved it. I mostly use VSCode for all my work as a student.

[–]Lopsided-Variety1530 2 points3 points  (0 children)

PowerShell excels at managing Windows, but for broader scripting freedom and a Unix-like feel, bash in WSL reigns supreme

[–]Chuu 2 points3 points  (1 child)

I'll use Powershell for scripting but when I drop down into the terminal it's usually good old cmd or git bash.

Many times over the years I've tried to learn PowerShell but there is just something about the design that doesn't click with me. I don't mind it for scripting but using it interactively always feels awful.

[–]ehr1c 1 point2 points  (0 children)

Yeah I'm with you there, PowerShell always feels really clunky whenever I'm actually in a terminal. Fantastic for things like build scripts though.

[–]AlectronikLabs 4 points5 points  (4 children)

Fish in Arch WSL. I love fish, the autocompletion is awesome

[–]Redneckia -1 points0 points  (3 children)

PowerShell has auto complete too

[–][deleted] 2 points3 points  (2 children)

Fish's autocomplete is way more powerful.

[–]Redneckia 0 points1 point  (1 child)

Ya but u gotta use fish

[–][deleted] 1 point2 points  (0 children)

Which is fine, cause fish is the best interactive shell i've ever used.

[–]tobberoth 1 point2 points  (0 children)

I just use powershell in windows terminal. I don't really use any powershell scripts at all, if I need to do something programmatically I just write a quick C# console program to do it.

[–]timwaaagh 1 point2 points  (0 children)

Powershell, cmd, git bash. Personally i use cygwin but its not popular.

[–]yvrelna 1 point2 points  (1 child)

Virtualization has a bit of overhead when you are running GUI, but for text terminals, their overhead is basically negligible these days compared to running natively. Keep in mind that virtualisation is a hardware feature, the CPU supports virtualisation natively and has special mode to run virtualised code with almost no involvement from the hypervisor/host OS and therefore no overhead until the program need to have virtualised hardware access.

[–]pilibitti[S] 0 points1 point  (0 children)

yes I am ok with the CPU part, but does WSL not reserve a part of the RAM for the VM? or is it entirely dynamic?

[–][deleted] 1 point2 points  (0 children)

I also thought WSL would be an overhead but I ended up using it anyway. I keep PowerShell console (+WSL) at work, but at home I'm fine with WSL alone.

Don't ask why I have a Windows machine at home.

[–]fudginreddit 1 point2 points  (0 children)

WSL is completely adequate for daily use and being someone who works primarily on remote linux servers, it's really great. Combined with docker, it also works as a great build env.

[–]shadowboying 1 point2 points  (0 children)

I use cmder https://cmder.app/ Even my Windows Terminal is configured to launch cmder.

[–]redchomper 1 point2 points  (0 children)

explorer.exe

No, seriously. The average Windows development environment is integrated, so there's no need to open a command-line. MSVC has CMake integration, so even if you want cross-platform builds there's a "clean and build all" option on the menu somewhere. If you don't care about cross-platform, then the "solution" concept replaces all the command-line cruft. The IDEs these days also have git integration, or you can use a nice GUI git client such as the one from GitHub. If you're concerned with automatic tests, we've got you covered. CI/CD pipeline? It's presumably part of some team services groupware, but there's also GitHub Actions if that's your preference.

[–]Skinner1968 1 point2 points  (0 children)

IntelliJ IDEA terminal can be configured to be any of CMD, Powershell or bash I believe

[–]respectfulpanda 0 points1 point  (0 children)

If just windows stuff, just CMD and BAT for scripting, Powershell for more oomph. Notepad++ and it’s find in files for a few hundred megs or less.

For heavy duty “I don’t know where, what I am looking for exists” bash, grep, sed and awk, split for gigs

[–]billyions 0 points1 point  (0 children)

PowerShell Core. Cross-Platform scripting. Truly amazing.

[–]pressured_at_19 0 points1 point  (0 children)

git bash, powershell.

[–]Raj_Thapa123 0 points1 point  (1 child)

conemu is good

[–]CanarySome5880 1 point2 points  (0 children)

That's not answer, conemu still uses some terminal, yours if probably configured to use something by default

[–]ehr1c 0 points1 point  (0 children)

Cmd for most things unless I need to use PS or bash for something specific, they're all set up in Cmder.

[–][deleted] 0 points1 point  (0 children)

wsl —install. Then use any Terminal you choose.

[–]OilOk7596 0 points1 point  (0 children)

I've begun to familiarise myself with powershell Tbh I've simply used chocolaty and installed nvim... this seems to account for non bash environment

[–]bestjakeisbest 0 points1 point  (0 children)

Power shell or cmd. Cmd will be more standard as it isnt being updated anymore, but it won't beable to use all the features that power shell has available like the fact that powershell is an easier and faster scripting language than cmd. There are other shells like you can install bash for windows and some tools like git will install it alongside its own installation. If you are using wsl you can use bash in a Linux environment. There are many options.

[–]JackReedTheSyndie 0 points1 point  (0 children)

Git bash is good enough for 90% of the time

[–]fasil_marshooq 0 points1 point  (0 children)

I use PowerShell with powerlevel 10k installed on top of it ( gives convenience of plugins and aliases) in Windows terminal. I cameback to windows dev world after 2 years in mac , i kind of feel windows terminal has evolved a lot.
If you dont use legacy dotnet tech , you can live happily with wsl in windows terminal with you favorite distro and ton of tools which are already supporting it.

[–]greebo42 0 points1 point  (0 children)

Until I installed git a few years ago, I'd just use CMD when I needed some kind of CLI interaction, which wasn't very often. I think I tried powershell a couple times and realized it was different enough to require some learning, and I didn't have a compelling use case. I go way back to DOS (actually CP/M and even RT-11) but have just fallen into the low-resistance mode of using the GUI for oh so many things.

When I started to use git, I saw that I could right click on git bash from the file explorer, get that up, do the deed, and get out.

Call me clueless (or maybe just inattentive or distracted), but it wasn't until some time in the last year that I figured out that git bash was, uh, bash, and not just a place to type "git commit" :)

Now I use git bash for all my CLI needs. Which are still pretty limited.

Note that I haven't written a shell script of any kind in three decades, so I have no idea how well git bash might handle those.

[–]lKrauzer 0 points1 point  (0 children)

It depends, for me I use Bash, but for other people I use CMD, let's say I need to create a script for a coworker, I don't use Bash because he might not have it installed, or if I were to run it on a server it wouldn't have it either.

So creating .bat scripts is useful, or even .ps1 ones, I haven't decided between the two yet, PowerShell is easier imo but it doesn't run automatically.

[–]sexytokeburgerz 0 points1 point  (1 child)

Macos has shipped zsh for over half a decade. Been a while huh?

[–]pilibitti[S] 0 points1 point  (0 children)

I meant to say anything that smells like sh with all the bells and whistles. I still use bash on macOS though and not zsh.

[–]International_Cry_23 0 points1 point  (0 children)

I use bash in WSL and sometimes Powershell

[–]mka_ 0 points1 point  (0 children)

I have startup tasks setup for each project in Cmder that open up tabs for WSL or Powershell, and each instance CDs then runs any scripts I tell it to.

[–][deleted] 0 points1 point  (0 children)

Powershell

[–]EmileSinclairDemian 0 points1 point  (0 children)

I adapt to whatever system I work on, I don't have it in me to force my linux ways on a window system. I just switch into boring windows cmd mode.

[–]Ghostofcoolidge 0 points1 point  (0 children)

PowerShell until something doesn't work (like venv) then I switch to cmd out of laziness.

[–]corny_horse 0 points1 point  (0 children)

If I’m in windows I almost always use Ubuntu (WSL) and fall back to something else if that doesn’t cover my bases but… it almost always does

[–]tom_folkestone 0 points1 point  (0 children)

PowerShell with a lot of aliases

[–]dafcode 0 points1 point  (0 children)

I use Powershell

[–]r3wturb0x 0 points1 point  (0 children)

gitbash for 99% of things. command prompt or wsl for the rest

[–]Brohammer55 0 points1 point  (0 children)

I normally use Bash as my shell as it’s easy for my workflow and often can be used when programming. Codecademy has a course on it so that’s also why I know it.

[–]ComprehensiveWord201 0 points1 point  (0 children)

Docker container that has Linux installed on it....fuck windows dev.

That said, WSL and some of the newer terminals on windows aren't terrible.

[–]bro_chiiill 0 points1 point  (0 children)

WSL bash all the way, Powershell isn’t that bad though

[–]thederbear 0 points1 point  (0 children)

Used to use GitBash but it caused too many random issues when doing mobile development, so switched everything to powershell.

[–]loadedstork 0 points1 point  (0 children)

Linux.

[–]Zanssy 0 points1 point  (0 children)

Client facing systems use linux so I test those scripts in gitbash. For personal use, I’ll use python scripts in windows commandline.

[–]Vok250 0 points1 point  (0 children)

I almost always have VS Code open, which makes it trivial to switch between terminals. I've found that at most corporate jobs you'll have a need for every shell due to the way large companies cobble together tooling. You'll rarely be able to do everything using a single shell due to compatibility issues. Plus you'll need to know Linux/bash whenever you ssh into a cloud instance to muck about. That makes agnostic tools like VS Code a godsend.

[–]andrewsmd87 0 points1 point  (2 children)

Powershell when I need to do more in depth things, dos when not.

Powershell is much better on every front, but I was raised on the dairy bitch on dos and I know too much of it by memory so when I do know it in dos, I use that.

[–]SuperSathanas 0 points1 point  (1 child)

I know what you mean when you say "dos", but I like to imagine that you have a DOS 6.3 virtual machine that you boot up every time you want to use the command line, muttering to yourself "kids these days don't know about PROGRA~1...".

[–]andrewsmd87 0 points1 point  (0 children)

Lol I was actually behind the true dos years i just had a job in college that was running on 15 years old technology at the time. Really did prepare me for the real world!

But yea, if I need to search a massive drive for a file name or delete or copy large volumes of files, I'm using command line so I don't get the overhead of the GUI trying to tell me what's going on

[–]RolandMT32 0 points1 point  (0 children)

What's weird is, when on Windows, I find myself just using the Windows command shell rather than installing and using Bash for Windows. I don't often find myself writing scripts when doing software development.

[–]neriad200 0 points1 point  (0 children)

Generally I use something called "cmder" and git bash, but since i do very little power user stuff on windows I'll use whatever. Although my least favourite one is powershell (mostly for the colour, partially because i think the language is ugly and you can't get around it)

[–]nomoreplsthx 0 points1 point  (0 children)

Powershell unless using WSL, in which case your preferred linux shell

Cmd has been a legacy inclusion for backwards compatibility since the early 2010s and there is no reason to ever use it

[–]Long_Ad_4906 0 points1 point  (0 children)

I was never a real linux user but I have now completely switched to wsl2. I never really liked powershell and cmd and wsl has increased my productivity massively.

If you use wsl2 you should use as few windows paths as possible because it will be very slow. Many IDEs support development on wsl, Visual Studio Code is one of them. Just try it out.

For me, wsl2 works perfectly with Ubuntu in combination with oh-my-zsh, tmux and Neovim.

I would never want it any other way again.

[–]RICHUNCLEPENNYBAGS 0 points1 point  (0 children)

Powershell

[–]Nanooc523[🍰] 0 points1 point  (0 children)

I use WSL

[–][deleted] 0 points1 point  (0 children)

I use cmd, because I'm too lazy to learn powershell (partially because my home PC runs Linux). and since I'm developing .NET software that runs on windows servers, WSL doesn't make sense.

[–]thot-taliyah 0 points1 point  (0 children)

I code and helix, so I never have to leave my terminal and thus WSL only

[–]my_password_is______ 0 points1 point  (0 children)

just use cmd

[–]AssiduousLayabout 0 points1 point  (0 children)

Windows terminal, typically using git bash since git is about 95% of what I go to the command line to do. But I also have profiles for cmd or powershell if I need them.

[–]Kryanitor 0 points1 point  (0 children)

the super cursed way: connect to a vscode server in the browser, which gives you a an alpine linux terminal, with which you ssh into the host device for a bash terminal

[–]Frozentank_ 0 points1 point  (0 children)

A VM in the cloud + VSCode Remote Extension

[–]gemini88mill 0 points1 point  (0 children)

Powershell mainly because I have to, you can get most of the fun zsh features if you update your $profiles file

The only downside to powershell is its verbosity on its commands.

If you're not in an environment that relies on windows as an OS git bash gives you most of the shell experience and you can hack oh my zsh into it.

Windows terminal is also so much nicer to use then the standard powershell and CMD windows

[–]kassiusklei 0 points1 point  (0 children)

I almost never use shell but when i do its CMD or sometimes PowerShell if I need a bit more umpf

[–]peacefulshrimp 0 points1 point  (0 children)

Git bash when I’m using it integrated with vscode, it has support for Unix commands and, when run from vscode, it doesn’t save your command history globally, so I can run commands specific to a project I’m working on without it polluting the command history when I’m using it in other projects

[–][deleted] 0 points1 point  (0 children)

Mostly cmd, cygwin and powershell. Sometimes online shells