Also C# (or should I say the .net framework) is now cross platform, which wasn’t really the case when I first saw this meme.

This joke made sense when instead of .net you could only use Mono with C# on other platforms, which wasn’t very good at the time.

Yes and no. They serve roughly the same purpose.

I actually hated Powershell until I was forced to work on some automation scripts with it and realized that it’s actually pretty cool.

Bash is good for quickly doing something in the terminal but for longer script files I prefer PS now. It feels much more modern and has a less janky syntax.

Funnily enough the reason I had to use it was to make my scripts cross platform between osx, linux and windows.

that’s not even a joke, I’m using intellij community as a merge and diff tool exclusively. it doesn’t support the language I want but even without it it’s better then anything else.

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)))))))))

Or bytecode that the runtime will interpret

I might be in the minority but I prefer to do it like this: Boolean(m).

It’s the same thing but less cool. On the flip side it’s easier to read when you have a line full of operators.

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.

This looks kind of like the Imperial City from Oblivion, which has a huge tower in the middle called White Gold Tower.

What happened to the White Gold Tower?

Use both the latin x and the cyrillic х as variable names in the same scope. Your coworkers will thank you.

As far as I’ve experienced you need really good quality headphones in order to enjoy Tidal. Mine is on the high end of mid tier and I couldn’t tell the difference in quality when I asked my wife to test me. I use Youtube Music because it’s pretty much the same as Spotify plus no ads on regular Youtube.

I agree, I also prefer Typescript, but I don’t think I’ve ever seen a meme about JS not having strongly typed variables.

They either don’t center around any specific problem or things that are also mostly true about TS.

I’d bet that most people who think this way either haven’t used it in the last 10 years or they only know it from the memes.

One of my favorite languages, it’s everything that’s good about Javascript plus the one thing that’s missing: types.

It seems like you were right, it was the theme that I chose that didn’t support showing the long press symbols, even though I enabled them in the settings.

Regarding the voice to text, for me it just opens Google’s voice input, it doesn’t seem like it has its own built in VTT.

I tried SwiftKey for about a week or so a month ago but I’m too used to GBoard to make the switch.

What I like about GB that SK doesn’t have or is too different:

• speech to text integrated into the keyboard. The Bing app is probably the best at this, especially for my non-native English accent, too bad SK doesn’t have its own implementation
• I can set up the keys to show their long press symbols
• the colon character is at an awkward place for my finger to reach
• GB’s swipe function can figure out much more easily what language I wanted to type in
• SK shows every possible accented version of the character that I long pressed on, and the one that I wanted was usually at an awkward place to reach. GB on the other hand sorts those of my native language right next to the original character, and only offers a few that I never use.

It took a few seconds to read them and about a minute to search for the package on npm, another minute to come back to Lemmy and type out my comment.

All in all, not the worst case of me wasting my time.