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.
-
@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.
-
@jmoore same here! Bring them over @scottalanmiller
-
@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.
-
@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.
-
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. -
@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.
-
@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-Uptimecmd 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?
-
@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 £600I 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.
-
@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 £600I 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.
-
@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?
-
@Obsolesce said in What Are You Doing Right Now:
You have an example of something someone would typically do on both Linux and Windows equally where it's much faster in BASH?
I know of not task that doesn't work this way. But uptime is a perfect example.
-
BTW... "Get-Uptime" isn't found on Windows 10 1809 fresh install.
-
Speed of uptime on Linux. This is bash calling SSH calling bash...
One second. Most of that time is used to set up SSH, nothing to do with Bash.
-
@scottalanmiller said in What Are You Doing Right Now:
BTW... "Get-Uptime" isn't found on Windows 10 1809 fresh install.
IT is a script that needs to be downloaded
https://gist.githubusercontent.com/morisy/8aa34f4ba0beaf8eef1b9224c616e041/raw/4644b875e9e5393f25b0fe79e24129eec5654f7e/Get-Uptime.ps1 -
@scottalanmiller said in What Are You Doing Right Now:
@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?
No, I did the exact same thing I'd have done on a Linux GUI....
- Click on PowerShell on the task bar to open it up. (keybind would work too)
- Typed in
Get-Uptime -Since, hit enter. - Maybe I saved a little time typing with PowerShell because of tab-completion. I only typed
get-up <tab> -<tab>thenenter.
-
@Obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@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?
No, I did the exact same thing I'd have done on a Linux GUI....
- Click on PowerShell on the task bar to open it up. (keybind would work too)
- Typed in
Get-Uptime -Since, hit enter. - Maybe I saved a little time typing with PowerShell because of tab-completion. I only typed
get-up <tab> -<tab>thenenter.
Weird,
-
@dbeato 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:
@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?
No, I did the exact same thing I'd have done on a Linux GUI....
- Click on PowerShell on the task bar to open it up. (keybind would work too)
- Typed in
Get-Uptime -Since, hit enter. - Maybe I saved a little time typing with PowerShell because of tab-completion. I only typed
get-up <tab> -<tab>thenenter.
Weird,
@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:
-
@scottalanmiller said in What Are You Doing Right Now:
Speed of uptime on Linux. This is bash calling SSH calling bash...
One second. Most of that time is used to set up SSH, nothing to do with Bash.
I can do that exact same thing in PowerShell on Win10 now that SSH works by default
word for word... letter for letter.... in PowerShell.
