3 ms·
You made me go read. Its a shit-show of the complex packaging and build assumptions at source, the horrendous tooling, and the difficulty negotiating the change
by ggm 5y ago
You made me go read. Its a shit-show of the complex packaging and build assumptions at source, the horrendous tooling, and the difficulty negotiating the changes. .NEt is up to 5 or 6 and the email/forum threads seem to be talking about 2.x and 3.
I wish things weren't this complex. But then I remember how much I hate autoconf/configure/libtool, and think "hmm maybe it wasn't so bad after all"
Re-implement .NET in RUST?
- Goz3rr 5y agoFWIW .NET Core 2.1 and 3.1 are LTS versions, support for 2.1 ended last month and for 3.1 in December 2022. .NET 4 is not relevant in this context because of versioning changes over the years and can be ignored. .NET 6 will be the next LTS version, to be released later this year.