Live data from Hacker News

20 years on AWS and never not my job

daemonology.net

61–70 of 73 posts

Re: 20 years on AWS and never not my job

#61
post #16

Colin, if I remember correctly, you first ran Tarsnap servers on Ubuntu before you made FreeBSD work on EC2. At what point were you confident enough to switch to FreeBSD?

I think cc1.4xlarge was the first instance I ran the Tarsnap service on. Being HVM made me far more confident -- PV dramatically increases the risk of VM/paging bugs, which is exactly the way to get silent data corruption.

So... I'd have to check my notes to be sure but I think fall 2011?

Re: 20 years on AWS and never not my job

#62
post #5

He gave them so much free labor

This... they really owe him something, IMHO. Hell, discounted service so he can make a better margin on Tarsnap sounds good to me!

I do have a few "free" AWS accounts! But they're for FreeBSD stuff (development, publishing official images, and FreeBSD infrastructure which Amazon hosts) -- I would never use them for my business.

I'm sure I could get away with it and nobody at Amazon would even notice, but it's the principle of the thing.

Re: 20 years on AWS and never not my job

#63
post #37

Netflix is a big FreeBSD user and a big AWS user, do they run FreeBSD on AWS? Would be the obvious sponsor to me as they rely heavily on the infrastructure built by volunteers like Colin

I don’t think they do. Netflix uses FreeBSD specifically for their custom-built CDN/streaming servers, which are hosted directly with ISPs … not on AWS. Their user-facing catalog app, however, runs on Ubuntu servers hosted on AWS. At least that’s what I recall reading here on HN.

Yes, that's correct. They're not idiots and realize that spinning up FreeBSD instances in EC2 can be very useful for development purposes -- the largest EC2 instances can run a buildworld very very fast -- but they have no need for FreeBSD/EC2 for their production workloads.

Re: 20 years on AWS and never not my job

#64
I had forgotten that you had to individually request AWS services early on. I checked my email history from 2007 and it's true, I was initially only granted access to "Amazon E-Commerce Service"! I got a separate email confirming that I had signed up for S3. Funny that they hadn't yet figured out that the automatic "package deal" is one of their biggest selling points.

The next service I signed up for was "Alexa Web Information Service". Web search as a service, back when "Alexa" was the search company they had acquired, not a voice assistant. By mid-2007 I was (finally) accepted into the EC2 beta. The rest, as they say, is history.

Re: 20 years on AWS and never not my job

#65
post #9

The author calls it a 'joke' that Heroes are just unpaid Amazon employees, but reality doesn't become a joke just because it's funny. The asymmetry here is staggering. I find myself holding back private research because I don't want to provide free R&D for a value-extraction machine that is already efficient enough. The author was at least dependency-driven in their contribution, but outside that kind of dependency,…

AFAICT, large saas players can simply implement the software interfaces regardless of business source licenses like what happened to redis, no? Or is there some specific protections for API surfaces that I'm not aware of. I vaguely recall Google v Oracle almost established some protections but then got deferred in later ruling. My memory is hazy on that though...

Re: 20 years on AWS and never not my job

#66
post #9

The author calls it a 'joke' that Heroes are just unpaid Amazon employees, but reality doesn't become a joke just because it's funny. The asymmetry here is staggering. I find myself holding back private research because I don't want to provide free R&D for a value-extraction machine that is already efficient enough. The author was at least dependency-driven in their contribution, but outside that kind of dependency,…

AFAICT, large saas players can simply implement the software interfaces regardless of business source licenses like what happened to redis, no? Or is there some specific protections for API surfaces that I'm not aware of. I vaguely recall Google v Oracle almost established some protections but then got deferred in later ruling. My memory is hazy on that though...

Indeed. And with the frontier AI models it's worse than that. You can literally just have them write test cases for the product you want to clone, then set it loose reverse engineering the code base.

That said, all these models are trained on the open source code bases presumably, so it would be interesting to see if AI-blackbox reverse engineering actually holds up in court.

Re: 20 years on AWS and never not my job

#67
post #66

Earlier quoted context omitted.

AFAICT, large saas players can simply implement the software interfaces regardless of business source licenses like what happened to redis, no? Or is there some specific protections for API surfaces that I'm not aware of. I vaguely recall Google v Oracle almost established some protections but then got deferred in later ruling. My memory is hazy on that though...

Indeed. And with the frontier AI models it's worse than that. You can literally just have them write test cases for the product you want to clone, then set it loose reverse engineering the code base. That said, all these models are trained on the open source code bases presumably, so it would be interesting to see if AI-blackbox reverse engineering actually holds up in court.

My gut says it would infact hold up in current US courts, but only because the lionshare of corporations want it to and the courts have been stacked in their favor.

I personally believe it should not and that AI code should NOT be considered a "clean room" method. That said, IANAL.

Re: 20 years on AWS and never not my job

#68

Earlier quoted context omitted.

Or SSPL, which extends AGPL with even more sharing requirements.

The SSPL is not an open-source license.

Yes it is. It plainly meets all the criteria in the definition iff AGPL meets them too.

Re: 20 years on AWS and never not my job

#69

Earlier quoted context omitted.

The SSPL is not an open-source license.

Yes it is. It plainly meets all the criteria in the definition iff AGPL meets them too.

The central difference is that SSPL discriminates against specific fields of endeavor, while the AGPL doesn't; see

* https://web.archive.org/web/20230411163802/https://lists.ope...

* https://opensource.org/blog/the-sspl-is-not-an-open-source-l...

* https://en.wikipedia.org/w/index.php?title=Server_Side_Publi...

Re: 20 years on AWS and never not my job

#70

Earlier quoted context omitted.

Yes it is. It plainly meets all the criteria in the definition iff AGPL meets them too.

The central difference is that SSPL discriminates against specific fields of endeavor, while the AGPL doesn't; see * https://web.archive.org/web/20230411163802/https://lists.ope... * https://opensource.org/blog/the-sspl-is-not-an-open-source-l... * https://en.wikipedia.org/w/index.php?title=Server_Side_Publi...

Which fields of endeavor? Does it say you can't use the software to run a nuclear power plant, or a military jet? Does it say you can't use it in a restaurant?
Post reply on HN