The only time I could ever see us adopting new calendar systems is when (if) we eventually migrate off-planet into space colonies or onto other bodies in the solar system. Why? Because only then will each colony have a completely different notion of what a solar year is, and different (or even entirely artificial) notions of solar days. In these colonies a standardized calendar system may arise. Or a chaotic web of independent calendar systems.
This attitude is exactly why Linux has such a horrible, horrible packaging experience. Building cross-distro packages is awful. Teaching users how to install packages is awful. Installing custom apt sources or repos to get newer versions of packages is awful. And we're getting stuck up on some inconsequential thing like a library will be duplicated. Guess what, OSX has been doing it successfully for years.
The Linux community is missing the forest for the trees.
Can we please stop talking about these "laws" that are based on absolutely nothing but observing an apparent trend that may not continue past tomorrow? Seriously, spoken to too many undergrads who think there's some sort of physical process or causal relationship driving Moore's law. It's bullshit. It's just people saying "growth has been this fast, and I don't know why, but I sure hope that growth continues to be this fast!"
Are there plans to work on integrating PGP encryption? N1 really looks nice but there are many people, like me, who can't move over until it gets e-mail encryption support.
Drupal has always performed like shit. 10/sec is actually pretty good for Drupal It's only good for managing static content, the only way you get any sort of performance out of it is super aggressive caching.
PHP is a slow abomination. The entirety of Drupal and all modules have to be bootstrapped and run on every request. It runs far too many SQL queries and those queries look atrocious (nested selects, tons of joins, etc).
Same with Magento Commerce. I was always shocked at just how slow it is.
We're using Haskell for server-side programming at my work and it's been fantastic. Functional programming is so well suited for stateless web services.
What I don't get about publishing the hashes, etc... if they are serving up tampered .iso files, why wouldn't they also change the website to serve the appropriate hashes for the hacked isos? For the verification to work I would think it needs to be PGP-signed and you should have the public key in advance.
I don't think MVC belongs on server-side web frameworks at all. It's not a continuously updating interactive display, it's a one-off thing. You don't have a model object sitting around sending messages to the view when it updates. This doesn't happen. There is no triangle of messaging. What really happens is a request comes in, and your "controller" is the one doing all the calling.
The HTTP server is by its very nature a pipelined or layered application. Requests are turned into responses through a series of transformations. They go down the layers as they work their way to your database, and back up the layers as they are built into responses. This is, incidentally, why functional programming is such a great fit for web servers.
The point is that we did not have an opportunity to influence the negotiations and therefore the text of the treaty. We instead are presented almost with a fait accompli that we must either accept or reject altogether.
I'd like to point out, in support of your arguments, that all artistic works are derivative. Creative works are not created in a vacuum. They copy and derive build upon the cumulative works of the rest of society. Nobody should ever have been entitled to a lifetime copyright.
Scala does not have lightweight threading. It uses the same thread pools from Java. All your millions of Actors are scheduled onto one of these thread pools.
> Congress shall make no law [...] or abridging the freedom of speech, or of the press