coreyoconnor

Ideally yes. However, that's assuming a lot of privilege that the average consumer wouldn't have at all in this case.

Given the responses I succeeded in my goal: highlighting the absurdity in the current system :)

IIRC prior to being treated you agree to be financially liable for the costs. Prior to even knowing that that will be or even the costs involved. Or even if you know what is involved are you going to understand what a reasonable cost is? EG: Sling is easy but what about a x-ray study? Is that 200$ or $150?

Just like a proper capitalist system! You know, like when you agreed to pay whatever for your iPhone prior to even know it'll work.

Good to know that the US health care system will impose these individuals with the cost. Shame on them for not properly researching the product. They should have considered their consumer choices against the possibility of cancer years later. No doubt the medical bankruptcy some will have is deserved.

Obviously sarcasm. This is, however, how the current US medical system behaves. It's impossible that these patients would have the capacity to evaluate medication sources like they would any other product. Many likely had no opportunity or choice. Yet the US supports a system that punishes an individual for aspects well beyond the individual.

Conceptually, there is a lot of overlap. Apollo had a few layers to it but would, more or less, matched kubernetes plus additional tooling. Dare I say closer to openshift? Brazil, the build tool, infrastructure and repository was similar to using nixpkgs. Brazil had some features beyond nixpkgs that were absolutely essential for an business like Amazon, but otherwise the goals and even techniques overlapped.

I onboarded very, very quickly by already knowing nixpkgs and container management. The concepts translated well. A few aspects that didn't either were things Amazon handled that other tools have yet to encounter: Cool to learn about. Or historical bits that didn't matter: fine to ignore.

I agree.

Disclaimer: Also ex-amazonian, left like one year ago.

"When a HD died early, you could also imagine undetected manufacturing flaws that finally gave way. With SSDs, at least in theory that shouldn't happen"

This is incorrect. As much of the argument seems predicated on this I don't see a real issue.

Incorrect: Even a single person company described above will still need to handle GPDR requests. The operational requirements is not 0 even for a company retaining no unnecessary records.

Regardless of the size of organization, GDPR applies. In particular, note the section "Right of Access":

* https://en.wikipedia.org/wiki/General_Data_Protection_Regula...

Which requires the organization to supply information about use of personal information. This will have an operational overhead regardless of scope of Personal Information used.

For a worse-case (hopefully impossible) variant of what this request looks like: https://www.linkedin.com/pulse/nightmare-letter-subject-acce...

Oh please somebody correct me if I'm wrong. Otherwise that's a silly amount of operational overhead for bootstrapping. Even for systems designed from the start to not use personal data: The org would still need to handle a rather detailed and costly administrative request.

Carta is "software to help companies, investors, law firms, and employees modernize the way they manage ownership"

The homepage is https://carta.com/

Or it's "Charleston Area Regional Transportation Authority". ;-) I find it's amazing how many of these type of announcements fail to provide even the slightest into to their little bubble.

"Rollup is a module builder" and here's a link to the main page: https://rollupjs.org/guide/en

(Which is mentioned nowhere in that announcement.)

For shits and giggles I recently compared a spot instance CPU miners of monero vs spot instance GPU miners. I don't have the exact numbers on hand but IIRC the CPU miner was ~50% the cost in terms of $/hash.

I like the UI of Amazon Chime: https://chime.aws/

Though it is business focused.

1. There is a free plan, but limited.

2. Android, iPhone, Mac, and PC clients that work well.

Occasional notification syncing issues. That's about the worse of it.

3. I don't know; I haven't used Skype in years. Better than Lync and Polycom.

4. Yep.

There are a few apps mentioned for helping with this problem. In my experience Should I Answer? is the best by far.

* https://play.google.com/store/apps/details?id=org.mistergrou...

None of the apps solve the random VoIP callers. I would be perfectly happy with an app that outright blocked many VoIP providers.

Still bad IMO. I do not recommend using an e-reader for PDFs. I use a Kindle DX on a rare occasion.

A tablet computer with pen provides the best experience IMO. I've used a iPad and an Android tablet before. Both have excellent PDF reading software. I recommend Bookari on Android. The Microsoft Surface, however, beats everything else I've tried.

I did a similar build. I had no clue other people were thinking the same. The entire build I was super nervous. I kept worry I was buying components for a system that wouldn't be worth it. "How can this be so cheap?" I kept wondering. Admittedly, I went for used E5-2687Ws from ebay. Which increased the risk IMO.

My experience mirrors the article and your experience. Fantastic value for a really great workstation! I happily run several VMs for dev work, the usual IDEs and switch between games with zero issues. I picked Noctua coolers, same as the article, and the noise level is also excellent.

In addition: Now the marketplace will be flooded with former Yahoo employees. Up until now I would claim < 6 months on average to find a job (Even in SV). Now... Not so sure.

Why is this bad? Is there a licensing issue?

Otherwise, re-using a known layout will not play into my purchasing decisions.

Partition template parameters into request-dependent and request-independent sets. Memoization with persistence of the request-independent template instantiation. "static" then is the special case of no request-dependent template parameters.

I think I'll write an article "pure functions with memoization are the next big thing!" Except they are not "new" because they've been around for decades. The only difference is the Web 2.0 uberkids haven't "discovered" the concepts yet.

A line that struck me as familiar: "I should add that my hearing’s getting worse. Which doesn’t help at all."

I wonder if the author is sure his hearing is actually getting worse or his perception is getting worse?

