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

Genuine question, why do you think this is so important to clarify?

Or, more crucially, do you think this statement has any predictive power? Would you, based on actual belief of this, have predicted that one of these "agents", left to run on its own would have done this? Because I'm calling bullshit if so.

Conversely, if you just model it like a person... people do this, people get jealous and upset, so when left to its own devices (which it was - which makes it extra weird to assert it "it just follows human commands" when we're discussing one that wasn't), you'd expect this to happen. It might not be a "person", but modelling it like one, or at least a facsimile of one, lets you predict reality with higher fidelity.


I'll be honest, as someone not familiar with Haskell, one of my main takeaways from this article is going down a rabbit hole of finding out how weird Haskell is.

The casualness at which the author states things like "of course, it's obvious to us that `Int -> Void` is impossible" makes me feel like I'm being xkcd 2501'd.


If you spend your life talking about bool having two values, and then need to act as if it has three or 256 values or whatever, that's where the weirdness lives.

In C, true doesn't necessarily equal true.

In Java (myBool != TRUE) does not imply that (myBool == FALSE).

Maybe you could do with some weirdness!

In Haskell: Bool has two members: True & False. (If it's True, it's True. If it's not True, it's False). Unit has one members: () Void has zero members.

To be fair I'm not sure why Void was raised as an example in the article, and I've never used it. I didn't turn up any useful-looking implementations on hoogle[1] either.

[1] https://hoogle.haskell.org/?hoogle=a+-%3E+Void&scope=set%3As...


What were you expecting to find? A function which returns an empty type will always diverge - ie there is no return of control, because that return would have a value that we've said never exists. In a systems language like Rust there are functions like this for example std::process::exit is a function which... well, hopefully it's obvious why that doesn't return. You could imagine that likewise if one day the Linux kernel's reboot routine was Rust, that too would never return.

> What were you expecting to find?

> functions like this for example std::process::exit


I'm not astonished this isn't provided that way in a language like Haskell but I suppose I would also not be surprised if it were provided.


It's not like sleeping pills at all actually. Sleeping pills have a huge dependence and tolerance factor. Antidepressants, generally, do not. Once you find one that works, they keep working effectively forever.

It's actually like statins. Ideally, a doctor will recommend diet changes in addition to the pills. However, relying on lifestyle interventions almost never is effective, And the more we learn about it, the more we realize that cholesterol is mostly genetic based rather than diet based anyway. So the most effective thing they can do is say "here, take these indefinitely". And thank God they do because it saves thousands of lives annually.

For many people with depression, a neurochemical imbalance is the root cause. Just like with statins, addressing it means taking some pills.


Probably gonna get buried at the bottom of this thread, but:

There's a good chance they just asked GPT5.2 for a name. I know for a fact that when some of the OpenAI models get stuck in the "weird" state associated with LLM psychosis, three of the things they really like talking about are spirals, fractals, and prisms. Presumably, there's some general bias toward those concepts in the weights.


I can't take this website seriously if it thinks that a difficult-to-reproduce syncing bug that has been around for a decade can be easily solved (and tested!) in a week and a half. That's the kind of delusional time estimate even my CS-illiterate boss wouldn't make.


And at the right time too. At almost every point before that, a gas powered engine was justified for duration and power, but the significant advances in both batteries and electric motors in the past 10-20 years have finally made them good enough that ICE tools are totally unjustified.


With all due respect, I hope you never touch the development of any piece of software any of my relatives or friends ever has to use.

Good UX is one of the most important-yet-underserved areas in the tech industry (the topic of this site), and this sort of attitude goes beyond being smug and naive to being actively harmful. Your goal should always be to make things easier and with as little friction as necessary.


> Advanced Passkey Features Required

> This application requires passkey with PRF extension support for secure encryption key storage. Your browser or device doesn't support these advanced features.

> Please use Chrome 116+, Firefox 139+, or Edge 141+ on a device with platform authentication (Face ID, Touch ID, Windows Hello, etc.).

(Running Chrome 143)

So... does this just not support desktops without overpriced webcams, or am I missing something?


Windows Hello should work fine just by PIN, it's the platform authentication part that's important, not the way you unlock it


Huh, unexpected is right. Bursts of heavy usage being better for longevity than steady usage goes against pretty much all conventional engineering wisdom.


Without knowing anything about it, I would posit that degradation accelerates the longer the battery is kept above some threshold temperature.

So, a heavy-burst+low results in a sudden high temperature then settling into a lower temperature. Steady flow keeps it at moderate temperature (above threshold) for a long time.


The paper notes there are multiple degradation mechanisms at play, and they are influenced by different factors, such as age, cycles, depth of discharge, state of charge at rest and so on. Hence the non-trivial response to more realistic discharge curves.

However they also note more material studies are needed to understand these mechanisms better.


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

Search: