2 ms·

Viggity - I see you've been writing your apps in WPF. Did you see the news about Evernote switching from WPF to native code. What are your thoughts on that and

• viggity 16y ago
  Sure, I was following that story most of yesterday. I think it really comes down to what kind of app you're writing. Evernote could have written their app in assembly and it'd be screaming fast but it'd be a PITA to maintain. They chose to go C++ because speed is really important to their customers, but I think they're going to have a harder time adding new features and tweaking old ones. With such a robust, flexible system that WPF provides, you're obviously going to have some performance overhead, but creating new features becomes a lot more easy. And perf is obviously going to get better with time simply due to the speed of your average PC. For me, I absolutely love WPF. The thing I love about it is that it is stupid easy to make intuitive UI - I can put any kind of visual element ANYWHERE I want. And using MVVM lets me keep a very nice separation between my business logic and my presentation. In fact, I'm hooking up the same view model to several different views and via declarative binding, changes to one automatically update all the others. Granted, there is a fairly steep learning curve, but there is a lot more training material now than there was 4 years ago. Also, FWIW, I've been doing some Silverlight dev and if SL could step up a little and improve their binding system (WPF's is much more robust), I'd have no problem switching over to Silverlight. I consider them to be two branches of the same tech. I'm expecting a lot more parity between the binding systems in SL 5.