Dr_tldr

It's the classic "not invented here" syndrome, but on the level of languages. It's not enough to be able to have strong types in Javascript, they want people to stop writing Javascript, scrap the entire ecosystem, create all new browsers on every platform, and only write in their strongly typed language that's just as flawed as Javascript.

JS runs natively on the web, it embraces multiple paradigms, it has a huge community, and you can get a job in almost any city on earth if you know how to use it. Haskell may be "better" as a language, (just as Esperanto may be superior to English) but if you want the widest range of opportunities in your life and not just in your language, Javascript/English beats Haskell/Esperanto.

Why not help bring some of Haskell's concepts to a more relevant language instead of bemoaning the entirely rational decisions made by millions of junior and senior developers?

Edit: the rabid insularity of the Haskell community definitely doesn't help. The Python community was dissatisfied with JS and created Coffeescript, and as of ES6 now everyone can enjoy the fat arrow syntax. Less pleasantly, the Java community got class syntax added to ES6, but at least they're trying to contribute. I'm sure Haskell has plenty of really cool things to bring to the table, but I've never heard of any of them, because all the Haskell community wants do is talk about how JavaScript sucks instead of embracing the functional side of it.

True, but one way to push them to fix their engine and make it better is for them to feel pressure to not be left behind. People are going to code in the way that makes sense for them, and if one mainstream-enough implementation works way better than another, eventually people are going to stop bothering with it.

Safari has become the new IE in a lot of ways, and larger and larger websites/apps are starting to only target Firefox and Chrome, leaving Apple with the options to either give up or rejoin the mainstream.

You rarely read HN, then.

For most adults/businesses in developed countries, mobile is a secondary device, while PCs run everything from AAA games to filing systems to interfaces for medical equipment.

It's definitely not standard, the almost universal standard is using ES6 import/export. There are several other suspicious patterns here, I definitely wouldn't take these as canonical, or even best practices.

I think this is great advice for a beginner on their first project. Using React's localState for everything is a huge anti-pattern, but Redux adds cognitive overhead and boilerplate.

Later, when you do a real project, Redux makes debugging and state consistency about 10 times easier, especially on a team or coordinating between multiple teams.

So this is either a glorified bucket shop or yet another company with the brilliant idea of setting up an unregulated secondary market selling an incredibly wide variety of different ownership instruments that were never intended to be sold.

IANAL, but if I was their counsel, I would definitely advise them to keep paying me a lot of money for a 10% chance it somehow works out with the regulators.

Uh, my whole point is that JS isn't that hard to learn, so why invest so much time trying to make it look like Java and write worse code in the process?

Thanks for helping my argument, I'm glad we agree that you're a bad engineer.

Sorry, but I think most people don't consider a badly designed service that disenfranchises customers arbitrarily and coincidentally saves HTC a bunch of money to be a "weird quirk."

Plenty of other companies are able to both honor their agreements and prevent fraud, why can't HTC?

Is there a non-haskell resource on monads you could recommend? Anything that starts with "first, learn haskell" is probably not the easiest way, assertions from people who already know haskell notwithstanding.

So it seems like the logical thing to do would be to create a study with better construct validity since it seems you don't think my evidence is any good and you definitely don't have any of your own.

If we're both just throwing around opinions this is no different than arguing tabs vs spaces. I've noticed that Typescript tends to be embraced by teams with lots of subpar enterprise Java developers with limited knowledge of Javascript. The same is also true of Angular, so it's a good fit here, but it's more for mitigating a lack of personal knowledge and organization standards than a general benefit.

> Also, its very strange to see these concepts illustrated with Javascript. I imagine thats something like trying to learn Chinese using the roman alphabet. Not that it can't be done, but a lot of important details are necessarily missing.

I think you're being sincere in expressing a common attitude within the Lisp/FP community, but it's an unfortunately limiting attitude. It would appear strange to an ancient Sumerian to see the Epic of Gilgamesh translated into English, but the translation is far more accessible and thus far more influential than the original.

I'm a front-end dev and I got into Clojure and Elm because of some books/libraries for functional programming in Javascript. It's doubtful I would've ever had enough interest to learn if no one in those communities made an effort to translate some of their concepts into a language that I already use.