BatmanAoD

joined 2 years ago
[–] BatmanAoD@programming.dev 2 points 2 days ago

One list, two list, red list, blue list

(I genuinely thought that was where you were going with that for a line or two)

[–] BatmanAoD@programming.dev 10 points 3 weeks ago

Agile Meridian / Post Manager

[–] BatmanAoD@programming.dev 9 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

Thanks for sharing this! I really think that when people see LLM failures and say that such failures demonstrate how fundamentally different LLMs are from human cognition, they tend to overlook how humans actually do exhibit remarkably similar failures modes. Obviously dementia isn't really analogous to generating text while lacking the ability to "see" a rendering based on that text. But it's still pretty interesting that whatever feedback loops did get corrupted in these patients led to such a variety of failure modes.

As an example of what I'm talking about, I appreciated and generally agreed with this recent Octomind post, but I disagree with the list of problems that "wouldn’t trip up a human dev"; these are all things I've seen real humans do, or could imagine a human doing.

[–] BatmanAoD@programming.dev 3 points 1 month ago

That is a pretty lame "poisoning".

[–] BatmanAoD@programming.dev 1 points 1 month ago

This also makes me realize that I sometimes enunciate "the" unvoiced.

[–] BatmanAoD@programming.dev 45 points 1 month ago (3 children)

Well now you've seen it elsewhere, too.

[–] BatmanAoD@programming.dev 5 points 1 month ago

distributing relay knowledge among chatters (TBD)

This is the core reason that centralization is currently necessary. So admitting that it's an unsolved problem for a federated alternative is basically reinforcing Signal's point.

[–] BatmanAoD@programming.dev 4 points 1 month ago

That's because you haven't unlearned it yet

[–] BatmanAoD@programming.dev 14 points 1 month ago

Two, arguably: one with Apple and one with upstream Linux.

[–] BatmanAoD@programming.dev 9 points 1 month ago (1 children)

String escaping sucks in bash and other posix-style shells too, though.

[–] BatmanAoD@programming.dev 4 points 2 months ago

But that's not actually true in general; there is a default branch concept in forges, and an integration and/or release branch in most recommended workflows. That's the trunk.

[–] BatmanAoD@programming.dev 1 points 2 months ago

Fair, but it's one that the typical tools for finding bugs, tests and static analysis, cannot actually help with.

65
submitted 11 months ago* (last edited 11 months ago) by BatmanAoD@programming.dev to c/programmer_humor@programming.dev
30
submitted 2 years ago* (last edited 2 years ago) by BatmanAoD@programming.dev to c/rust@programming.dev
 

Almost five years ago, Saoirse "boats" wrote "Notes on a smaller Rust", and a year after that, revisited the idea.

The basic idea is a language that is highly inspired by Rust but doesn't have the strict constraint of being a "systems" language in the vein of C and C++; in particular, it can have a nontrivial (or "thick") runtime and doesn't need to limit itself to "zero-cost" abstractions.

What languages are being designed that fit this description? I've seen a few scripting languages written in Rust on GitHub, but none of them have been very active. I also recently learned about Hylo, which does have some ideas that I think are promising, but it seems too syntactically alien to really be a "smaller Rust."

Edit to add: I think Graydon Hoare's post about language design choices he would have preferred for Rust also sheds some light on the kind of things a hypothetical "Rust-like but not Rust" language could do differently: https://graydon2.dreamwidth.org/307291.html

view more: next ›