Re:The Case for C# and .NET
by TheRealDunkirk on Monday July 25, 2022 @07:05AM
(#32222851)
If you like the productivity, just wait till you try Rails.
[ Parent
| on HN ]
Re:The Case for C# and .NET
by kcartlidge on Monday July 25, 2022 @05:10PM
(#32230976)
> 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.
Re:The Case for C# and .NET
by TheRealDunkirk on Monday July 25, 2022 @10:19PM
(#32233507)
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.
Re:The Case for C# and .NET
by kcartlidge on Tuesday July 26, 2022 @05:05PM
(#32244006)
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).
Re:The Case for C# and .NET
by 202206241203 on Monday July 25, 2022 @08:07AM
(#32223225)
Rails is still a thing in 2022?
Old habits die hard I guess. Some languages just need to buy a coffin already
Re:The Case for C# and .NET
by TheRealDunkirk on Monday July 25, 2022 @08:29AM
(#32223389)
LOL. That's good. Thanks for that.