Yes, at this point the choice is who gets to spy on you.

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.

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.

The EU introduced a limitation to how much power electric devices can consume in off or standby mode.

0.5 watt normally, 1 watt if they have a status display and 2-8 watts if they’re connected to a network.

On a yearly basis this saves as much electricity as one of the member states (Romania) used in a year.

My point is that small things add up to huge numbers.

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.