Not trying to play PAM favorites or anything, but every time I interface with CyberArk or BeyondTrust it just makes me appreciate Devolutions more. On a related note it is truly amazing just how convoluted and difficult CyberArk can make the simplest tasks.
Posts by Griff Barker
This seems like the more natural course to me as well
Seems pretty darn usable to me! I spend a good chunk of my day in PowerShell and have written many, many automations, integrations, etc. in PS. Curious to know what makes it unusable?
The CLI authentication experience across Microsoft Graph and other various MS cloud services has definitely sucked for a little bit, and they have been working on that. In the meantime, there are neat helpers out there like DLLPickle that help work around some of those sucky issues.
It seems to me these are potentially issues with the modules themselves that you're working with, and not so much issues with PowerShell itself.
Which is still frustrating to be sure! I just don't think specific modules having issues makes the entire language or shell "suck".
Curious to know what in particular sucks so bad, if you're willing to share. There are a great number of things that "suck" about languages and shells when you're not familiar with them. And then of course there are things that ultimately do just suck.
I'm so thankful for password managers, SSO, SSH keys, and certificate authentication. I literally could not spend all day finding passwords and re-logging!
I also feel like 4k is a bit much. 2x 32 inch monitors at 1440p has been what I've most enjoyed personally. It's what I have not and I don't foresee myself changing it up any time soon.
Though one of them randomly goes back to 1080p intermittently on my Arch install, gotta figure that out.
Very possibly their timing of entry into the market for sure. Now there are so many options, even some with less friction to get started.
Every day we stray further...into me having another tasty problem π
This is the kind of quality social media content I can get behind.
100% my feeling as well! I have never really understood the allure or why it has driven success for them.
Go for both! There's absolutely room for both for sure. I use PowerShell much more often personally, due to my circumstance. But I still use bash with regularity.
Agreed!
PowerShell the shell
β
PowerShell the language
...which is a source of confusion for a lot of folks for sure, including myself years ago!
Those executables using /flags would work just fine in Command Prompt, whereas PowerShell cmdlets would not.
Also, PowerShell uses -Parameters rather than /flags. Because of this comment I assume you're trying to call a Windows-specific executable (maybe a legacy one like `findstr.exe` or maybe an actual application like `cleanmgr.exe` with the forward slash style arguments.
PowerShell is cross platform and can invoke executables that are not inherently PowerShell themselves so it comes down to understanding the operating system you're on and what its requirements are for its executables.
If you're calling Windows executables from PowerShell (e.g. `findstr`) then you may still need to use the Windows-style backslash.
Or vice versa with native Linux binaries (e.g. `grep`) where you'll need the forward slash.
Is not the direction of the slashes dictated by the OS, rather than the command line itself? You should be able to largely use either slash in PowerShell as long as you're consistent about it.
8bitdo 64 controller
iβm enamored with this thing. thereβs something very beautiful and also very perverse an N64 controller thatβs Normal
π€’
The count of people who do not read documentation is far, far too high.
Venn diagram with circles so closely overlapping that they are functionally the same, showing that people who don't understand a specific thing are basically the same people who crash out about a specific thing.
Pick your topic. If the shoe fits!
It's the same circle.
My dogs have entirely more energy than this time of night warrants.
Today is not the day I need a power outage! I have things to do!
gdscript function with the incorrectly spelled function name as an alias for the correctly spelled function. #godot #indiedev
Backwards compatability
Tri-color Corgis are the "orange cats" of dogs and you won't change my mind.
Saturdays are the best because the fish and chips truck is in town π
Wrote an Azure function in PowerShell and set it up as a custom authentication extension/claims provider to get and inject some Entra ID user attributes into SAML assertions during single sign-on.
PS + JSON = π so there's some reasonable defense for just camelCasing everything. That said, I do think with cmdlets being PascalCase, properties would look best PascalCase as well for consistency. Granted, I'm talking only about scripting. At the commandline its all lowercase lol.