I believe statcouter also now works without Flash.

I've never coded something in Erlang, but I believe Rust tried to copy the idea of message passing from Erlang.

I think message passing allows you to copy the data, which would mean you might not need to deal with cache coherence issues.

Like this ?:

https://blog.mozilla.org/blog/2013/04/03/mozilla-and-samsung-collaborate-on-next-generation-web-browser-engine/

When you get rid of everything else on the phone, but just the browser. You use less resources to view the same pages.

It's that simple.

Yes, that is the great advantage of FirefoxOS, even if the project fails, we'll have a lot more standards at W3C which allow HTML5-apps to do all kinds of things HTML5 wasn't able to do before.

That is the whole point of FirefoxOS, get rid of all the extra layers and pretty much only run a rendering engine on top of a Linux kernel (exceptions are things like: wpasupplicant).

It has been shown that FirefoxOS can use less resources than Android that way.

Which is good because their target market is not the first world countries, but countries like Brazil, Mexico, Poland, Spain. Where smartphones are not as widespread (in Spain and Poland it might be certain parts of the country or markets), mostly because of the price of the phone itself. Prices may drop, but especially parts like touchscreens are very expensive and will probably remain that way.

Because this is a new market for smartphones, FirefoxOS actually has a chance of getting a proper share of the market in those countries.

FirefoxOS might be a little less flashy than the first-world competitors, but they pretty much have no marketshare in those countries anyway. And will probably not have much of a marketshare any time soon.

There is no Android in FirefoxOS.

They do support running on the same Linux kernel though, so they can make use of the same drivers that were already developed for devices that can run Android.

Actually, it has been shown FirefoxOS can run on less powerful devices than Android can.

Apple actually does give back.

Have a look at their work on WebKit and LLVM.

They want to replace sendmail in the OpenBSD base install. Complexity of configuration and probably code for auditing is probably the reason.

Thus I think the biggest reason that OpenSMTPd exists is because Postfix doesn't have licence that is compatible with inclusion in the OpenBSD-base install.

Probably OpenSMTPd will be awesome and having more choice might be useful too.

pf improvements ? The last import of pf in OpenBSD was years ago.

OpenBGPd has a really, really old port and depends on certain kernel interfaces currently only available on OpenBSD (although they could be ported to FreeBSD).

It will take a long time, I'm afraid. :-(

I think the Google backbone example isn't a good example because very little people have the luxury problem Google has: lots of links which are not a 100% utilized and enough developertime to spend to fix.

Websites was a an example of 'cloud computing', I wouldn't call Amazon AWS and the others chump change.

SDN isn't about commodity hardware per se, it is more about having an API to configure/control and especially automate the network.

With OpenFlow you can preconfigure most of the forwarding entries (not just routing) as well.

Software defined in my mind just means, it has an API so that application specific software can control it.