{"id":3385,"date":"2010-10-27T15:35:52","date_gmt":"2010-10-27T14:35:52","guid":{"rendered":"http:\/\/www.itwriting.com\/blog\/3385-lessons-from-evernotes-flight-from-net.html"},"modified":"2010-10-27T15:35:52","modified_gmt":"2010-10-27T14:35:52","slug":"lessons-from-evernotes-flight-from-net","status":"publish","type":"post","link":"https:\/\/www.itwriting.com\/blog\/3385-lessons-from-evernotes-flight-from-net.html","title":{"rendered":"Lessons from Evernote\u2019s flight from .NET"},"content":{"rendered":"

Evernote has released version 4.0 of its excellent note-taking product. Software developers have taken particular interest in the blog post announcing its release<\/a>, because of what it says about .NET, in this case the Windows Presentation Foundation, versus native code:<\/p>\n

\n

Evernote 4 is a major departure from Evernote 3.5 in every way. While 3.5 added tons of great new features, there were some problems we simply couldn\u2019t fix: the blurry fonts, slow startup times, large memory footprint, and poor support for certain graphics cards were all issues that the technology behind 3.5 (Windows .net and WPF) was incapable of resolving. As a result, we ended up chasing down platform bugs rather than adding the great features our users wanted. <\/p>\n

So we decided to start over from scratch, with fast, native C++ that we knew we could rely on. As you\u2019ll see, the results are amazing. This new version will set a foundation for rapid improvement.<\/p>\n

Evernote 4 is designed to give you a great experience on any computer that you use, whether you\u2019re on a netbook, a five year old Windows XP machine or a super fast top-of-the-line Windows 7 computer.<\/p>\n

On our test hardware, Evernote 4 starts five times faster, and uses half the memory<\/strong> of Evernote 3.5.<\/p>\n<\/blockquote>\n

A bit of background. WPF was introduced in Windows Vista and was originally intended to be the main GUI API for Windows, until the notorious reset midway through the Vista development cycle which marked a retreat from managed code back to native code in the operating system. I\u2019d guess that the issues faced by the Evernote team were not so different from those faced back then by the Windows team at Microsoft.<\/p>\n

WPF is not only based on .NET. It also uses DirectX and hardware acceleration under the covers, enabling rich multimedia effects. The layout language of WPF is XAML, giving freedom from scaling issues which cause hassles in the native API.<\/p>\n

So what are the lessons here? Is WPF no good? <\/p>\n

It is not so simple. WPF is brilliant in many ways, offering the productivity of .NET coding and a powerful layout framework. However it was a technology which Microsoft itself hardly used in its key products, Windows and Office \u2013 a warning sign.<\/p>\n

When Microsoft built Visual Studio 2010 and .NET 4.0, the development team used WPF for the Visual Studio shell. This move by an internal team to create such a complex product in WPF was good for the framework itself. The font issue was addressed, performance improved. Evernote might not have found all its issues fixed in version 4.0, but it would likely have been better.<\/p>\n

After I tweeted about Evernote\u2019s experience, a couple of Microsoft folk contacted me to make this point. The trouble is, even version 3.5 of WPF was not the first version, and it never sounds altogether convincing if, when a customer complains about your product, you tell them everything is fine in the latest and greatest build. Why did Microsoft not get this right before?<\/p>\n

That said, I am sure the latest WPF is better than before, though it is still heavyweight relative to native code. Factors that might suggest a WPF solution include:<\/p>\n