A few days ago, David Heinemeier Hansson announced that Turbo 8 is dropping TypeScript . I'm okay with that because I don't even know what Turbo 8 is. However, over the past few years, some frontend programmers have tried to sell me the idea that "TypeScript is useless, just use tests". I think people with such opinions either don't care about code quality or simply don't know what TypeScript is. Here, I will explain why you should use TypeScript.
  • @germanatlasEnglish
    23•10 months ago

    If you aren’t using [favourite programming language] you are a terrible dev who should feel bad!

  • macniel
    8•10 months ago

    uhm, you can get pretty great code quality in JavaScript. And you can also get pretty bad code quality in TypeScript (or any typed language). Its about your attitude toward it.

    I’m okay with that because I don’t even know what Turbo 8 is.

    are you though? You seem upset that people aren’t using TypeScript.

      • @Double_A@discuss.tchncs.de
        9•10 months ago

        The trivial problem here being knowing what kinda of parameter some random function somewhere in your code expects… And your code not randomly breaking in production when someone changes that function after you already used it, unless you wrote unit tests that literally test every single line of code.

        • Bipta
          2•10 months ago

          My sense is that this argument primarily holds for teams without thorough code reviews. For individuals or teams with good reviews, TypeScript adds little except for complex code or massive rewrites. I’m not saying it adds little in absolute terms, but that it adds little once you account for the overhead of using it.

          • @Double_A@discuss.tchncs.de
            5•10 months ago

            A quick check everytime when you build / package the code is surely more effective than a human code review.

            Also the difficulty of coding in a language where there isn’t any static type analysis still remains. How does it even work, do you have to do a manual text search everytime you change some existing function or class?

          • @alr@programming.dev
            1•10 months ago

            Nonsense. The compiler can handle type-checking far more quickly and acurately than any code reviewer. When I review code, I want to look at code structure, algorithms, data structures, interface design, contracts, logic, and style.

            I don’t want to go through your code line by line cross-referencing every function call to make sure you put the arguments in the right order and checking every member access for typos. That’s a waste of my time, and by extension, the company’s money.

          • @Double_A@discuss.tchncs.de
            2•10 months ago

            My point was that without a type system you need an impossible 100% code coverage, to be sure that you didn’t accidentally mess up some variable assignment or parameter somewhere, since you have nothings to easily and automatically catch those errors.

              • @Double_A@discuss.tchncs.de
                1•10 months ago

                I think we are actually saying the same thing though…? Tests should really only ensure functionality. It should be the language’s job to help you with obvious implementation errors (such as using a wrong value type).

  • @vzq
    1•10 months ago

    Damn right. I care about getting features in the hands of my users. If code quality helps with that, if type script helps with that, I’m all in favor.

    But the moment I care about code quality for its own sake you need to sack my ass like yesterday.