Not really, https://en.m.wikipedia.org/wiki/First_Amendment_to_the_Unite...

Can you name even one case?

Probably because it's a good way to avoid spam filters in emails I guess, since the group posts would come straight from Google?

> .net framework 2.7 is guaranteed to be installed by default these days

Yes, but that wasn't the case back in the mid-2000s when VB6 was dying and no one wanted to migrate to VB.Net

WinForms in C# was pretty decent tbh. Not so sure about WCF/Metro/Modern and whatever it is now that Microsoft been releasing. They just stopped caring about consistent UI for apps on Windows altogether since ~2010 or so.

WinForms is fine but it makes it way too easy to put all your behavior in the code behind instead of doing things nicely. Which I guess is what you want for a non-programmer tool but it is a hassle for me. Either way the .NET UI situation is a mess and I’ve never seen the sense in picking up the latest flavor of the month since it will be out of favor by the time I have occasion to use it.

You say was but winforms is still supported in VS2022 and is probably my go-to if I need to hack together a small windows program.

Correct, but it hasn't been upgraded in over a decade. It no longer produces apps that are consistent with Microsoft's own the way it was until Windows 7.

Also, most machines did not have the .Net framework installed, and back then it was 20 MB download which was gonna take ~2 hours on dial up back in the day vs MSVMVM6.dll which was on all Windows versions from 98 until 7 at least.

Microsoft stopped supporting it. VB 6 was the last "true" Visual Basic. The .Net Visual Basic was not backwards compatible with the very large code base projects everyone had created over the years and ones on forums and websites like planet-source-code (before GitHub existed) and the many, many beginner-friendly books.

They had a conversion wizard to migrate VB 6 projects to VB.Net but it was very half hearted and never worked on anything except the very trivial code bases. Anything that used OCX and you were out of luck, except OCXs were very very common in classic VB development.

People kept writing VB6 as long as it was practical (Windows 7) and then either moved on to greener pastures or left coding altogether as it was becoming impossible to use modern libraries anymore and the overall learning paradigm have shifted from books/forums into video tutorials and "modern" languages.

Back in the day, Microsoft figured it was easier to simply erase all the borders.

https://devblogs.microsoft.com/oldnewthing/20030822-00/?p=42...

Meanwhile, Windows is still shipping MSVBVM6.dll and the IE-4-compatible OCX files for compatibility with apps made using mid-1990s APIs.

How would they have known that those certificates got distrusted? The article says the certs in question were not on any known revocation list.

https://learn.microsoft.com/en-us/security/trusted-root/2019... and https://www.microsoft.com/en-us/security/blog/2018/10/04/mic... both list the cert in question

Try doing the same in Go and it's even worse.