• 1 Post
  • 11 Comments
Joined 2 months ago
cake
Cake day: August 9th, 2026

help-circle







  • You avoid function coloring. It’s a function parameter.

    I have a problem with this wording, because function coloring is isomorphic to function parameters. It is fundamentally about how if you need thing X as a parameter at the bottom of the callstack, it will spread upwards. It doesn’t really matter whether the parameter is implicit or not. And it also goes for return types: if you introduce a Result at the bottom of your previously-infallible stack, it will start to spread upwards, unless you bite the bullet and unwrap it. Which will then unwind the stack so philisiphically it still does spread upwards, except implicitly and invisibly.


    score 1 · canonical




  • If you’ve paid attention to the HuggingFace hacking scandal and to what’s going on in mathematics, we’re well past the “stochastic parrot”, and have entered a world in which a sufficient amount of raw capital and verifiable constraints can solve complex problems.

    Unconvincing. An unsupervised swarm of stochastic parrots told to emulate hacking and piped directly to shell managed to eventually exploit something. Like, yes, it can do harm, but that has absolutely nothing to do with intelligence. The parrot may well be able to do your job, because you don’t really need to think to implement yet another CRUD service. You may take psychic damage from being forced realize that your job was one of the bullshit ones, but it would’ve still been one even without the parrot.

    To put it in maximally edgy terms, there is a moral imperative to firebomb something, where datacenter ∈ something, but not for the specific purpose of slowing AI.


    score 3 · canonical