3 ms·

> Seems like a great PowerShell replacement. It sounds like it can potentially replace way more than PowerShell. I mean, why would a .NET shop even bother with

> Seems like a great PowerShell replacement. It sounds like it can potentially replace way more than PowerShell. I mean, why would a .NET shop even bother with Python or any form of shell scripts if they can attach a shebang on top of an ad-hoc snippet? And does anyone need to crank out express.js for a test service if they can simply put together a ASP.NET minimal API in a script?

pjmlp 1y ago
Ecosystem, people keep forgetting syntax, grammar and standard library isn't everything. That is why even the languages I dislike and am not a big fan of, have a little place on my toolbox.
- motorest 1y ago
  > Ecosystem, people keep forgetting syntax, grammar and standard library isn't everything. Ecosystem means nothing if you have comparable or even better alternatives in a framework of choice. Also, it's not like the likes of Python don't have their warts. Anyone with a cursory experience with Python is aware of all the multiplatform gotchas it has with basic things like file handing.
  - mattmanser 1y ago
    For me, every time I have to use python it's the package handling that leaves my head spinning. It still feels like the bad old days of npm. I think it's a popular language with scientists despite that because they don't have to care about portability, reproducability or needing your replacement to be able to run it without ever speaking to you. I use python infrequently enough that every time it's a pain point.
    - mardifoufs 1y ago
      Not sure I follow. I wish python was as good as npm/node_modules. And how is nuget better than npm? Is it just package quality or something else? I rarely use npm and I'm not a webdev but whenever I use it I think it's pretty great.
      - mattmanser 1y ago
        When I said "bad old days" I mean a previous iteration, not the state today. I'm talking about the early days of npm. In the early days of npm a lot of install examples would do global installs, you'd often end up with a confusing mess in npm. Nowadays people are much better at only doing project level installs and even correctly telling you whether to have it as a dev dependency or not.
        mardifoufs 1y ago
        Ah sorry that makes sense!! Yeah, that's exactly what how I feel too. It's sad that npm has improved so much while Python's packaging hasn't (not by default at least, whereas npm is basically a default in js projects by now), in the same time frame.
  - pjmlp 1y ago
    If you work alone, maybe. Some of us have to take other devs into consideration. Human collaboration is also part of the ecosystem.
- int_19h 1y ago
  I don't think ecosystem or people forgetting syntax would be an issue in a .NET shop.
  - pjmlp 1y ago
    It certainly is, unless the folks at the .NET shop get to be the ones writing the missing libraries, related tools, books, tutorials, conference talks,....
trog 1y ago
I've been writing shell scripts in PHP for more than 20 years for this reason. Don't work on a lot of PHP sites any more but I still do most of my shell scripting in it. I think this'll be a big win for C# users once they get used to the paradigm shift. I notice another poster said it's a bit slow but for many common use cases even half a second startup time is probably a small price to pay to be able to write in the language you're familiar with, use your standard libraries, etc.
pragmatic 1y ago
Python has a lot of libraries (ai, machinelearning, data stuff, whatever) that no one has bothered porting to .net (or other platforms). .Net is usually a second tier target but python ALWAYS has first tier support (along with java and usually go).

pjmlp 1y ago

Ecosystem, people keep forgetting syntax, grammar and standard library isn't everything. That is why even the languages I dislike and am not a big fan of, have a little place on my toolbox.

motorest 1y ago
> Ecosystem, people keep forgetting syntax, grammar and standard library isn't everything. Ecosystem means nothing if you have comparable or even better alternatives in a framework of choice. Also, it's not like the likes of Python don't have their warts. Anyone with a cursory experience with Python is aware of all the multiplatform gotchas it has with basic things like file handing.
- mattmanser 1y ago
  For me, every time I have to use python it's the package handling that leaves my head spinning. It still feels like the bad old days of npm. I think it's a popular language with scientists despite that because they don't have to care about portability, reproducability or needing your replacement to be able to run it without ever speaking to you. I use python infrequently enough that every time it's a pain point.
  - mardifoufs 1y ago
    Not sure I follow. I wish python was as good as npm/node_modules. And how is nuget better than npm? Is it just package quality or something else? I rarely use npm and I'm not a webdev but whenever I use it I think it's pretty great.
    - mattmanser 1y ago
      When I said "bad old days" I mean a previous iteration, not the state today. I'm talking about the early days of npm. In the early days of npm a lot of install examples would do global installs, you'd often end up with a confusing mess in npm. Nowadays people are much better at only doing project level installs and even correctly telling you whether to have it as a dev dependency or not.
      - mardifoufs 1y ago
        Ah sorry that makes sense!! Yeah, that's exactly what how I feel too. It's sad that npm has improved so much while Python's packaging hasn't (not by default at least, whereas npm is basically a default in js projects by now), in the same time frame.
- pjmlp 1y ago
  If you work alone, maybe. Some of us have to take other devs into consideration. Human collaboration is also part of the ecosystem.
int_19h 1y ago
I don't think ecosystem or people forgetting syntax would be an issue in a .NET shop.
- pjmlp 1y ago
  It certainly is, unless the folks at the .NET shop get to be the ones writing the missing libraries, related tools, books, tutorials, conference talks,....

trog 1y ago

I've been writing shell scripts in PHP for more than 20 years for this reason. Don't work on a lot of PHP sites any more but I still do most of my shell scripting in it. I think this'll be a big win for C# users once they get used to the paradigm shift. I notice another poster said it's a bit slow but for many common use cases even half a second startup time is probably a small price to pay to be able to write in the language you're familiar with, use your standard libraries, etc.

pragmatic 1y ago

Python has a lot of libraries (ai, machinelearning, data stuff, whatever) that no one has bothered porting to .net (or other platforms). .Net is usually a second tier target but python ALWAYS has first tier support (along with java and usually go).