“Internet Explorer 7 provides security through a robust new architecture, security features that help defend against malicious software (also known as malware), and new ways to better protect against the theft of personal data from fraudulent websites, a practice known as phishing.”
That being said, the very first security issue for the final code is already a fact. Security firm Secunia has released a security advisory and a proof of concept. It’s not a severe issue, but I feel this doesn’t bode well for the future.
On a related note, IE7 will be pushed to clients as a high priority update. Another fun fact is that you need to reboot after upgrading. Let’s rephrase that: you need to reboot after installing Microsoft’s web browser! You can install Seamonkey, Firefox, Opera and others without rebooting and they all work fine. Obviously, the reboot is because of its integration in Windows. But why does it need to be integrated if others can do it without the black magic?
The fact that they’ll force it through the automated update service means there will be a quick adoption rate for IE7. The bad news is that all web developers can now start their compatibility checking (and probably IE7 CSS hacking) or they’ll be bugged about it by the clients. I can hear you thinking “but there have been betas, you should’ve checked with those”. In normal circumstances I’d agree, but Microsoft has their own idea of the alpha-beta-rc-release cycle. The IE7 betas changed so much that you couldn’t rely your testing on them. The betas should have been released as alphas which would make today’s final release a beta – that’s what Microsoft’s final releases usually are anyway.
One last point (for now): what the hell did they do the interface?!