I already see lots of broken pages because of NoScript, I often use bookmarklets to strip the page of excessive (mis)use of design... so as long as you can show me the text I will be fine, thank you. ;) Not the typical user though, I know.
On the other hand I am thrilled about security and privacy possibilities this brings to the table! So I can't wait to try it out. Keep up the good work!
(Of course, this will change over time, just that I don't expect it to be 100% secure by June)
Have you ever tried Google+? In my experience this is one of the most demanding pages out there and it is almost unusable in Firefox for me. The only reasonable way for me to use it is to switch to Chrome. (Linux, cheap Intel Celeron with 2.6 GHz)
Also, just tried loading the site on a much faster internet connection and everything worked, although text entry was slightly laggy on a new note. Still couldn't figure out how to get a count of my notes though.
There has been talk in PhantomJS on making multiple engines available. It's the 11th most commented issue[1], out of 1k+ issues.
Sometimes a broadly used browser-engine is important, but other things servo could be useful.
One issue with PhantomJS (on webkit) is that it crashes quite frequently and use a lot of memory[2], areas where Servo may do better.
[1] https://github.com/ariya/phantomjs/issues/10209
[2] https://github.com/ariya/phantomjs/issues?utf8=%E2%9C%93&q=i...
export OPENSSL_INCLUDE_DIR=$(brew --prefix openssl)/include
export DEP_OPENSSL_INCLUDE=$(brew --prefix openssl)/include
./mach build
Alternatively, if you don't mind shadowing the system's default version of OpenSSL, you can try `brew link --force openssl`.Well, we obviously all gonna use it that way though :-)
Web compatibility is a long road, and it's crucial for us to be able to know what missing functionality is most important and the places where we need to focus on performance the most. The purpose of the package is to help us find and prioritize bugs and missing features. We want to know which sites are the most broken (and, even more importantly, which missing features are breaking those sites). From the Web developer side, we also want early feedback on use cases that may be slow today, so that the browser engine can eventually become a great experience for everyone.