631 karma · joined October 17, 2010
I really expected FF to be on par with Chrome in terms of rendering quality but that really turned out not to be the case in many small, yet annoying corner cases. They got big by incorporating the quirks of IE and then improving on that, maybe it is time they start thinking about implementing some of the WebKit rendering quirks and go from there.
I really want to keep on using FF and to love it but if it means I have to switch browsers for some of the sites I use daily that will be difficult.
Using FF 27 on OS X 10.9.2
Edit: Ah I should have clicked the TLDs :)
Edit 2: And on the Desktop just noticed the filter button, sorry, that one is invisible when I view the site on my phone
Current OS have a hard time dealing with such heterogenous systems so they decided to start from scratch: The entire OS is structured as a distributed system with a dedicated mini-kernel running on each core of the processor and potentially also your network card etc. They even disallow shared memory between the core kernels and solely communicate through a message passing system.
If you are interested in their approach check out the Barrelfish website: http://www.barrelfish.org
And here is a great overview of the architecture: http://www.barrelfish.org/TN-000-Overview.pdf
Keep on hacking!
On a different note, does anybody know why they started with native clients instead of one web client? I can think of some advantages of native clients (P2P streaming as the have it, better OS integration etc.) but when compared to the big disadvantage of having to maintain two codebases (Win + OS X) and deliver updates to both I would expect it to require more resources for them than one web client for all.
one of the builders here. We created this as a side project because a lot of times founders we talked to shared really interesting insights in person with us, but would be too busy to run a blog and write about their learnings on a regular basis. TIL List gives those people the ability to share their insights with others and everybody gets to learn something new every day.
We just launched and will soon start to send out the first emails, we hope you will be on board!
We are looking forward to your feedback!
According to Rossi the servers keep the old version around after rollout, so rollback wouldn't require them to push out the old binary again but just to restart the old process. This will probably only take a couple of seconds making rollback really fast if needed.
Really love the idea though, hope we get to see a purely device based version of this at some point (by chute or somebody else).