What Are You Doing Right Now
-
@EddieJennings said in What Are You Doing Right Now:
That's promising then. Maybe in 5 years we'll have version 6 on everything where I work . It is telling that it took 6 versions to get that functionality.
And how many decades to get PowerShell in the first place
-
@EddieJennings said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@black3dynamite yeah, PowerShell is still stuck in like 1982 here.
No, I think all of you are stuck in 1982 while PowerShell has moved on...
Unless there's a bleeding-edge version of Powershell out now that has that cmdlet, it doesn't seem to be native for 5.1.
I know there's a module out there that does what your picture shows, but it would be nice if that was just baked-in.
This is one of my two major complaints with PowerShell. Modules that you just aren't told you need to load in so many guides, which Microsoft officially published many. They are working on a feature to automatically load a needed module on demand, like any decent management tool should.
My other complaint is output. I never quite know if a given output is going to be text, csv, or some other formatting. From a long-time UNIX user, this is frustrating. I know I just need to tell it to be sure, but that's just slowing me down.
-
@scottalanmiller said in What Are You Doing Right Now:
@EddieJennings said in What Are You Doing Right Now:
That's promising then. Maybe in 5 years we'll have version 6 on everything where I work . It is telling that it took 6 versions to get that functionality.
And how many decades to get PowerShell in the first place
Well, it is called "Windows".
-
@travisdh1 said in What Are You Doing Right Now:
This is one of my two major complaints with PowerShell. Modules that you just aren't told you need to load in so many guides, which Microsoft officially published many. They are working on a feature to automatically load a needed module on demand, like any decent management tool should.
Don't forget ones that break. We have scripts that have worked for years, but you update Windows and suddenly they don't run any longer.
-
@travisdh1 said in What Are You Doing Right Now:
My other complaint is output. I never quite know if a given output is going to be text, csv, or some other formatting.
True. It's very haphazard and amateur. Seems to lack a clear vision, more like a hodge-podge of different teams, visions, ideas. just thrown together and no one trying to make it all work.
-
@travisdh1 said in What Are You Doing Right Now:
@EddieJennings said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@black3dynamite yeah, PowerShell is still stuck in like 1982 here.
No, I think all of you are stuck in 1982 while PowerShell has moved on...
Unless there's a bleeding-edge version of Powershell out now that has that cmdlet, it doesn't seem to be native for 5.1.
I know there's a module out there that does what your picture shows, but it would be nice if that was just baked-in.
This is one of my two major complaints with PowerShell. Modules that you just aren't told you need to load in so many guides, which Microsoft officially published many. They are working on a feature to automatically load a needed module on demand, like any decent management tool should.
My other complaint is output. I never quite know if a given output is going to be text, csv, or some other formatting. From a long-time UNIX user, this is frustrating. I know I just need to tell it to be sure, but that's just slowing me down.
When the output is an object (which is true I think almost all the time), I find the object useful. I haven't had the experience in the text-only output world to know what I'm missing there.
-
@EddieJennings said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
@EddieJennings said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@black3dynamite yeah, PowerShell is still stuck in like 1982 here.
No, I think all of you are stuck in 1982 while PowerShell has moved on...
Unless there's a bleeding-edge version of Powershell out now that has that cmdlet, it doesn't seem to be native for 5.1.
I know there's a module out there that does what your picture shows, but it would be nice if that was just baked-in.
No, nothing new or fancy... just plain old PS6:
That's promising then. Maybe in 5 years we'll have version 6 on everything where I work
. It is telling that it took 6 versions to get that functionality.PowerShell 7 is on its way with some sweet (and much needed) functionality.
-
@scottalanmiller said in What Are You Doing Right Now:
@travisdh1 said in What Are You Doing Right Now:
My other complaint is output. I never quite know if a given output is going to be text, csv, or some other formatting.
True. It's very haphazard and amateur. Seems to lack a clear vision, more like a hodge-podge of different teams, visions, ideas. just thrown together and no one trying to make it all work.
It's always objects unless you purposely make it old school text, like when you mix in cmd. Exe commands.
-
Dealing with this shitty Chinese software that "interacts" with Amazon. It doesn't work because it won't update from the server (throwing 403 error). Everything is in Chinese and support is only available during Chinese day time and in Chinese only. Their own support can't fix it and now this marketing person wants me to uninstall and reinstall it.
You can't even run it without running as admin, so I had to create a Microsoft application compatibility exception just to get it to run in a regular user's account. Also, you have to switch the entire OS to Chinese to get it to accept the serial number.
I don't trust this thing so much that I have a non-domain joined system that is connected to our guest wifi network.
Waste of time/money.
-
@EddieJennings said in What Are You Doing Right Now:
@travisdh1 said in What Are You Doing Right Now:
@EddieJennings said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@black3dynamite yeah, PowerShell is still stuck in like 1982 here.
No, I think all of you are stuck in 1982 while PowerShell has moved on...
Unless there's a bleeding-edge version of Powershell out now that has that cmdlet, it doesn't seem to be native for 5.1.
I know there's a module out there that does what your picture shows, but it would be nice if that was just baked-in.
This is one of my two major complaints with PowerShell. Modules that you just aren't told you need to load in so many guides, which Microsoft officially published many. They are working on a feature to automatically load a needed module on demand, like any decent management tool should.
My other complaint is output. I never quite know if a given output is going to be text, csv, or some other formatting. From a long-time UNIX user, this is frustrating. I know I just need to tell it to be sure, but that's just slowing me down.
When the output is an object (which is true I think almost all the time), I find the object useful. I haven't had the experience in the text-only output world to know what I'm missing there.
Ease of use, obvious use cases. Text is SO fast and SO easy. Object is more powerful, and I appreciate the reasons that they thought that OOP was the future (because they listened to every two bit 1990s Java professor) but in the real world of systems administration, it makes little to no sense and just causes endless problems.
-
@Obsolesce said in What Are You Doing Right Now:
@EddieJennings said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
@EddieJennings said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@black3dynamite yeah, PowerShell is still stuck in like 1982 here.
No, I think all of you are stuck in 1982 while PowerShell has moved on...
Unless there's a bleeding-edge version of Powershell out now that has that cmdlet, it doesn't seem to be native for 5.1.
I know there's a module out there that does what your picture shows, but it would be nice if that was just baked-in.
No, nothing new or fancy... just plain old PS6:
That's promising then. Maybe in 5 years we'll have version 6 on everything where I work
. It is telling that it took 6 versions to get that functionality.PowerShell 7 is on its way with some sweet (and much needed) functionality.
that's cool
-
@dbeato said in What Are You Doing Right Now:
The Dell X Series is a little bit old by now. At least they don't sell it anymore in Premier
Still showing when you navigate the website.
https://www.dell.com/en-uk/work/shop/networking/sc/networking-products/switches -
@hobbit666 said in What Are You Doing Right Now:
@dbeato said in What Are You Doing Right Now:
The Dell X Series is a little bit old by now. At least they don't sell it anymore in Premier
Still showing when you navigate the website.
https://www.dell.com/en-uk/work/shop/networking/sc/networking-products/switchesYeah, the annoying part is
-
@hobbit666 I have one of those in my garage.
-
@dbeato said in What Are You Doing Right Now:
Yeah, the annoying part is
Luckily they show on our supplier website
The Dell X1052p £600 -
@hobbit666 said in What Are You Doing Right Now:
@dbeato said in What Are You Doing Right Now:
Yeah, the annoying part is
Luckily they show on our supplier website
The Dell X1052p £600I never used the X-Series, but whatever the series was right before it seemed like it was solid.
-
@scottalanmiller said in What Are You Doing Right Now:
@EddieJennings said in What Are You Doing Right Now:
@travisdh1 said in What Are You Doing Right Now:
@EddieJennings said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@black3dynamite yeah, PowerShell is still stuck in like 1982 here.
No, I think all of you are stuck in 1982 while PowerShell has moved on...
Unless there's a bleeding-edge version of Powershell out now that has that cmdlet, it doesn't seem to be native for 5.1.
I know there's a module out there that does what your picture shows, but it would be nice if that was just baked-in.
This is one of my two major complaints with PowerShell. Modules that you just aren't told you need to load in so many guides, which Microsoft officially published many. They are working on a feature to automatically load a needed module on demand, like any decent management tool should.
My other complaint is output. I never quite know if a given output is going to be text, csv, or some other formatting. From a long-time UNIX user, this is frustrating. I know I just need to tell it to be sure, but that's just slowing me down.
When the output is an object (which is true I think almost all the time), I find the object useful. I haven't had the experience in the text-only output world to know what I'm missing there.
Ease of use, obvious use cases. Text is SO fast and SO easy. Object is more powerful, and I appreciate the reasons that they thought that OOP was the future (because they listened to every two bit 1990s Java professor) but in the real world of systems administration, it makes little to no sense and just causes endless problems.
I feel they both have their place in their own world. I would rather manage MS / Windows as objects than text based output. For me it would be a lot less convenient to manipulate the data for Windows from BASH cli. You do very different things in Linux than you do in Windows. They are built so differently and in this case, I think PS is a better tool. I feel the same in a mixed environment of Windows/Linux. Yes BASH for managing Linux, but PowerShell for managing anything MS/Windows, and PowerShell (Core) for managing Windows from Linux.
I don't notice a speed difference when done properly.
-
@Obsolesce said in What Are You Doing Right Now:
PowerShell (Core) for managing Windows from Linux.
Having tried it both ways, using Bash on Linux to reduce the overhead of PS is a big benefit to adding it into the mix.
PS has some nice stuff, but it's like "Windows seems hard because of PS, but PS seems to deal with it well." But at the end of the day, most of Windows issues seem to be intentionally being extra hard, then making extra hard solutions to justify it. How much of Windows needing the overhead of PowerShell is caused by Windows having PowerShell and wanting it to seem reasonable to have designed it like they did? So a circular problem of PowerShell is hard and we need to justify it by making Windows hard, Windows is now harder and we need PowerShell, and so on.
-
@scottalanmiller I need some warm choco chip cookies and a big glass of cold milk
-
@Obsolesce said in What Are You Doing Right Now:
I don't notice a speed difference when done properly.
People say this, but consistently PowerShell can't respond that fast. It's just slow. No matter how you cut it. Just launch a command remotely and time it. You say "properly", but if PowerShell doesn't work on Windows as Microsoft deploys it, could their being a stronger statement about how badly it is designed?
What "proper" deployment of PowerShell is needed to work it work competitively?
BASH works well, right out of the box, on every OS. No need for "proper" setups to make it function in a way that the creators weren't able to do.
