[tracker1]

While I agree, one even commented as much on some of the Relevant GitHub issue threads... .Ner is a pretty good platform for web and backend work.

I prefer Rust or even Node/TypeScript myself, but have worked a lot in the .Net space since pre release in 2002.

[smackeyacky]

Having worked on node and .NET on Linux professionally I vastly prefer .NET

JavaScript and typescript exist in a bizarre netherworld of not really being type safe and not really being type free. It makes for some truly strange code bases that reflect whatever is cool but none of it aged well.

Npm is hideous. Dreadful. It’s a daily struggle especially if you have to deal with private repos (azure specifically).

C# is just a better language. Better, more expressive collections and a type system that has consistency. EntityFramework for databases is fantastic, node has nothing remotely as good.

.NET and Nuget are a breeze. I would go as far as saying Linux is the superior experience when programming .NET since you spend a lot of time with the CLI and power shell sucks.

[tracker1]

I like the Deno runtime approach more than Node, but that's another issue. I find JS/TS is pretty great for ETL and input data validation and transformation where the flexibility of the language and io streams lend themselves to that work. Not to mention when you need a slightly different script.

I also like the expressiveness and productivity I get out of it. Though many of my issues with C# comes down to the culture in practice more than the language.

C# is better when you have more firm constraints and the coffee will be longer lived and worth the complexity. It's just the difference between a script and a full program/application with all that involved in the Net space.

My point was mostly that. Net is still pretty good for things in Linux even without a blessed, official desktop UI framework.

[dellamonica]

What is wrong with PowerShell core?

*PS core is the one based on the new versions of dotnet.

[smackeyacky]

I am old - my first work experience was on Unix machines in the late eighties and I just find Linux a lot easier to work with if you're spending a lot of time with a CLI. You have more default tools at your disposal (bash, make, sed/awk/grep etc) which all have to be installed manually on a Windows machine.

Powershell tries to be everything and ends up being too much, badly implemented. I have dabbled in it for Windows/Microsoft specific things (Outlook manipulation) but while you can write a PS script that tries to do something like delete all yesterdays mail with a particular characteristic, in practice it often doesn't work due to the impedence mismatch between COM and PS. I like the idea, I really do, but it's just not as straight up practical as the Unix tools.

[dellamonica]

Yes, if you don't use dotnet and is already used to Unix tooling then it is a tough sell, but otherwise the integration with dotnet is quite good.

[tracker1]

You can build a web server and do ETL with PowerShell?

If it's a simple script, bash is in the box... If it's more complex, I'll reach for a more rich scripting platform.

[dellamonica]

I mean, the entire dotnet is available, you can do anything in PS though obviously that is not always the smart call.

It has been very useful to me to use as a REPL on my own C# libraries, I can instantiate and use types from these libraries and interface with the file system and network on an ad hoc basis.

[pjmlp]

That is the problem nowadays, it feels like ASP.NET/Azure is driving .NET roadmap.