i found this particularly confusing because we all know that “over” is the only sane choice.
342 karma · joined May 20, 2020
notnmeyer.at.hn
i found this particularly confusing because we all know that “over” is the only sane choice.
even then though, it’s more that complex needs are complex and not so much that k8s is the thing driving the complexity.
if your primary complexity is k8s you either are doing it wrong or chose the wrong tool.
whether it’s a physical or digital medium the artist is expressing their creativity and manipulating the tools to realize that vision.
i use it to take notes during the day at work and then use the notes for our standup.
probably too far for me, but very interesting to follow someone on this journey
it works out very well.
would i rather pay more in taxes for a nicer looking freeway or have it be utilitarian? ehhhhhhh, im unsure.
even then, one maintainer makes an excellent suggestion: give folks a list of the specific vars to set for various tools, and the pr author shoots it down as too much work.
the approach to this reasonably good idea feels flawed and effectively dead.
6 years and about 6 prs and most went nowhere.
without question everything should provide opt-out (or even better, opt-in) for telemetry.
is there middle ground for standardized opt-out vars without it being all or nothing?
maybe DO_NOT_TRACK_<identifier>?
it’s not flawless, but its strengths outweigh the weaknesses.
i still need homebrew for casks, but that’s fine.
“look at the scatter plot again” is anthropomorphizing the llm and expecting it to infer a fairly odd intent.
would queries like, “does the scatter plot visualization look like any real world objects?” may have produced a result the author was fishing for.
if it were the opposite situation and you were trying to answer “real” questions and the llm was suggesting, “the data is visualized looks like notorious big” we’d all be here laughing at a different post about the dumb llm.