I once thought the same thing. tldr: Nope. My hearing is fine. Anxiety causes my brain, afaict, to always be on the lookout for threats. No sound was being filtered from my conscious. The perception was that I "couldn't hear". I could hear fine, but I couldn't filter out unimportant from important. The result is something that seems like bad hearing.

Taking anti-anxiety drugs solved the problem for me. Like magic I could hear fine. Conversations, even in noisy situations, became easy to perceive and follow.

I couldn't find any documentation on this at the time. The doctor didn't think much about the idea. I wonder if anybody else had the same experience?

Depends on the change of real estate prices relative to changes in wages. Wages can go up but after cost of living the effective wage might be quite low.

Doesn't taste like pulled pork to me. To me the flavor is bubblegum pineapple. Which is fantastic! Ranch 99 will have Jackfruit on occasion. Wear latex gloves while cutting. The "latex like substance" is in the white pith of the fruit. There is a lot of the stuff and it's really, really sticky.

I've run into the same opinion from other developers: "there is very little quantified info about what works and what doesn't" In my experience they are looking for the wrong answers. They want an answer of how to design software. How to define the entities, classes, functions etc. Quantitative software development discusses less of design, IMO, and more organizational factors. EG: How a companies organization and processes impact quality. This is not what practitioners expect. Yet, this is where the science of software development is. Thanks for the book reference! An economic perspective on software quality sounds enlightening.

I don't know why you were downvoted. This is a nice summary.

Related to this is the Games Outcome study. While this specifically studied the development of games, the observations and conclusions are applicable to all software development:

* http://www.gamasutra.com/blogs/PaulTozour/20150126/235024/Th...

I'll give it a try.

Rockets require dense oxygen to burn. Near the edge of the atmosphere the air is not dense. Cooling the air increases the density. Cooling the air a lot will produce the dense oxygen required by a rocket. Air also contains water vapor. Cooling the air will increase the density of this water vapor. Forming liquid water then ice. This water and ice will block air flow. Which will prevent a cooler from producing the oxygen required. To prevent ice this cooler uses antifreeze. Methanol is sprayed (?) into the air being cooled. The methanol is then collected from the air and recycled. The collected liquid will contain water absorbed from the air. This prevents the ice and removes the water. Producing the dry, cold, and dense air for the rocket. The innovation is using the methanol efficiently. The methanol introduced to the air absorbs water. This decreases it's antifreeze ability. This also increases the liquids volume. Where the oxygen is collected for the rocket the air is dense, low volume, and dry. This is where a low volume of pure methanol is required. From that point forward the air is less dense, warmer, and less dry. A larger volume of less effective antifreeze is required. By recycling the liquid and pumping the liquid forward they match the requirements with the liquid.

That's the best I can do YMMV :-) Cool stuff!

Assuming I understand the question correctly: Yes.

Nix uses a pure evaluation model so it enjoys the property: An artifact in the nix store is uniquely identified by the closure used to build the artifact. For any artifacts A, B if and only if the closure used to build the artifact are equal then the artifact file path will be equal.

This creates opportunities for sharing between builds that can be hard to achieve in other systems. One form of sharing "referencing a derivation in multiple apps" works as expected, just like other systems: Each app will reference the same artifact.

(a derivation is the closure to be evaluated to build an artifact in the nix store. Well, attribute set of closures.)

Suppose a derivation is assigned to the variable "commonData" and two derivations "appX" and "appY" reference this closure. "commonData" will be built once and both app derivations will receive a path to the same file in the nix store.

The other form of sharing comes from the equality comparison being based on the closure and not the name used to reference the closure.

Ehh.. I'm butchering the explanation... I think there is a succinct PL term that covers this.

Suppose we have a derivation:

let x = mkDerviation { name = "foo"; builder = aBuilder; src = /share/src/foo; }

which is referenced by another derivation

let y = mkDerviation { name = "bar"; builder = aBuilder; src = /share/src/bar; inherit x; }

"y" will force the evaluation of the "x" derivation's closure. The source directories, since they are not in the nix store, will be copied to the nix store first. (By an implicit conversion between local files and nix store paths)

So far so good, but what happens if there is another derivation like so?

let z = mkDerviation { name = "zab"; builder = aBuilder; src = /share/src/zab; somethingLikeX = mkDerviation { name = "foo"; builder = aBuilder; src = /share/src/foo; }; }

"somethingLikeX"'s equation is equal to "x" but not the same reference.

What will happen if z is evaluated after y? (assuming aBuilder is the same) First, the derivation "somethingLikeX" will be evaluated. Ah ha! That closure is equal to the closure for "x" above! Which has already been evaluated. So that evaluation result will be shared. Even though "z" does not directly reference "x".

This can result in more sharing than the developer explicitly requested: Equal closures are shared.

Yep. Definitely! One caveat, in short, is: Everything involved in the build must be placed under the nix store (/nix/store). Which, for some software, can cause issues: They might have a hardcoded runtime path that references /usr/lib. Nix provides tools to resolve these assumptions, but they can still be a sticking point at times. There is also, more or less, a unsafePerformIO that can be used. Which is discouraged. Still, for private builds the cost can be acceptable.

Check out nix / nixpkgs. :-) That's the closest to Brazil IMO.

I think the discovery of exoplanets will have far reaching cultural implications.

We've gone from believing planets are extremely rare to knowing planets are relatively common. Now that planets are known to be common, does that mean life is common? What will that do to the cultures that, in effect, support themselves on the belief that humans and the earth are unique?