egil

At least it is https, so no mitm attack. You have to trust the Sandstorm developers, even if you download the source and apply all the steps manually. If the site gets compromised, the attackers can modify the source and the website documentation for the PGP verification.

The major security issue is that containers share the same kernel as the host, with the whole kernel syscall interface as attack vector. VMs run separate kernels that only interface with the host via the hypervisor.

The article was published with a new url: http://www.wired.com/2015/09/bjarke-ingels-2-world-trade-cen...

I reckon the authors point is that they control how they use it. They might not own it all (but they sure hold the copyright to much of it), but no other entity outside of their control is going to pull the rug from under their feet.

I concur. I was quite late to jump on the e-book wagon (mostly due to DRM), but I am quite happy "renting" books on my Kindle, being aware of its limitations. When I read, I don't feel the pages turn, either with a dead tree book or e-book. I simply read the streams of characters, and my hand does some sort of strictly irrelevant gesture to move the stream ahead.

From a more practical standpoint, the possibility of storing loads of books on my Kindle is greatly appreciated. I recently spent a week at a hospital, and the Kindle entertained me through days of idle time.

Calling Stallman "Linux creator" is quite an achievement in ignorance when he explicitly refers to the os as "GNU/Linux" to give GNU credit.

How about security? Quite an important topic to simply gloss over. Comparing containers with virtual machines without mentioning the difference in abstraction and attack surface gives a false sense of security for the former.

Previous discussion: https://news.ycombinator.com/item?id=9417773

Works fine here from Norway.

For more info, see https://github.com/rcarmo/raspi-cluster/blob/master/README.m...

Google cache of the original page in question, http://webcache.googleusercontent.com/search?q=cache:TSYSWNu...

The actual gzipped image file at https://images.collabora.co.uk/rpi2/ is 156 MByte, so I guess 3Gb is the size of the partition imaged, not of the actual data consumed.

He has also written an excellent C# book, C# in depth http://csharpindepth.com/ .

That is probably because Surface RT has pretty much been rejected by the market. There is no business in beating a dead horse.

Up again here from Norway.

And people prefer different coding styles. One persons "icky syntax and forced use of whitespace" is another ones preference. At the same time, you trade your freedom of whitespace expression with simplicity when you need to understand or work with code written by others.

I adore them for their pronunciation skills if they literally shared it through speech. (Sorry, I had to :) )

The status quo for such projects is to use Busybox, and I reckon it will continue for projects where systemd etc is too much.

Of course. Terrible mistake!

To be honest, I for one know very little about the important persons in <enter orthogonal branch of science here>, gay or not. We might all know about the terrible fate of Alan Turing, but I don't expect non-cs people to know.

(Thanks to gpvos for the correction of faith->fate. )

It is, but at the same time you waste all the resources and time invested in the new employee.

However, it would be an improvement if the hn title could address an international audience.

Git was originally created to manage the Linux kernel. It is indeed complex, but it has to be at that scale. Git might not be the best option for every project, but I find it quite easy to use at the trivial scale as well. (How do you beat 'git init' ? No repository setup or anything.)

Have you looked into the (re)rendering on the client? We had a similar issue with an extjs application rendering dead slow on ie9. By suspending the rendering while the app was loading/transitioning (using batchLayouts in the ext case), IE loading time improved significantly.

The kickstarter was posted yesterday. See https://news.ycombinator.com/item?id=7737134 for the previous discussion.

Maybe the Ivy League universities should set up a distributed cdn so they can share the load when the next amazing paper hits the net :)

In that case, you would lock down the key so it could only be used to execute the strict subset of commands to do its job. It is very common practice, but is not mentioned at all in the blog post.

If you bypass the geo-block, you don't have a license to play the geo-blocked content either, regardless of your Netflix subscription.

If it breaks, you surely need to fix it (and having plans to fix it or upgrading it due to lack of replacement parts etc is of course neccessary). However, there is also inherent risks in upgrading such appliances, so it should not be done simply because the hardware is old.

"If it ain't broke, don't fix it." - Bert Lance