JPDev@programming.dev to Programmer Humor@programming.dev · 11 months agodotnet developerprogramming.devimagemessage-square55fedilinkarrow-up128arrow-down10
arrow-up128arrow-down1imagedotnet developerprogramming.devJPDev@programming.dev to Programmer Humor@programming.dev · 11 months agomessage-square55fedilink
minus-squareaberrate_junior_beatnik@midwest.sociallinkfedilinkEnglisharrow-up2·11 months agoOk, but we all should admit: .net is a terrible name.
minus-squareneutron@thelemmy.clublinkfedilinkarrow-up0·11 months agoAnd then there’s .net classic and .net core. Making up two entirely separate names shouldn’t be difficult for marketing executives.
minus-squaredan@upvote.aulinkfedilinkarrow-up1·edit-211 months ago.NET Core doesn’t exist any more. It’s just .NET now. I think that changed around the release of .NET 5? The classic version is mostly legacy at this point too.
minus-squareneutron@thelemmy.clublinkfedilinkarrow-up1·11 months agoMy workplace insists on using dot net classic to recreate a twenty years old VB app that should be able to drink, vote, and drive. Please send help. SQL queries are a spaghetti mess and all the original devs are probably gone or dead.
minus-squareNegativeInf@lemmy.worldlinkfedilinkarrow-up0·11 months agoJust because it’s no longer supported doesn’t mean there’s not some poor intern refactoring spaghetti backend in a basement somewhere using it.
minus-squaredan@upvote.aulinkfedilinkarrow-up2·11 months agoSure, but you can still find plenty of info on it by searching for .NET Framework or .NET 4.6. All the documentation is still available. Its just not in the spotlight any more.
minus-squareLmaydev@programming.devlinkfedilinkarrow-up1·9 months agoIt is very much still supported and will be for a very long time. You just shouldn’t start any new products using it.
Ok, but we all should admit: .net is a terrible name.
And then there’s .net classic and .net core. Making up two entirely separate names shouldn’t be difficult for marketing executives.
.NET Core doesn’t exist any more. It’s just .NET now. I think that changed around the release of .NET 5?
The classic version is mostly legacy at this point too.
My workplace insists on using dot net classic to recreate a twenty years old VB app that should be able to drink, vote, and drive.
Please send help. SQL queries are a spaghetti mess and all the original devs are probably gone or dead.
Just because it’s no longer supported doesn’t mean there’s not some poor intern refactoring spaghetti backend in a basement somewhere using it.
Sure, but you can still find plenty of info on it by searching for .NET Framework or .NET 4.6. All the documentation is still available. Its just not in the spotlight any more.
It is very much still supported and will be for a very long time.
You just shouldn’t start any new products using it.