Login
You're viewing the functional.cafe public feed.
  • Nov 10, 2026, 11:32 PM

    @argv_minus_one @liberty @aparrish

    Writing safe accessible languages is hard, but we should keep trying.

    I once taught a kid at my local library how to code using Scratch.

    Within about 20 minutes, he re-invented fork-bombing. (Future Cybersecurity engineer, I imagine.)

    The Scratch engine handled his fork bomb perfectly - filling his screen with the expected randomized bat animations, while quietly cleaning up extras when there were too many for thre processor to handle.

    Building good accessible languages is certainly a challenge, but I believe it is achievable. And it's so important to help us teach fork bombing to our next generation of Cybersecurity engineers.

    💬 1🔄 0⭐ 2

Replies

  • Nov 11, 2026, 4:42 AM

    @EdTheDev

    Writing a safe accessible language seems pretty impossible, though, because to do so would be to reconcile two mutually-opposing forces.

    Safety requires a sophisticated type system, with generics and bounds and all that. Rust has that, as do some other languages, but such languages are famously non-simple.

    A dynamically-typed language is simpler, but then you lose type safety, and have to keep track of types in your head, which is easy to screw up.

    @liberty @aparrish

    💬 1🔄 0⭐ 2
  • 💬 1🔄 0⭐ 2
  • 💬 0🔄 0⭐ 0
  • Nov 11, 2026, 5:24 AM

    @argv_minus_one @liberty @aparrish

    As I mentioned, the solution is animated bats.

    (Sorry, I'm not treally trying to argue, just trying to get a laugh.)

    I find that new programmers that I teach need accessible languages, rather than safe ones, or even fast or powerful ones.

    They need languages with great tutorials, interesting uses, and high quality error messages.

    💬 0🔄 0⭐ 3