&gt; I&#x27;ve checked out servo and compiled and started it in release mode - it required 600MB RAM and 700% CPU to load google(!) with the same speed as my little firefox with tons of extensions - forgive my ignorance but I&#x27;ve expected more from the hype.<p>Thanks for the bug report, but I can&#x27;t reproduce. According to the built-in memory profiler, Servo uses 39 MB of explicit allocations to load google.com, which is well in line with other browsers even without a whole lot of optimization for memory use.<p>A large amount of CPU usage during initial pageload, on the other hand, is a feature, not a bug. Using more resources lets us get the page loaded faster, which not only shows you the page faster but also typically reduces power consumption since we can get the CPU into an idle state.<p>&gt; Rust programs consume so much resources that it could just use a GC instead of the complex manual memory management.<p>Manual memory management isn&#x27;t about some broad notion of &quot;resource consumption&quot;: it&#x27;s about having low-level control of resources, which can not only reduce memory usage but also eliminate pauses. I think it&#x27;s very unlikely that the JavaScript garbage collector could be made thread-safe without regressing performance (which is what you presumably mean by &quot;just use a GC&quot;).<p>&gt; The syntax and the standard library is as &#x27;modern&#x27; as in cpp - I&#x27;m not as impressed as I was a fan of Mozilla.<p>Just to name the first features that come to mind: Rust has a module system and hygienic macros, which are syntactic features not in C++. Rust comes with a standard library that includes networking, which isn&#x27;t in C++.<p>&gt; Search the internet for optimizations, my firefox feels like as fast as chrome - sometime even faster. It just needs some tweaks.<p>Those &quot;tweaks&quot; are in fact likely to be slowing down your browser.