• Ghoelian@piefed.social
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    2
    ·
    1 month ago

    I find that very hard to believe, if you’re truly just talking about typing. If this is true you’re using an awful language server / linter / whatever.

    Coding style is also a deterministic process, for which every widely used language has a linter or formatter or whatever. Also no LLMs needed.

    As a professional software developer of 8 years, I honestly have no idea what you’re talking about

    • auzy1@lemmy.world
      link
      fedilink
      arrow-up
      2
      arrow-down
      1
      ·
      1 month ago

      This is Lua code. LuaLS is basically the language server available.

      And sorry, I should have said “dynamically typed”. But, weak tables.

      There’s a lot of things that don’t get caught, such as concatenating a boolean which causes a lua error in our environment. LuaLS won’t catch that.

      Formatting isn’t a problem for us, but it does affect the kernel. But, the VSCode one we use does a lot of weird things honestly.

      • Ghoelian@piefed.social
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 month ago

        I am not familiar with Lua at all, but that does just sound like a bad language server. I still don’t think the solution is AI, it’s just making a better language server.

      • Ghoelian@piefed.social
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 month ago

        Well this is why you have different levels of warnings. Some are just flat out errors, some are strong warnings, others are weak warnings. Of course, at the end, the programmer has to be the one to decide to follow the language server’s diagnostics or not.

        As far as I understand, the whole draw of Rust is it’s very opinionated in its safety. If you don’t want that, Rust is just not for you.