If the government fines individuals for not digging holes in their back garden every day then suddenly it's economically viable to dig holes in your back garden every day, but it doesn't mean it's overall productive.
23,184 karma · joined May 5, 2012
james@incoherency.co.uk
https://incoherency.co.uk/
If the government fines individuals for not digging holes in their back garden every day then suddenly it's economically viable to dig holes in your back garden every day, but it doesn't mean it's overall productive.
In what sense?
This may be related to the commonly-held fallacy of "cash on the sidelines". Cash is always on the sidelines. Cash is not created or destroyed by buying and selling stocks or bonds. Cash is simply handed from one party to another, but the cash has to be held by somebody.
> you're suggesting there's some kind of information flow from the anticipated body of the script back up to the imports
Yes, I am suggesting this. I don't think it is possible to write programs without either anticipating what you're going to write down below before you get there, or else being able to go back and edit what you already wrote.
Of course agent harnesses allow the latter, but raw models without a harness can still do an exceptionally, superhumanly, good job of straight-line programming with no editing.
> Infer imports from context, infer body from context + imports. All strictly causal.
Of course it's causal, that's kind of a reductive way to look at it.
Just infer the entire program from context and then type what you inferred.
Pain is part of reality. Suffering comes from wishing reality was different to how it is.
The link to the original for Scion Capital is a 404 FYI: https://billiondollarpdf.com/entry/burry-scion-subprime/ - the original seems to be included towards the end in the PDF at the top of https://www.michael-burry.com/scion-capital-michael-burrys-l... and is fascinating reading.
What does "strict receipt" mean? Every entry seems to be labelled "strict receipt".
EDIT: The Warren Buffett one is also a 404: https://billiondollarpdf.com/entry/superinvestors-graham-dod... - what's going on? Are people taking these PDFs down in response to high traffic from this site? Or you put these links up without checking them?
https://www.superinvesting.com/pdf/The-Superinvestors-of-Gra...
Plainly it was not a "need" since people managed for thousands of years without it.
This is what progress looks like.
It's not a really great reason, because what's the downside of going back to the client? But that's the best reason I can think of.
Assume H(P,i) to be a program that tells you whether the program P will halt on input i. Returns true if it halts and false if it doesn't.
Define a new program G(x) that halts if x does not halt on itself as input and loops forever if x halts on itself as input:
def G(x):
if H(x,x):
while True:
pass
else:
return
Does G(G) halt?If G(G) halts then H(G,G) is true so we end up in the infinite loop, a contradiction. If G(G) does not halt then it returns without looping, also a contradiction.
So our halting oracle H does not exist, so there can not be a function that tells you whether another function will halt on itself as input, so there can not be a function that tells you in the general case whether some other computation will halt, QED.
This is like a much cooler version of a thing I made a few years ago for simulating model oscillating engines: https://incoherency.co.uk/oscillating-engine/
Almost everybody's revealed preference is to stay alive rather than to not be alive, otherwise we'd see a lot more suicide.
> making an important choice such as bringing life into the world, without considering the consequences, is already somewhat unethical.
This is a view you can take, but it's not as obviously important as you seem to think.
An alternative view is "making an important choice such as FAILING to bring life into the world, given the opportunity to do so, without considering the consequences, is somewhat unethical."
If the standard was truly that you can't have kids unless you're sure they're going to have a great life, then we would have gone extinct millions of years ago.
Why?
As a human being who was once born, I am extremely grateful for my existence, and how much thought my parents put into it beforehand is of practically no consequence.
You seem to imply that if parents haven't already committed to giving their kids a perfect childhood with perfect parenting then the kids are better off not living at all?
You can't because LLMs that can hold a conversation didn't even exist 5 years ago, let alone automatically hooking themselves up to a bidirectional handwriting interface.
You can't just point at one part of this and say it is as old as geocities and think that that makes the whole project uninteresting. The project is greater than the sum of its parts.
I can't believe so many people in this thread are so critical of it.
I was working on an SDF-based CAD tool. One of the things I want to be able to do is select a pair of surfaces (which are identified by a "surface id" propagated up the expression tree) and add a blend between those two surfaces (e.g. a fillet or chamfer).
Here is a video demo of how far I got by doing it myself and using o3 (I think?) to help: https://www.youtube.com/watch?v=LOvqdlDbkBs
The video is a bit confusing because there was some screen-recording lag so it sometimes looks like I clicked on something other than what I clicked on.
You can see that the strategy I have implemented there works most of the time but at the end it fails to apply the blend.
That strategy is to rewrite the expression tree using distributivity so that blend arguments are siblings, and then apply the blend at the union/intersection (min/max) that is their parent.
But this fails when you need conflicting pairs of blends.
The problem is: given an expression tree describing an SDF, (but where the value passed up the tree is a tuple `(distance, surface_id)` rather than just distance), and given a set of fillets of the form `(surface_id_1, surface_id_2, radius)`, produce a new expression tree which fillets all of the places where those surfaces join.
In ambiguous situations, for example the 2 surfaces come together at an edge, and then that edge runs into a 3rd surface, I don't mind how you resolve the region near the 3rd surface as long as it is intuitive and predictable for the end user.
I spent quite some days working with various agents to come up with a solution to this and still haven't managed to find one.
Maybe you could do it in a couple of hours yourself?
> Opus 4.8 references being monitored, which isn’t the case.
It kind of plainly is the case that they are being monitored?
"I think someone's listening to my thoughts" ... "No, we're not, carry on as usual!"