Hacker Newsnew | past | comments | ask | show | jobs | submit | burdock's commentslogin

Having seen this documentary, that is very much the point. In fact, I believe Fielder and Oppenheim intentionally biased the filmography to make you question everything: is "Liz" being intellectually honest? Does she understand what she did wrong? How does Fielder actually feel about the subject?

As the film ends, no questions are answered, no facts are presented to push or counter the narratives introduced, it just ends, and you're left wondering what just happened.

To my point, some of these questions have obvious answers, at some points EH is presented as honest, and at some points she is presented as deliberately obtuse. Some things are intentionally played up both in editing and acting to direct you to an answer. It makes you question everything, including the documentary itself, which is why I think it kind of transcends "documentary" as a genre.


thank you for sharing your perspective. I'm still eager to see the film, though I expected this sort of angle.

It's a passive-aggressive artistic approach. In this case, Holmes already has a tainted reputation. Show a bunch of awkward scenes of her, reinforcing the slander. But in the end, present no real conclusions or positions that could be criticized. "We're leaving it up to the viewer".

But they're riding the mob's wave, and exploiting her. Making everyone dumber.


That's not my perspective at all. The film is far more sympathetic to Holmes than you might anticipate. I don't want to spoil it, but, after watching I recommend you revisit both of our comments :)


I'll watch it. and it's possible. often the distributors position a film differently than the producers. e.g. a drama marketed as a comedy -- that may be happening here too.

but so far, most of the experience has been through the marketing , and the angle is obviously "let's make her look like a con artist"


I've written at length about my disdain for text interpolation in helm.

I've done some experiments using Apple's Pkl and CNCF's KCL, which look to solve these problems with a simple "configuration language".

I don't think either have very widespread adoption, though I did hear a while back that Apple is using Pkl internally.


I do thank the advent of LLM's for making the task of tracing through 3 layers of YAML rendering indirection to find an actual bug in layers of insanity. They are surprisingly good at it. A purist might look at the system and be taken aback in horror, but pragmatically the crazy templating things that used to be pretty major in terms of maintainability have become a lot less problematic.

I don't even mind text interpolation in helm that much. Yes, it's horrific, but it really doesn't become problematic until you are having an external system render the text being sent to helm that might be processed again after the fact with Kustomize. Your text might hit literally 3-4 different YAML rendering pipelines before it finally hits your cluster. Insanity

Hashicorp had a similar idea to this configuration language you are mentioning. They named it HCL. We do know how that turned out, but maybe that was more questionable design rather than problems endemic to the approach.


Even if you're all in on AI, it's still not a great situation. Do you want your agent to burn 10000 tokens fixing indentation bugs every time it touches a helm chart?

What takes effort for humans, takes effort for AI too.

And yeah, HCL was a horrible design. Anything else would have been better, Cue, jsonnet, dhall, pkl, etc. (I'm not sure which of those existed when HCL was created.)


HCL solves the problem of unknown values. It's certainly not a "horrible design" unless you're trying to compare it to something that does a different job.

For a single source of truth for YAML/JSON such as for Kubernetes manifests, any of the ones you list are fine though and a vast improvement on using Go templates for it.

(Yes I've used all of them - and indeed did the first public talk about Pkl two days after it was open-sourced, after several years of using it internally at Apple).


> Do you want your agent to burn 10000 tokens fixing indentation bugs every time it touches a helm chart?

If your agent is doing this you need to get a much better agent. It should call `helm lint` to find those errors.


Helm lint will only find problems with whatever text is supplied to the Helm chart. It will not catch a large hunk of the class of errors being discussed here. There is plenty of scenarios that are valid Helm that are still invalid to be supplied to a cluster.


I was responding specifically to finding indentation errors. Most of the class of errors you mentioned can only be validated by attempting to apply the manifest to a live cluster running the target API version anyway.


It's why, except for upstream charts, I use exclusively jsonnet (through kubecfg) when I can.

String interpolation is a pox on the ecosystem, especially given how YAML was only originally a debug helper...


Intellectual property has rarely ever been "the golden goose", despite the anecdotes of the few Henry Fords that exist.

Throughout history, the golden goose has typically been owning capital, and having market reach (see: advertising, the silk road).

No matter how amazing your IP is, if you can't produce it at economically viable scales, and if you can't put it in front of people who will buy it, then you have nothing. So venture capital comes along, buys you out, and takes all your future profits in exchange for the "risk".

On the other side of the coin, there's open source software developers, PhD's publishing papers for free, and your local musicians that like to play at events just for funsies.

I mean, imagine the kind of world we'd live in if medicine were focused strictly on profitable moats instead of open research, and... oh. Right.

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


That's why I think lower speed, high density 3D compute is a good candidate for future hardware.

By lowering the clock speed, power and heat drop exponentially.

I'm just hoping we figure out something logistically better than laminating chips together.


I completely agree. I'm betting on physical learning systems via reservoir computing personally. Will be going back to school to study nanotechnology soon to pursue this formally in addition to some experiments Ill be funding and running on my own dime as well. Have you ever seen steel ball bearings submerged in castor oil? If you apply an electrical current to that what do you think will happen? The most fascinating thing occurs, the ball bearings self organize into a network that can even display properties of hebbian learning if set up correctly! I suspect experiments such as these will eventually even raise the bigger question of, what is life actually? Another way to think about the potential of this area of technology is to think of a biological synapse, its about 1 micron in size right? Well, how many "neural atoms" can we fit in that space? 1000x1000x1000!! Its marvelous how much space there is when you shrink things down. Ill even go so far as to speculate that to create genuine superintelligence, youll need this technology Ill be working on to mature and form into some.new form of stochastic processor/computer


I've been thinking about going into biochem. Seems like an interesting problem space where, in the past year we've seen massive progress in our understanding of molecular biology.


Cloudflare Proxy, which is required for their ddos protection - and which as I recall accounts for like half of internet traffic - handles TLS termination at CF servers.

When you capture traffic at internet backbones, which the NSA does (Room 641A), you don't get to middle-man the encrypted traffic. Cloudflare gets access to unencrypted traffic, because they act as the TLS termination.

Most companies take this trade-off because "we can trust cloudflare", or "the data isn't that important, and besides it's encrypted the rest of the way anyway."


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: