HN user

n_jd

25 karma
Posts0
Comments12
View on HN
No posts found.

I was also pleasantly surprised, especially by how easy it was to setup disk encryption. I probably wouldn't have done so otherwise.

If this paradigm catches on there's no reason you won't be able to do the same thing with your own infrastructure.

I know this is a straw man because I can't know what sort of infra you're imagining, but I suspect a lot of people would be more comfortable with their builds stored on S3 under the scrutiny of their security team rather than on their engineers' laptops.

Been a while since I've read them but I recall there was info about the FSB and northbridge, which no longer exist outside the CPU. They've been replaced by internal memory controllers and PCI-E controllers.

CC NC forbids using the material for commercial purposes [1]. On 'use', opensource.com defers to the four freedoms [2], which includes the freedom to use software for whatever you like. So by opensource.com, software licensed under CC BY-NC-SA 4.0 is not open source. Also they don't mention creative commons when discussing open source licenses [5] because it doesn't make sense for code.

I can see why you might think opensource.com says that open source "literally means the source is public" if you only read the first sentence in their defining article [3]. Fair enough, this is a common misunderstanding [4].

[1] https://creativecommons.org/licenses/by-nc-sa/4.0/

[2] https://opensource.com/law/10/10/license-compliance-not-prob...

[3] https://opensource.com/resources/what-open-source

[4] https://www.forbes.com/sites/wenjiazhao/2012/07/06/beliefs-a...

[5] https://opensource.com/law/13/1/which-open-source-software-l...