What Are You Doing Right Now

scottalanmiller

@hobbit666 I have one of those in my garage.

hobbit666

@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

EddieJennings

@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 £600

I never used the X-Series, but whatever the series was right before it seemed like it was solid.

Obsolesce

@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.

scottalanmiller

@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.

jmoore

@scottalanmiller I need some warm choco chip cookies and a big glass of cold milk

scottalanmiller

@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.

valentina

@jmoore same here! Bring them over @scottalanmiller

Obsolesce

@scottalanmiller said in What Are You Doing Right Now:

What "proper" deployment of PowerShell is needed to work it work competitively?

Proper scripting, using efficient and/or correct cmdlets, not piping in needless circles...

I really depends on what you are trying to do. It's not always technically apples to apples. You may run one line in BASH for some purpose, and then compare it to directly to how it's done on PowerShell, when perhaps you wouldn't do it in the first place, or in practice not in the same way.

scottalanmiller

@Obsolesce said in What Are You Doing Right Now:

Proper scripting, using efficient and/or correct cmdlets, not piping in needless circles...

I'm talking about running a single command. Just like asking the uptime. No scripts, just the time it takes for the shell to set up, execute and be done. We do that 98% of the time that we run any shell and PS doesn't stand up to any other shell. Running stuff locally takes longer than running things remotely on any other shell.

WrCombs

It's roughly 27 degrees Celsius right now
beautiful day out side. I'm gonna go spend the day with my son playing out and about now.

Obsolesce

@scottalanmiller said in What Are You Doing Right Now:

@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.

It really just depends on your use case. Linux and Windows are used differently.

Obsolesce

@scottalanmiller said in What Are You Doing Right Now:

@Obsolesce said in What Are You Doing Right Now:

Proper scripting, using efficient and/or correct cmdlets, not piping in needless circles...

I'm talking about running a single command. Just like asking the uptime. No scripts, just the time it takes for the shell to set up, execute and be done. We do that 98% of the time that we run any shell and PS doesn't stand up to any other shell. Running stuff locally takes longer than running things remotely on any other shell.

Like what? I did a Get-Uptime cmd and it was instant. If it was any faster, I wouldn't notice.

You have an example of something someone would typically do on both Linux and Windows equally where it's much faster in BASH?

dbeato

@EddieJennings said in What Are You Doing Right Now:

@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 £600

I never used the X-Series, but whatever the series was right before it seemed like it was solid.

It was PowerConnect which were solid and still some running for me.

wrx7m

@dbeato said in What Are You Doing Right Now:

@EddieJennings said in What Are You Doing Right Now:

@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 £600

I never used the X-Series, but whatever the series was right before it seemed like it was solid.

It was PowerConnect which were solid and still some running for me.

Yeah, I still have 2 running. There is a location that some cables were run long before my time that has a powerconnect 5548P and it is uplinked to another one in the server room. I have 5 drops left to replace, before I can get rid of both.

Edit- My main switches are Extreme XG450 G2 Summit switches, configured in a stack.

scottalanmiller

@Obsolesce said in What Are You Doing Right Now:

Like what? I did a Get-Uptime cmd and it was instant. If it was any faster, I wouldn't notice.

It's not instant. Are you sure you didn't spend time getting PS up and running first, THEN time only the command after all the time was already spent?