Still better than .dot
Comment on dotnet developer
aberrate_junior_beatnik@midwest.social 10 months ago
Ok, but we all should admit: .net is a terrible name.
Honytawk@lemmy.zip 10 months ago
nexguy@lemmy.world 10 months ago
I totally agree.socialmedia
neutron@thelemmy.club 10 months ago
And then there’s .net classic and .net core. Making up two entirely separate names shouldn’t be difficult for marketing executives.
dan@upvote.au 10 months ago
.NET Core doesn’t exist any more. It’s just .NET now.
The classic version is mostly legacy at this point too.
NegativeInf@lemmy.world 10 months ago
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.
Zangoose@lemmy.one 10 months ago
Hi, it’s me, the intern refactoring the spaghetti .NET core backend. I’m not in a basement though. AMA
dan@upvote.au 10 months ago
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.
kogasa@programming.dev 10 months ago
Not an intern, but this week I’ve unraveled some mysteries in ASP.NET MVC 5 (framework 4.8). Poked around the internals for a while, figured out how they work, and built some anti-spaghetti helpers to unravel a nested heap of intermingled C#, JavaScript, and handlebars that made my IDE puke. I emulated the Framework’s design to add a Handlebars templating system that meshes with the MVC model binding, e.g.
and some more shit to implement variable-length collection editors. I just wish I could show all this to someone in 2008 who might actually find it useful.
neutron@thelemmy.club 10 months ago
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.