go-callvis VS cmder

Dependency plugins and tools are automatically installed after executing the command: protoc-gen-go, protoc-gen-go-grpc, protoc-gen-validate, protoc-gen-gotag, protoc-gen-go-gin, protoc-gen-go-rpc-tmpl, protoc-gen-openapiv2, protoc-gen-doc, golangci-lint, swag, go-callvis.

[Windows only]

I recently discovered Cmder:

https://cmder.app/

It's a portable console emulator and gives you the ability to "place your own executable files into the bin folder to be injected into your PATH" when it's run.

So far I've added:

jq

Assuming you already have Visual Studio Code installed, the first thing you'll want to do is Download Cmder. Extract the files to C:\cmder, or wherever you like.

I use cmder, it's great https://cmder.app/

The multiple supported shells remind me a little bit of the Windows cmder app, which I recall being pretty decent: https://cmder.app/

But the cross platform aspect is really nice, even if in my experience using different terminal apps per platform hasn't been too big of an issue.

Maybe except for MobaXTerm feeling better than most Linux tabbed/split terminal offerings due to its usability and support for sending input to multiple remote sessions at the same time, SSH integration etc.: https://mobaxterm.mobatek.net/ (something like Remmina is on par with mRemoteNG, so nice but not quite there)

I've since found that dev workflows in Windows work pretty damn good now, actually. I hate PowerShell so I still don't use it, but I now use Nushell, Cmder, and Git-Bash as my shells within the native Windows terminal emulator and it's actually pretty damn good and very close to the Unix experience. I actually like the native Windows terminal more than Kitty and would switch to it on my Ubuntu machine and my work MacBook if it were available on these systems.

If you haven't tried Cmder yet you definitely should.

The Second was to directly avoid powershell & cmd altogether .. i also used cmder which gave me a feeling of Linux on windows