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.
“It never happened but they deserved it”. It’s a classic rhetoric of people who deny or white wash genocides.
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
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.
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.
I wonder how Svelte’s code is built to make this tradeoff worth it. I’ve been using TS for a long time and in every project the compilation part was the shortest task in the whole build process, especially when you compare it with bundling or running unit tests.
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?
I used it on a Mac and on Windows, for me it feels very modern when compared to bash (although I never was a bash expert).
However, the problem is that it’s not installed by default on Linux (at least on most distros as far as I know) and Mac, and Windows machines might have an outdated version which you’ll have to take into account.
So unfortunately it doesn’t meet OP’s criteria that it should “just work” without installing an interpreter.
Use both the latin x and the cyrillic х as variable names in the same scope. Your coworkers will thank you.
Is this really world news, tho?