the real goal of free Google Analytics is to get people to place the javascript tracking snippet on their webpages so they can collect data for Ads and now paying customers.
I doubt many sites are going to bother with all the complexity of implementing and utilizing SPDY when only chrome supports it. To see significant advantage with SPDY vs something like long-polling you need to build your app around it, and if you need to support long-polling methods anyways, not very many sites are going to bother.
I think you are confusing SPDY[1] with WebSockets[2]. SPDY is Google's experimental replacement for HTTP. You don't build your app around it at all - from the application layer it should be mostly invisible.
SPDY can be implemented as an Apache module[3] which could be used only when the browser supports it.
It is true that WebSockets replace long polling, but there are plenty of libraries that abstract the differences out nicely.
well perhaps somewhat understandable, why should i be happy with an inferior interface because of it? This falls very squarely in the category of "not my problem, but you just made it my problem anyways"
I see this as part of a big trend towards software and software designers that think they know what you want better than you do, and its an endless source of frustration for me, and im sure many others.
>BSD is losing its ground against Linux (and Windows).
why is that important? why do the BSDs have to be gaining on Linux to be a viable, useful system. If your entire goal becomes "competing" with Linux, you miss the entire point many people chose a BSD to begin with, a stable, well thought out, usable system. The ZFS integration clusterfuck with freeBSD pretty clearly shows the results of trying to rush things so they are somehow better than linux.
Merging all the BSDs together to "fight" Linux is stupid and shortsighted, the OpenBSD philosophy is about more than security tweaked defaults for freebsd, its an entire process from conception of a new program, to implementation, to maintenance of the code. If you try to reduce it to a common codebase, it is just going to be freebsd + tweaks, which negates the entire reason people want to use OpenBSD to begin with.
You might be right. The problem with software I suppose: if it grows, there will be pain. If it doesn't, well, let's just hope it won't stall and die quietly.
I don't mean to compete or fight against Linux in that sense. I suppose I just want to see more things happening in BSD land (Amazon instances, VirtualBox, native Java) but if that happens, could potentially disturb the stability of *BSD itself.
And yes, I do know (a bit) the principal behind OpenBSD that may not work well with other BSDs. Different goals that lead to different software development process.