this post was submitted on 07 Feb 2024
1630 points (99.3% liked)

Programmer Humor

19548 readers
1016 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
1630
dotnet developer (programming.dev)
submitted 9 months ago by [email protected] to c/[email protected]
124 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 90 points 9 months ago (3 children)

Ok, but we all should admit: .net is a terrible name.

[–] [email protected] 28 points 9 months ago (1 children)

And then there's .net classic and .net core. Making up two entirely separate names shouldn't be difficult for marketing executives.

[–] [email protected] 10 points 9 months ago* (last edited 9 months ago) (2 children)

.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.

[–] [email protected] 2 points 9 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.

[–] [email protected] 7 points 9 months ago (4 children)

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.

[–] [email protected] 1 points 7 months ago

It is very much still supported and will be for a very long time.

You just shouldn't start any new products using it.

[–] [email protected] 2 points 9 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.

@using (var obj = Html.HandlebarsTemplateFor(m => m.MyObject))
{
  Name: obj.TemplateFor(o => o.Name)
}

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.

[–] [email protected] 5 points 9 months ago (1 children)

Hi, it's me, the intern refactoring the spaghetti .NET core backend. I'm not in a basement though. AMA

[–] [email protected] 2 points 9 months ago

I am so sorry, man. No one deserves this.

[–] [email protected] 5 points 9 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.

[–] [email protected] 18 points 9 months ago

Still better than .dot

[–] [email protected] 8 points 9 months ago

I totally agree.socialmedia