deanmkenzey

This doesn't really seem to be specific to Javascript. A beginner in pretty much any language will have to go through these kind of issues.

And stop disallowing me to paste into password fields please. I use Keepass.. ..ever tried to enter by hand secure passwords like this: cw-ZY~!$m=#3RM4",Y9Mpcd\_!+z;FN]p

They actually trying to force me to use more insecure passwords.

> everyone who is in charge went to one

This is an illusion. There are of course people in charge with a degree, but most people I know who have a successful business don't have a degree. They even often dropped out of school because they were too ambitious for wasting their time there.

I do see heaps of people with a degree applying for shit jobs though. But that's what most people and parents don't want to hear of.

> I don't understand why use CoffeeScript instead of plain JavaScript

I didn't say I don't use plain JS today, I do! And indeed for the exact same reasons you mention :)

Not using 'any' is also perfectly fine, as you can with Javascript, Python, Ruby, etc.. And I guess that most companies just don't understand how I use Coffeescript.

Besides, I am not against others using Typescript, it's a fun experiment and a great opportunity for front-end developers to learn about static typing, enjoy it if you can! For me it unfortunately doesn't work, I've never gained from it because I generally don't have type issues. It's a pain in the ass that's constantly bugging me, pulling me out of the flow. It's a monster of a tool that tries to solve a problem I don't have.

You can easily test your Coffeescript code with a dynamic type checker and be perfectly type safe, even at runtime! Why for gods sake convert your code base to another language primarily for imaginary type safety?

But for some strange reason entire armies of developers move to Microsoft's Typescript, living their imaginary type save dream. Moving from a language as Coffeecript to Typescript is like dropping at least 25% of your productivity. Not only you'll have to write more code, which in itself increases the chance for bugs, but you'll also be fighting countless compiler issues, installing numerous @types modules, having intellectual discussions about types and whatsoever to make it 'kind of work'. Oh, and almost none of the TS code bases I've seen are without the 'any' keyword, which is actually an instant breach of your type safe haven. IMAO 'any' should never pass a code review in a Typescript project if you want to stay true to your religion. With such a strict regime, like you are forced to with real strictly typed languages, would completely eliminate TS. Without 'any' it's practically impossible to write a large code base with it.

I wrote numerous relatively bug free applications in Coffeescript, small and large as well. Just do good testing and you'll be fine, and as a bonus you'll have type safety at runtime! The mine field is not types IMAO, there is so much more to high quality code bases.