The same reason people drive their car to buy groceries.
You bought it for something where it was the only option, driving 30km to work everyday. But ever since you got it, the trip to the super market is kinda too hot in the summer and too cold in the winter and what if you spontaneously need to buy more than expected?
People learn it for front end dev, and then they use what they know for back end too.
https://programming.dev/post/7789832
How does people manage to work with that language?
by not ever using == and !=, but only === and !==
Because in reality you’re not doing stupid stuff like that in the image. And using Typescript definitely helps.
However I’m always annoyed that the month parameter when constructing a date object is 0 based. So 1st of Jan is
That’s nothing. The ‘tm’ type in the C standard library also starts months at 0. But the year 0 is the actually the year 1900.
So 1. january 2024 would be
tm date{ .tm_mday=1, .tm_mon=0, .tm_year=124 };.Looks confusing at first, but I found it nice for accessing a month array.
const months = ["Jan", "Feb", ...]; months[0] === "Jan"; const label = months[date.getMonth()];Typescript :)
By banishing the bad part of the language with linter.
For instance, standard eslint preset has rules that enforce usage of
===, https://eslint.org/docs/latest/rules/eqeqeqThese rules often come with project starter template
And typescript is basically just a linter on steroids
almost forced to for web front end. why you would use it anywhere else, however, i will never know
The same reason people drive their car to buy groceries.
You bought it for something where it was the only option, driving 30km to work everyday. But ever since you got it, the trip to the super market is kinda too hot in the summer and too cold in the winter and what if you spontaneously need to buy more than expected?
People learn it for front end dev, and then they use what they know for back end too.
Ikr? English is hard /s