• 0 Posts
  • 24 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle

  • Not necessarily, depending on your situation you can type the JS code yourself.

    If the team making the JS code were using jsdoc then the Typescript compiler can recognize the comments and use it for type checking.

    In some instances the compiler can infer types from JS code to do some basic validation.

    Even if the external JS code is recognized as any, your own code that’s using it still has types, so it’s better than nothing.


  • Typescript is a language, Node is a platform and framework. You can use Typescript in your Node project, they’re not mutually exclusive.

    The way I see it Typescript is more popular than ever, almost all (popular) libraries come with types and every job offer I get they use Typescript.

    And with good reason, our team recently took over a small Javascript app and there are tons of bugs that would never have existed if they were using Typescript. Things like they refactored something but missed to update a reference, or misspelled a variable name, failed to provide a required parameter to a funcrion, referenced a field that existed in another config object etc.






  • Depends on what you already know.

    Functional languages like Haskell, Clojure or Erlang have a reputation of being hard to grasp.

    Rust’s borrow mechanics are hard for some people at first, especially because it’s very unique to the language.

    Javascript can be frustrating because it also has some rare features among popular languages, and uses the same keywords for different concepts. It’s not bad at all once you let go of your assumptions and dedicate the time to understand how it works under the hood.

    C++ is also notorious for being hard but I haven’t used it for a very long time so I can’t say anything about it.


  • alokir@lemmy.worldtoProgramming@programming.dev*Permanently Deleted*
    link
    fedilink
    arrow-up
    15
    arrow-down
    1
    ·
    edit-2
    1 year ago

    Probably Typescript, it has so many quality of life features that I miss when I’m using anything else. A close second is C#, Kotlin third.

    Rust when performance really matters.

    PowerShell when scripting and automating stuff. It’s common to hate it because “microsoft bad” but it’s very logical and it feels modern. Funnily enough, I’ve only used it on Mac and Linux.





  • The title makes it seem like it’s a wide spread thing in the industry but according to the video it’s 3 frameworks.

    Yeah, it’s additional work but I’ve found that really convoluted or complex type definitions usually mean you should consider refactoring. Of course this is a bit different when it comes to developing frameworks where you might want to support a bunch of different use cases.

    Maybe I’m biased because I’ve been using TS ever since it first came out.







  • Yeah but javascript has 473 popular frameworks and counting, and the churn is immense. Your codebase becomes out of date before you’ve finished writing it.

    That’s not really the case anymore, it was back at around 2015 for a few years when nodejs blew up and we realized that JS is capable of much more than we initially thought.

    We threw a thousand different things to the wall and a few frameworks stuck. Today the ecosystem is pretty stable, especially of you choose a popular framework like React or Angular.