Does that make it better?

Nah, it’s 53 billion for each

Thank you for providing the good reasons for it, it makes much more sense now

The accounts started out optional with benefits to entice

They’re now mandatory for Home and hard to bypass

How long before they extend this to Pro and Enterprise? To Server? To Active Directory itself?

They’re not done yet, not by a long shot.

Tesla isn’t a car… It’s an EXPERIENCE!!!

(/s just in case it isn’t obvious enough)

It’s worse than that: it requires the old school lead acid 12v battery to be charged, so even if the car’s battery is full, it doesn’t matter if that old car battery has failed

That’s not unique to Tesla EVs, but it being required to open the doors may be (the 12v lead acid runs the general vehicle electronics rather than down converting the 400v or 800v main battery… I don’t understand that decision, but I’m no electronics expert so there may be really good reasons for it…)

Last couple cars I’ve had that’s been a setting you can change… I set mine to lock when the car moves at more than a few mph, the other options seemed like too high a chance to cause an accidental lockout to me

I’m legit still pissed off about that one

Pretty sure it’s just about the shared name

Just like Jan 6

I mean, what isn’t short for Elizabeth?

Since my other systems were unaffected, I’m pretty sure it’s something on my PC, possibly an update for the Wi-Fi drivers introduced a bug that affects the 5.8 channels

It’s been stable since switching so it’s more academic at this point, I have no burning need to be connected to the 5ghz channels

That just makes her approve even more

It seems to be an issue with using a 5.8 gigahertz WiFi endpoint, which has worked fine up until a couple days ago when it started dropping packets going outside my local network: I could watch a continuous ping start failing for a couple minutes while using Synergy to control my laptop that was connected to my work VPN without issue, so it only seemed to be an issue routing outside my network, which is really weird. Switching to the 2.4 gigahertz channels seems to have fixed it entirely.

What I need to do is look up the JournalD commands to be able to read the logs correctly and find what I’m after… Might also spin up a VM to see if that goes out at the same time, would be interesting if the VM can still work while the host is dropping packets…

Not sure what’s extravagant about it… Fully object oriented pipeline in a scripting language built on and with access to the .NET type class system is insanely powerful. Having to manipulate and parse string output to extract data from command results in other shells just feels very cumbersome and antiquated, and relies on the text output to remain consistent to not break

PowerShell, it doesn’t matter if more or less data is returned, as long as the properties you’re using stay the same your script will not break

Filtering is super easy

The Verb-Noun cmdlet naming convention gets a lot of (undeserved) hate, but it makes command discovery way easier. Especially when you learn that there’s a list of approved verbs with defined meanings, and cmdlets with matching nouns tend to work together.

It actually follows the Unix philosophy of each cmdlet doing one thing (though sometimes a cmdlet winds up getting overloaded, but more often than not that’s a community or privately written cmdlet)

It’s easily powerful enough to write programs with (and I have)

And it works well with C#, and if you know some C#, PowerShell’s eccentricities start to make way more sense

Also, I mainly manage Windows servers for work running in an AD domain, so it’s absolutely the language of choice for that, but I’ve been using it for probably close to 14 years now and I can basically write it as easily as English at this point

Yeah, PowerShell does do things that don’t exactly make sense without having some understanding of the underlying dotnet and what the components actually do

It crossed that border a long, long time ago

I’ll probably give it a spin anyway, might be I find some benefit and it looks like an interesting project. Being Rust based instead of C# .NET based could theoretically make it a lot faster (though I’ve not really had an issue of speed in PowerShell)

V1 never actually shipped with any version of Windows

Windows 7 shipped with V2, 8 with V3, 8.1 with v4, and 10 with v5 and later 5.1.

5.1 is the latest (and last) version of Windows PowerShell.

All versions after that are just PowerShell (or PowerShell Core for version 6)

Not sure why they don’t bundle it by default, but starting at v7.2 it can be updated by Windows update

Just looking at it briefly it looks a lot like PowerShell, any reason to use it over PowerShell?