Another reason why .Net 3.0 should be called .Net 2.5 (or something similar)

Check out Kirk Allen Evan's blog entry ( . All through it, his reasons given point to calling it something less than .Net 3.0 IMHO.

Again, note that .NET Framework 3.0 is an additive release to .NET Framework 2.0. With .NET Framework 3.0, the languages still use the 2.0 compilers, and leverage the 2.0.50727 Framework.
It is based on 2.0 for everything so why not keep with that!!! The version number really doesn't make anything clear!

I lead the Chrome Developer Relations team at Google.

We want people to have the best experience possible on the web without having to install a native app or produce content in a walled garden.

Our team tries to make it easier for developers to build on the web by supporting every Chrome release, creating great content to support developers on, contributing to MDN, helping to improve browser compatibility, and some of the best developer tools like Lighthouse, Workbox, Squoosh to name just a few.

I love to learn about what you are building, and how I can help with Chrome or Web development in general, so if you want to chat with me directly, please feel free to book a consultation.

I'm trialing a newsletter, you can subscribe below (thank you!)