This is great to hear, but perhaps comes too late for people like myself. Node.js has been by go-to platform from around 2014 until last year. But around September last year, I found myself thrust into the .NET ecosystem (due to a client project). Within a few months, I realized that it too, had finally become usable by default (unlike the last time I tried it, when it was too tightly coupled to Windows). In fact, it felt like what Node.js would be, if it had strong typing built-in, and had a good standard library that eliminated a lot of the module management and churn. I'm now finding it hard to return to Node.js.

▲

throwanem 4 days ago | parent | next [-]

Interesting. I haven't looked hard at .Net despite some advocacy from past colleagues. Perhaps I should.

	▲	pimbrouwers 4 days ago \| parent [-]
		I can second this experience. I arrived roughly 10 years ago, right in time to see netcore1.0 emerge. Been onboard even since. You should absolutely check it out. The compilation story (native aot) is what I'm currently most excited about it.

▲

3 days ago | parent | prev | next [-]

[deleted]

▲

ninetyninenine 3 days ago | parent | prev [-]

Eh the focus on OOP is my main issue with it. It’s not my style in that sense.

	▲	WorldMaker 2 days ago \| parent [-]
		F# is a great FP language that runs on .NET and there's a growing field of FP proponents working in C#, sort of a Trojan Horse situation trying for a best of both worlds (easy onboarding for C# junior devs, but deep FP options thanks to things like C#'s clever LINQ syntax). LanguageExt is a big part of some of those ecosystems: https://github.com/louthy/language-ext