- Compilers: Mono's DMCS, GMCS, MCS are written in C#. ECJ (Eclipse Java's compiler) is written in yes, Java. In fact there is no CUDA compiler written in shader languages does not prove that there is the performance issue using shaders.
- there are archivers/extracters that are written in managed languages, JVM depends on archived Zip files and it does most of the time using Java snippets. In most cases the performance of Java/C# working with archiving is at least OK. Most people would not use Java based archiver because is not named: WinZip, WinACE, etc. and is a customs issue, not necessarily a VM issue
- browsers, renderers and encoders are really where is hard to use a VM language when you want fine grained performance, drivers too, so they tend to be written in C/C++.
Yet, there are places where JVM for example was used as an optimizer (the query planner of Oracle DBs is using a JVM, because HotSpot can optimize the query computation equation. It is great to get a runtime compiler that optimize the code based on DBA's patterns, not static precompiled templates.
At the end, Evernote was complaining for an issue that is not dependant on .Net managed side, they complained on drivers that have issues with WPF drivers or WPF design. I can argue that C/C++ side was too hard of the WPF. WPF (Windows Presentation Foundation) have a COM/C++ fundations which provide a mini-framework of accelerated UI on top of DirectX 9. Combinations of bad performance of DirectX 9 + XP/Vista/Win7 with integrated video cards was the issue, wasn't it? Did I read other article? In fact, how could Microsoft use WPF in their IDE, if it was so blurry and slow? Why SharpDevelop uses it too? I think that maybe most of those issues were fixed either as a part of WPF (from .Net 4) or by video drivers providers. The startup time complained also was because WPF loads much more things (like DirectX9 on Win Vista/7 is not loaded as a default framework, so there is the need to load more libraries), and memory is likely to be related on the same issue.
In fact the XWT (the new cross-platform API for MonoDevelop and maybe Mono) is based on WPF on Windows, Gtk# and Cocoa# and it will use the WPF designer for designing UIs.