[bob1029]

The performance really is astonishing in many areas now.

The part that keeps me hooked is the fact that I can stand up something capable of producing those numbers in 30 lines of code using 1st party dependencies only. I can then have a full prototype to demo by late afternoon, again having antagonized over exactly zero 3rd parties.

For me, the performance numbers aren’t just about speed while in production. It’s also about speed to production. Having the confidence that it’s almost certainly going to be fast enough by default keeps me from worrying about optimizing random bullshit throughout.

I still haven’t seen anything that comes remotely close to the combination of speed and stability offered here. I do some pretty nasty things with the runtime and it just copes. GC seems like pure magic now too. I continue to avoid things like LOH allocations with streams, but I don’t worry about it like I used to in the 4.x days.

[TheRealDunkirk]

If you like the productivity, just wait till you try Rails.

[kcartlidge]

> If you like the productivity, just wait till you try Rails.

I like Rails (vintage, Rails 5). Unfortunately DotNet and EF combined now have virtually the same productivity but with massively better performance. Which is a shame as Ruby is a great language.

[TheRealDunkirk]

I’ve tried very hard to use EF. If you think it’s equivalent to the productivity of ActiveRecord, well… more power to you, I guess.

[kcartlidge]

And that's why there are so many ecosystems - to cover the variety of tastes and preferences.

I think the end game may be one unique ecosystem per developer (like with JS frameworks).

[202206241203]

Rails is still a thing in 2022?

[henry700]

Old habits die hard I guess. Some languages just need to buy a coffin already

[TheRealDunkirk]

LOL. That's good. Thanks for that.

[SZJX]

PHP is still a thing since time immemorial… And will remain there for a long time to come. (Seems like they made quite some improvements in the latest iterations as well.)