Why we use .NET Framework 4 or excess to a greater extent than .NET Framework 3.5?

.Net Framework4.0 comes up with some of major changes as compare to previous versions of .Net Framework3.5 and2.0Following are list of Major Changes in .Net4.0

• ControlRenderingCompatabilityVersion Setting in the Web.config File 
• ClientIDMode Changes 
• HtmlEncode and UrlEncode Now Encode Single Quotation Marks 
• ASP.NET Page (.aspx) Parser is Stricter 
• Browser Definition Files Updated 
• System.Web.Mobile.dll Removed from Root Web Configuration File 
• ASP.NET Request Validation 
• Default Hashing Algorithm Is Now HMACSHA256 
• Configuration Errors Related to New ASP.NET4 Root Configuration 
• ASP.NET4 Child Applications Fail to Start When Under ASP.NET2.0 or ASP.NET3.5 Applications 
• ASP.NET4 Web Sites Fail to Start on Computers Where SharePoint Is Installed 
• The HttpRequest.FilePath Property No Longer Includes PathInfo Values 
• ASP.NET2.0 Applications Might Generate HttpException Errors that Reference eurl.axd 
• Event Handlers Might Not Be Not Raised in a Default Document in IIS7 or IIS7.5 Integrated Mode Changes to the ASP.NET Code Access Security (CAS) Implementation 
• MembershipUser and Other Types in the System.Web.Security Namespace Have Been Moved 
• Output Caching Changes to Vary * HTTP Header 
• System.Web.Security Types for Passport are Obsolete 
• The MenuItem.PopOutImageUrl Property Fails to Render an Image in ASP.NET4 
• Menu.StaticPopOutImageUrl and Menu.DynamicPopOutImageUrl Fail to Render Images When Paths Contain Backslashes