gsmethells

Yep. This the classic end-to-end argument, a white paper all CS grads must read https://en.m.wikipedia.org/wiki/End-to-end_principle

So ... explain like I'm five. :) How can Diffie-Hellman, which has been taught ad infinitum as a safe method for key exchange, be discussed like it has a loophole?

Given our current computer architecture models, we'll run into Planck's constant or some other universal constant eventually. Already the path forward has more to do with increasing the number of cores rather than the performance of a single core.

"In a distributed system, you can know where the work is done or you can know when the work is done but you can't know both."

A simple thought experiment will quickly tell you that's not true. Given a task queue, the compute process that pulled the task and put a result could easily provide where and when and give you both.

The diaper pattern is a well-know anti-pattern. But the idea that all exceptions are thus evil is a giant leap of logic that is hard to swallow.

I concur, wine fridges are totally a necessity!

Ceph, OpenStack Swift, GlusterFS, OrangeFS, Lustre.

https://en.wikipedia.org/wiki/Clustered_file_system#Distribu...

https://en.wikipedia.org/wiki/Object_storage

Will each disk in the system be weighted so that different size disks can be used in the system over time? OpenStack Swift offers this and is useful to not lock-in disk size at design time.

Is the goal to provide POSIX file access as NFS and AFS do? The mention of object storage as a future direction feels like the early "the sky's the limit" euphoria of a new project that has yet to adopt specific end goals.

If there ever was a need for a TL;DR, then this is it. Anyone care to take a crack at it?

Cool!

Know your dependencies well. Keep them few and far between -- and well vetted.

This was originally on Slashdot in 1990's and has been on HN before.

Perhaps mosquitos are here to manage the human population in the ecosystem.

Why did you guys choose Ceph instead of OpenStack Swift? Just curious.

They do have some differences if you look close enough.

What happened to division of labor? Progressive enhancement? Mixing CSS into JS is just muddying the water.

Security is completely ignored here. Is a web app controlling your microphone or camera a Good Thing? Maybe yes, maybe no.

The fact that anyone has to even think about code size is the real problem.

Yes, downloading a giant JS lib for one function is insane, hence the ton of tiny dependencies.

However, it is equally insane that basic SDK expectations found in every other language has yet to come to be pre-implemented by the JS engine in the web browser itself. Some basic code ought to already be on the localhost the moment your app arrives.

Wow! GitHub is being influenced by GitLab (who released this feature recently in GitLab 8.4).

To me, it's more about choice of programming language than performance. Though the latter is very important, I think the former is what will open up doors to making the browser a platform of choice (pun intended). Currently, it feels like JavaScript is the Comcast of the web. Everyone uses it, but that's only because there aren't any other options available to them.

When is this going to be available for DICOM medical images? :)

http://dicom.nema.org

Is this trying to be OpenStack Swift or leverage OpenStack Swift?

Hypermodularization sounds like the latest euphemism for Dependency Hell (tm).

Geez, how far off is Frankenstein?

I just used this to book my flight to PyCon 2015 oddly enough. It was pretty damn easy to use and let me jump from its search results to directly booking with Air Canada. Pretty smooth...

I remember when this first hit slashdot back in 1999. It's still a damn funny analogy. 8)

Maybe it's the word "share" that needs changing instead.

As far as packaging and deployment of a native executable goes, I thought it odd to not mention Excelsior JET (http://www.excelsiorjet.com) as I believe that's the only Java compiler that can handle all of the JDK (gcj isn't there yet).