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

How do you know that for sure? How can you be absolutely certain that LLMs are what will lead to AGI?


I’ve yet to meet a single person who claims AGI will happen without recycling the same broken reasoning the peak-oil retards were peddling a decade ago.

Talking to these people is exhausting, so I cut straight to the chase: name the exact, unavoidable conditions that would prove AGI won’t happen.

Shockingly, nobody has an answer. They’ve never even considered it.

That’s because their whole belief is unfalsifiable.


What if you're in 30 °C weather?


High twist wool, unlined, adds basically zero heat (“summer weight wool” is a term that may include all these qualities). Doesn’t even do much to block wind (but does block the sun, a bit!). Totally fine in that range. That’s before resorting to something like an unstructured linen jacket (ever seen Lawrence of Arabia? Those guys are wearing plenty of clothing in the heat, a linen jacket is nothing) or warm-weather cottons like a seersucker (I’ve not bothered with any of that for jackets, myself, as light wool does fine for me, though I have several other pieces in linen).

Hell I own sweaters that are totally comfortable up to about that point, and higher if there’s a breeze. It’s all about construction and fabric.


> People aren’t allowed to mutilate babies

Circumcision?


Native speakers also seem to have given up on "less" vs "fewer" entirely.


Is the result is molecular identical? If so, no.


Trump Claims He Can Overrule Constitution With Executive Order Because Of Little-Known ‘No One Will Stop Me’ Loophole

https://theonion.com/trump-claims-he-can-overrule-constituti...


> I think being able to take and return futures or promises and handle them how you wish is better ergonomics.

You can do that. If you don't await an async call, you have a future object that you can handle however you want.


Yeah but to be fair, that can have adverse effects if you, say, busy wait.

The sync code might be running in an async context. Your async context might only have one thread. The task you're waiting for can never start because the thread is waiting for it to finish. Boom, you're deadlocked.

Async/await runtimes will handle this because awaiting frees the thread. So, the obvious thing to do is to await but then it gets blamed for being viral.

Obviously busy waiting in a single threaded sync context will also explode tho...


There are [1] and [2] for function arguments and loop variables, respectively, but nothing for the general case. Note that a type checker will complain if you re-assign with a different type. Pylint also has [3] for redefining variables from an outer scope, but Ruff doesn't implement that yet.

[1] https://docs.astral.sh/ruff/rules/redefined-argument-from-lo...

[2] https://docs.astral.sh/ruff/rules/redefined-loop-name/

[3] https://pylint.pycqa.org/en/latest/user_guide/messages/warni...


Because this isn't immutability. The goal is to have a way to define an object that will never change after initialisation, and JS's const isn't it.


Clearly that isn't the goal.


By "the goal", I mean TFA's, not JS's.


How isn't it transitive in C++? If the variable/reference is const, you can't modify fields, and you can only call const methods. What else do you need?


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

Search: