emergentcypher

Umm, newspapers enjoy freedom of the press because the 1st amendment explicitly guarantees freedom of the press.

> Congress shall make no law [...] or abridging the freedom of speech, or of the press

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.

Good. Get off this ride. I'm asking why the hell we are still stuck with the current packaging schemes.

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.

OK, I'll grant it this, PHP performance has improved quite a lot in recent years.

Anything else.

Does it have encryption yet?

- PHP is slow. Unlike JS, it's generally interpreted and not JIT (unless you're Facebook).

- Drupal has to bootstrap itself and all modules on every request.

- Drupal makes waaaaay too many SQL queries

- Drupal generates horribly performing SQL queries

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.

That wording is worse than absurd. It's comical. Their ability to use a thesaurus does not make them intellectuals, in fact the exact opposite.

Howabout the question is, should Congress repeal the All Writs Act.

Really? What is this 10%?

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.

created to stop a threat to humankind that we must defend against

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.

Scala runs on JVM and uses the same OS-level threads. What's going on here is the actors are being scheduled to run on a thread pool.

Scala runs on JVM and uses OS-level threads.

However, Actors are not threads, so in a way it's like user threads. One million actors will be scheduled to run on a pool of OS threads.

Similarly the Haskell and Erlang are using lightweight threading.

This is why the JS ecosystem frustrates me. We're talking about an ES7 -> ES6 transpilation, which I will then have to transpile again to ES5. And that's before we even hit the VM/JIT.

How many more of these articles do I have to read?

How many more of these comments do you have to read?

Closed source. No thanks.

Now I can just get a free cert and turn on TLS. What's the problem, exactly?

Most people are not capable of running their own mail server. The convenience of services like Google, plus the risk of turning your mail box into a spam machine, vastly outweighs the downsides for most people.

I don't know why. It just adds a level of indirection. Comparing anything with gross pay is pretty meaningless.

I think the idea isn't that every single person will host themselves. But you could have an account with a local provider, and the network will be a built-up federation of local providers linking together. In this way you individually don't have to manage your own instance, but everyone's data isn't centralized and owned by one corporate entity and you effectively limit your trust.

Given the way Facebook, et al, are evolving however, I think the market will make this question moot faster than we can answer it.

Which tells us something about the nature of the bugs we will find in our programs.

The type-checker prevents certain classes of bugs, inconsistencies in types, lots of silly typos and mistakes. But it doesn't fix errors in our logic or algorithms. The type-checker doesn't know you should have added instead of multiplied, nor does it fix conversion errors at the borders of our programs where we, say, write a Haskell data structure into a JSON file.