What Are You Doing Right Now
-
@scottalanmiller said in What Are You Doing Right Now:
That's not true. You can make open source on MS just as easily as on Linux (other than Windows being harder to develope for because the tools just aren't as good and the OS not as good.)
That was not at all or even close to my point or what I said / meant.
-
@scottalanmiller I think this is likely worth it's own topic what I'm going to ask.
But how and why does BASH work "universally" to call things like "top", "uptime", "df" where as with Powershell none of this seems to exist without going out and installing individual scripts into every system?
-
@DustinB3403 said in What Are You Doing Right Now:
@scottalanmiller I think this is likely worth it's own topic what I'm going to ask.
But how and why does BASH work "universally" to call things like "top", "uptime", "df" where as with Powershell none of this seems to exist without going out and installing individual scripts into every system?
Because they aren't apples to apples.
-
@scottalanmiller said in What Are You Doing Right Now:
The issue is MS not including things by default that are considered basic functionality anywhere else.
And you actually just answered it.
-
@DustinB3403 said in What Are You Doing Right Now:
The issue is MS not including things by default that are considered basic functionality anywhere else.
oh, but it's there! You can get uptime in PowerShell 5.1, but it's more typing.
-
@Obsolesce said in What Are You Doing Right Now:
Because they aren't apples to apples.
That isn't the answer though, @scottalanmiller stated it moments before I clicked submit. PowerShell and Windows in particular just don't include "basic tools" OOB.
You want them, go get it yourself.
-
@Obsolesce said in What Are You Doing Right Now:
oh, but it's there! You can get uptime in PowerShell 5.1, but it's more typing.
That's more cumbersome. Who the hell wants to type more?
-
@DustinB3403 said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
oh, but it's there! You can get uptime in PowerShell 5.1, but it's more typing.
That's more cumbersome. Who the hell wants to type more?
Nobody, that's why scripting and automation exist! Which PowerShell does nicely.
-
@Obsolesce said in What Are You Doing Right Now:
@DustinB3403 said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
oh, but it's there! You can get uptime in PowerShell 5.1, but it's more typing.
That's more cumbersome. Who the hell wants to type more?
Nobody, that's why scripting and automation exist! Which PowerShell does nicely.
But in BASH I can script too. But I don't need to write a script to pull the UPTIME of the system because it's included with literally every BASH using system besides Windows.
The fact that I can script, doesn't mean I should have too.
Every time I actually use Powershell, I'm writing a script (usually because I don't want to run the process manually over and over).
-
I'm headed home for the day.
Night all.
-
@DustinB3403 said in What Are You Doing Right Now:
I'm headed home for the day.
Night all.
Night, we just hired a new guy, too!
-
@Obsolesce said in What Are You Doing Right Now:
@DustinB3403 said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
oh, but it's there! You can get uptime in PowerShell 5.1, but it's more typing.
That's more cumbersome. Who the hell wants to type more?
Nobody, that's why scripting and automation exist! Which PowerShell does nicely.
It does, no question there. If you are making really large scripts, it's a great tool. Especially if they are complex.
And for large things, it is definitely better than Bash. But Linux doesn't use Bash for things that approach the "programming" line rather than the system admin line, that's not what a Shell is for. Technically Python, Ruby, Perl, and others are all shells, too, and are more robust and really good for enormous projects.
-
@DustinB3403 said in What Are You Doing Right Now:
Every time I actually use Powershell, I'm writing a script (usually because I don't want to run the process manually over and over).
I probably would say that about my use of Bash, too. I do tiny scripting almost every time that I type. It's just that in bash doing so is so easy, I forget that I'm doing it.
-
@Obsolesce said in What Are You Doing Right Now:
@DustinB3403 said in What Are You Doing Right Now:
The issue is MS not including things by default that are considered basic functionality anywhere else.
oh, but it's there! You can get uptime in PowerShell 5.1, but it's more typing.
The point was never that there wasn't a way to get it, but that there wasn't a way to get it without scripting it. No direct shell access. It has to be manipulated. But that's unrelated to the performance discussion.
-
Construction on the NTG outdoor meeting space has begun (it is due for new lighting and all new paint this week.)
-
@DustinB3403 said in What Are You Doing Right Now:
But I don't need to write a script to pull the UPTIME
No script needed to pull the uptime manually in PS either.
But I'm sure most admins have better things to do than to manually pull the uptime of each device in the terminal individually. No idea why that's even a discussion. If you are doing that, something already isn't right.
-
@Obsolesce said in What Are You Doing Right Now:
But I'm sure most admins have better things to do than to manually pull the uptime of each device in the terminal individually. No idea why that's even a discussion. If you are doing that, something already isn't right.
Well, in BASH it is a one liner to almost instantly get it from tons of machines. It's actually a pretty common task. In Windows, if you want the same report, it is very doable, but not quite as transparent.
But if you are logging into machines at all, then uptime remains a continuous thing you want.
-
@scottalanmiller said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
But I'm sure most admins have better things to do than to manually pull the uptime of each device in the terminal individually. No idea why that's even a discussion. If you are doing that, something already isn't right.
Well, in BASH it is a one liner to almost instantly get it from tons of machines. It's actually a pretty common task. In Windows, if you want the same report, it is very doable, but not quite as transparent.
But if you are logging into machines at all, then uptime remains a continuous thing you want.
Bash was designed to be THE interface to manage a Linux system. So yes, it was designed to manage the system with small simple commands that you use all day.
This want the case with PowerShell. Windows went a different direction. If you want a simple CLI with simple commands, use CMD. If you want a serious and powerful scripting language for Windows, use PowerShell. Nothing is better than that for Windows.
-
@Obsolesce said in What Are You Doing Right Now:
This want the case with PowerShell. Windows went a different direction. If you want a simple CLI with simple commands, use CMD. If you want a serious and powerful scripting language for Windows, use PowerShell. Nothing is better than that for Windows.
I don't agree here. CMD was simply left to languish. MS made it really, really clear that PS was the absolute final word in tooling for managing Windows. They stated this over and over again. And unlike Bash which was just a generic system that predated linux by decades, PS was custom built for this one purpose.
-
Steaming some veggies for me. Heating up some soup for Liesl.
