discusseded

Pfft, your depth of insight could be scratched off with a fingernail.

It's every person and institution that shielded the voters from the reality of Biden's mental decline who should be blamed. These enablers ought to be charged with crimes against the US for election interference.

We could have had a real primary and let voters decide, now we're stuck with a convention nomination process that's out of our hands.

Fuck the DNC.

This blog does a fairly straight-forward job on explaining the basics. For me, I learn best in an interactive 1:1 or well-constructed video, so ChatGPT was priceless. I could ask it stupid questions all day long, and after throwing some different ideas around I started to see the essential parts and just let my prior knowledge of PS, .NET, and C# WPF take it from there.

At the end of the day, all that really matters is using the PresentationFramework assembly and creating a window:

• Add-Type -AssemblyName PresentationFramework
• Either use Visual Studio > WPF Project and make the UI you want. Take the XAML file and use PowerShell to get the raw content:
  • $Xaml = Get-Content -Path MainWindow.xaml -Raw
  • $SanitizedXaml = $Xaml -replace "bad syntax e.g. Foreground={x:Null}" "Foreground="Transparent" # Certain XAML syntax is incompatible with PS XML
  • [xml]$XmlReader = [System.Xml.XmlNodeReader]::new($SanitizedXaml)
  • $Window = [Windows.Markup.XamlReader]::Load($XmlReader)
• Or, use .NET-style syntax in PS directly:
  • $Window = [System.Windows.Window]::new()
• Then show the window:
  • $Window.ShowDialog() | Out-Null

I appreciate the feedback. For the Linux side it's for personal projects and learning opportunities so starting with something familiar and growing from there is my goal.

I dabble in C and C++ so cli isn't out of the question for me. But .NET is my comfort zone, and I like the rapid tooling that PS offers.

I have multiple reasons to dig into Python so really I just need to get on with it.

Python is always something I intend to learn but never get around to. Does it natively handle GUI for process tooling or does it require a third party? What makes PowerShell so useful to me is the native ability to create visual applications without the need to compile. I can create tools for my company that launches right out of ConfigMgr Software Center and other technicians can contribute without needing a programming background.

At home I want to mess around with tooling for home services without having to resort to web development.

By far it's the object pipeline. Having structured data makes it easy to automate workflows in a predictable way. With bash everything is a string, so everything has to be parsed. It's tedious.

It took about a year of steady use before I came to enjoy the syntax. It shines in a production environment with other cooks in the kitchen. I never got into the C style, I like my code human readable at a glance. It's fine if everyone's a sage but we have a team with a mixture of skill levels and for me PowerShell gets it right.

I did install it on one of my machines but haven't dug in yet. I'm curious to see how much of my workflow will translate to Linux, yet at the same time I want to make sure I'm actually learning Linux and not using PS as a crutch.

Thanks for the reference. I'm looking at it and I think you're right.

After learning PowerShell and then moving to Linux and having to learn bash...I don't get this sentiment. PS is the shit. I can make full GUI applications and automate all kinds of workflows. Their use of objects makes it so easy to extract data and utilize it. Bash feels so much more primitive and clumsy by comparison. What am I missing here?

LinX

I loooove my openSUSE desktop. 11 was the last straw. No amount of AI is going to bring me back.

I HATE advertisements, and I paid for Pro but it seemed like they didn't care. They want to milk me for everything I'm worth.

Good thing we have options. Linux has gotten so good, it's better than Windows 11 while letting me decide how to use the OS. Big learning curve, but it's smooth sailing when you get past it.

Our ticketing system has "untrained user" and "works as designed, not as expected" as options. Can't fix the problem if you don't know its nature.