@Voxera nice I like to read what you write. I also play with my code until it satisfaction my ability to read it easily.

I started thinking of back using `function` statement as a default for call back. because even for writes it make more sense to declare myself that i'm going to write function now and then thinking about the argument . then write variables and then say it will be arguments for next expression

And this guy know me so wall:
https://davidwalsh.name/i-dont-hate...

your are not alone. i think they are greet in the start but overuse of them everywhere even on super long function kill the readability . because i can't tell anymore where all that functions started.
they look just as a declaration of const/let/var when i scroll fast.

and even on short arrow if i not expect function as parameter i need to read the expression three times to tokened it out and beak it into a meaningful expression

It call `casting` and it consider as a good idea in c++

first of all , the community of JavaScript live just fine before 1.5-2 years. aka before Typescript got common aka before angular make everyone use it.

so if you like to learn how to program good quality code that explaining himself just open some random high rank project in GitHub and start reading . I'm sure you finish it quickly, and probably will learn something

And I don't thinks the dashboard applications that everyone made today are more complex dashboard applications that we build two years ago.

and line about me : i'm start coding before 20 years from 16 age . learn and write pascal, c, c++, assembly, java, and before 10 years I landed in JavaScript for good. so I consider my self as expert in that area and really not a guest like all java programmers who just discovered how wonderful JS is. and come to contaminate it with their cumbersome habits.

I am web frontend expert and I am also feel that whole world of front end going loony . there are some good idea else and there but the whole crap of TypeScript ( aka coffeeScript ) and compiling fucking javascript ( high abstract language if you remember ) make me crazy

That it the common error on production ??

and when the type can be `config object` `number` or `string` how can it be possible to mistake.

or all the people you now involved with a lot of intense use of custom classes .

and if that is the case maybe that is the problem .

It is a rumor that all people who do not know better repeat .

The propaganda of microsot interests, whose IDE can not handle JS without Types. and they try... ho they try . so they decide a new strategic : if they can't write interpreter that understand JS let's teach the people how explain the JS to the machine. and that is absolutely for machine because it much easier to read JS without types. much easier

I and all serious JS programmers do not remember mistake in Typing on production.

that kinds or error JUST DOES'T HAPPEN

Dynamic types are evolution over types,not the opposite. so dynamic Types are a POWER not weakens

@beegC0de The problem begins to rise when they start invites new types, probably not as super-quality engineering as there is in js naturally. Types I need to check learn and understand. say each class in OOP.

So almost from beginning