• peoplebeproblems@midwest.socialEnglish
            1·
            20 days ago

            Sure! It doesn’t do anything yet, I just have a text file with how I’m intending to architect it.

            It quite literally started two four (edit: I can’t keep track of time) days ago.

            I’ll configure a repo, stick this in a file, and push it. I’ll reply with another comment so you (and others) can look it up.

            I’ve come up with some crazy stuff. Instead of something like “class” to indicate a class, it’s

            🏫 Followed by the emoji name of the class like 🖼️📁. So it will need to be able to handle operators in the name it’s amazingly gross! Properties and methods will also be emoji names, like to get the 🖼️📁 “File Name” it would be 📁💳.

            • jaybone@lemmy.world
              1·
              20 days ago

              I was kind of being sarcastic. I haven’t written a compiler since I rode my dinosaur to college. Still it’s a funny idea. Could probably do it in C using a bunch of pound defines.

              • peoplebeproblems@midwest.socialEnglish
                1·
                20 days ago

                I was thinking Rust, but that works too.

                Because then I could call the Language Spoons.

                It would as uncomfortable to use as it is to watch Rusty Spoons

  • Dyskolos@lemmy.zip
    1·
    20 days ago

    I really really dig the fuckaround/findout. It paints the try/catch with a more dreadful undertone and reeks of mystery.

    • merc@sh.itjust.works
      1·
      19 days ago

      Yeah, I love that one.

      “Try” is too hopeful. “fuck_around” makes it clear that you know what you’re doing is dangerous but you’re going to do it anyhow. I know that in some languages wrapping a lot of code in exception blocks is the norm, but I don’t like that. I think it should be something you only use rarely, and when you do it’s because you know you’re doing something that’s not safe in some way.

      “Catch” has never satisfied me. I mean, I know what it does, but it doesn’t seem to relate to “try”. Really, if “try” doesn’t succeed, the corresponding block should be “fail”. But, then you’d have the confusion of a block named “fail”, which isn’t ideal. But “find_out” pairs perfectly with “fuck_around” and makes it clear that if you got there it’s because something went wrong.

      I also like “yeet”. Partly it’s fun for comedic value. But, it’s also good because “throw” feels like a casual game of catch in the park. “Yeet” feels more like it’s out of control, if you hit a “throw” your code isn’t carefully handing off its state, it’s hitting the eject button and hoping for the best. You hope there’s an exception handler higher up the stack that will do the right thing, but it also might just bubble all the way up to the top and spit out a nasty exception for the user.

    • jballs@sh.itjust.worksEnglish
      1·
      20 days ago

      The whole thing was pretty damn good all the way through. The only thing that had me wondering was

      Tea

      Until it got to

      SpillTea

      Well played.

    • Demigodrick@lemmy.zip
      2·
      20 days ago
      HAI 1.2
CAN HAS STDIO?
IM IN YR LOOP UPPIN YR VAR TIL BOTH SAEM VAR AN 10
    VISIBLE SUM OF VAR AN 1
IM OUTTA YR LOOP
KTHXBYE

      A perfectly reasonable language. None of this Gen Z rubbish.

      Something something better times. Shakes stick at sky.