JPDev@programming.dev to Programmer Humor@programming.dev · 2 years agodotnet developerprogramming.devimagemessage-square12linkfedilinkarrow-up114arrow-down10
arrow-up114arrow-down1imagedotnet developerprogramming.devJPDev@programming.dev to Programmer Humor@programming.dev · 2 years agomessage-square12linkfedilink
minus-squareaberrate_junior_beatnik (he/him)@midwest.sociallinkfedilinkEnglisharrow-up1·2 years agoOk, but we all should admit: .net is a terrible name.
minus-squareneutron@thelemmy.clublinkfedilinkarrow-up1·2 years 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-up0·edit-22 years 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-squareNegativeInf@lemmy.worldlinkfedilinkarrow-up0·2 years 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-squareZangoose@lemmy.onelinkfedilinkarrow-up0·2 years agoHi, it’s me, the intern refactoring the spaghetti .NET core backend. I’m not in a basement though. AMA
minus-squareneutron@thelemmy.clublinkfedilinkarrow-up1·2 years agoI am so sorry, man. No one deserves this.
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.
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.
Hi, it’s me, the intern refactoring the spaghetti .NET core backend. I’m not in a basement though. AMA
I am so sorry, man. No one deserves this.