Live data from Hacker News

Developer and Power Users Tool List for Windows

hanselman.com

71–80 of 235 posts

Re: Developer and Power Users Tool List for Windows

#72
post #26
post #6

I wonder why the author recommend winget but not scoop. Scoop obviously has more community support and that's the most important part of a package manager (more packages, more frequent update, etc).

Any upsides to scoop compared to chocolatey?

It's a lot faster than chocolatey, choco gets painfully slow with many packages due to being serial. Scoop is considerably faster

Re: Developer and Power Users Tool List for Windows

#74

AutoHotKey finally fell off my list, to be replaced by... powershell. After about 8 years of utter disdain for the mistake that is powershell, I’m actually enjoying giving it a proper test drive. I can’t quite believe it myself but i chsh’d to pwsh on my mac and linux boxes too. Goodbye 30 lines of AHK just to capture and parse the output of a RunWait (in practice it was better to create a WSH com object and exec the…

How did you finally get into it? I was stoked about it 15 years ago when I first read about it, but using it never clicked with me. Every now and then I enthusiastically try to embrace it, just to eventually be annoyed by all the clumsiness, lack of speed, or about having to wade through layers of objects just to get to the information I need. It just does not have the feeling of a tool for shell users honed by shell…

It’s early days on my test drive. I don’t know how well it’ll fare for fairly common actions in bash like “here documents” or what the equiv of shopt extglob is in pwsh.

My usual cli usage is what i’d call “text manipulation” - slicing and dicing command output or converting csv-like data in some way or another.

My toolset is the usual suspects - bash, sed & awk but beyond a certain complexity i’ll switch to python.

The key thing for me is i can still use grep, sed, awk and python in pipelines as before but i’m attracted by the easy data access in pwsh.

The idea that Get-Process returns an object and i can just query each process’s WSS attribute for example is appealing right now (as opposed to explicitly manipulating text to suit, e.g. grep resident /proc/*/statm or ps -o rss or whatever approach)

Re: Developer and Power Users Tool List for Windows

#75
post #40

I'm surprised Dexpot[0] isn't listed. It's a really great virtual desktop management tool and has a number of things included that's not included with the Windows 10 default virtual desktop feature. Then there's VcXrv[1] to share your clipboard between WSL and Windows, it also lets you run Linux GUI tools in WSL. Essential IMO, if only for clipboard sharing. Sizer[2] is another great tool for quickly resizing and pos…

I see you use multiple monitors, does Sizer play well with them? I discarded it cause I thought it did not support multimonitor setups well. My main use case is setting up some complex layout (in multimonitor), and be able to save it, and restore it when needed.

> I see you use multiple monitors, does Sizer play well with them?

It supports them well.

It has a drop down box where you can define the monitor you want for a specific entry and then window positions will be relative to that monitor.

Alternatively you can also set a window's position to any X / Y coordinate. So if you had let's say 2x 2560x14440 monitors and you wanted to position a window to the 2nd monitor you can tell Sizer to move it to X coordinate 3050 and it would be +500 pixels into the 2nd monitor. You just need to enable the checkbox "allow move outside screen bounds". That could be useful I guess if you wanted a window to span more than 1 monitor and you have super thin bezels.

Re: Developer and Power Users Tool List for Windows

#76
post #8

Sort of a side note: Exceptional Mac programs are often showcased and awarded. Either by Apple or others in the Mac “community”. Is there example from the Windows side? Programs that highlight the very best the Windows platform can deliver?

I think that there are simply too many to spotlight.

I think that Microsoft just don't care.

Re: Developer and Power Users Tool List for Windows

#77

Earlier quoted context omitted.

> I wonder why the author recommend winget but not scoop. Scott Hanselman works for Microsoft and is a prominent advocate for the .NET/Microsoft ecosystem so his recommendations are likely to skew towards native MS tools in the first instance. Nothing wrong with that as long as you consume his material through that lens! That said, I'm quite surprised I hadn't heard of Scoop[0]. Looks interesting... [0] https://scoop…

Best thing about scoop is that it doesn't need admin privileges. Everything is installed as portables in user directory

Everything is installed as portables in user directory

Is that a good thing?

Re: Developer and Power Users Tool List for Windows

#78
post #2

I'd add Directory Opus[0] to that list. It's an incredibly customizable and scriptable file explorer that allows you to fit it exactly to your workflow. It's like IntelliJ of file explorers. - Tabbed interface with multiple panes - Every function can be assigned a shortcut - Every button can be scripted - Defaults can be overwritten - Dynamic layouts based on folder contents, path or determined by a script - Custom f…

It's probably using the Active Scripting interfaces for scripts. I seem to remember that Python supports those interfaces so that might be an option.

Re: Developer and Power Users Tool List for Windows

#80

Earlier quoted context omitted.

Best thing about scoop is that it doesn't need admin privileges. Everything is installed as portables in user directory

Everything is installed as portables in user directory Is that a good thing?

In corporate environments it is, since you don’t have to get permission from the IT police to install VSCode or Firefox or grep.

(Of course, you should. But sometimes it’s not an option.)

Post reply on HN