![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/8nN0qtLEOJ.png)
I was seriously considering buying the game on release but after 8 hours of not having fun paying it I’m glad I had GamePass to try it on first.
I was seriously considering buying the game on release but after 8 hours of not having fun paying it I’m glad I had GamePass to try it on first.
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.
It’s a good way to get started, and then incrementally type as much as you can, preferably everything.
Later on, or if you start a new project with TypeScript, it’s a good idea to turn on noImplicitAny
and only allow explicit any
in very specific framework level code, unit tests or if you interface with an untyped framework.
The hassle really pays off later.
I don’t either)))))))))
JavaScript: i know it was easy to write it like this but you should index your citations next time
Typescript: I meant properly, not on your scratch sheet
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.
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.
I was working on an enterprise web application, there was a legacy system that everyone hated and we replaced it with a more modern one.
We got a ticket from our PO to introduce a 30 sec delay to one of our buttons. It sounded insane, but he explained that L1 support got too many calls and emails where users thought said button was broken.
It wasn’t, they were just used to having to wait up to 5 minutes for it to finish doing its thing, so they didn’t notice when it did it instantly.
We gradually removed that delay, 10 seconds each month, and our users were very happy.
Ads are indeed getting smarter every day