this post was submitted on 21 Jun 2023
28 points (93.8% liked)

.NET

1467 readers
5 users here now

Getting started

Useful resources

IDEs and code editors

Tools

Rules

Related communities

Wikipedia pages

founded 1 year ago
MODERATORS
28
submitted 1 year ago* (last edited 1 year ago) by sisyphean to c/dotnet
 

The original thread is on the devil’s website and I don’t want to direct traffic to it, so here’s a link to the tweet instead:

https://twitter.com/davidfowl/status/1671351948640129024?s=46&t=OEG0fcSTxko2ppiL47BW1Q

you are viewing a single comment's thread
view the rest of the comments
[–] douglasg14b 1 points 1 year ago* (last edited 1 year ago) (1 children)

TBH I wouldn't recommend you be building applications in .Net Framework.... Most complaints about it have been a solved problem for years with .Net Core/.Net 5+. And there are upgrade paths, at least if you aren't maintaining WPF/Winforms

Bugs and regressions? I wonder if that's for different things than I touch, I've had almost no disruptions for the last 9 years. But I've mostly worked on console apps and backends. Almost no UI work aside from some WPF and Winforms side projects ages ago.