u/matzero

great project team alora! let's go

Wow

hi

Isn't the Reason fast pipe operator for Bucklescript the thin arrow (->) instead of the Ocaml |. ?

https://bucklescript.github.io/docs/en/fast-pipe.html

Great to hear that you guys finally reunited the undocumented babies with their parents... What’s that? dogs and cats?

So must we sterilize entire societies from any possible misunderstanding and guard against not having a unifying point view? Seems legit...

And they would be learning history from a toy manufacturer? Besides, as it was already cleverly pointed out in this thread, being more technologically advance does not imply being good or on the "right" side of history. The reason behind the banning of this toy is moronic.

"The fact that Revell's product’s description fails to mention the aircraft never existed is risky in that people who buy it might actually believe the Nazis possessed superior technologies, Wehner added." We are becoming a moronic species.

I'll have a coke, hold the ice.

This couldn't be further from the truth. When I started programming 25+ years ago you really needed to have a strong desired to learn because the road to programming was a painfully difficult one. One of the authors point is that the IDEs don't come installed anymore. Ha! It took an entire submanual of instructions to install the 5 diskettes that comprise the C compiler on my dads IBM/2. It was painful, information was hard to find and a lot was trial an error.

You should drop the mic and retire after that title.

God help us all, we’ll have to re learn C#

that sun.

Curious if it was based on a real character.

Halfway through the story I had to check if I was still on the sub /funny

And they say weed does not kill...

I don't have a specific case as I mentioned I have not used TS myself. I was just echoing some of the blogposts (albeit old) that were pointing to the typing system of TS as one that is not mature when compared to Flow.

Simply because the intention of the output is to be optimized transpiled code and not easy to maintain source code.

The output that Bucklescript (the compiler to JS) generates does a great job to produce optimized and readable javascript. You won't have trouble reading the code. However I would caution you against the proposed escape hatch strategy. The strategy that I would propose would be to leave the existing ReasonReact modules as they are and make them part of a "normal" Reason React JS project. There will be some rework but assuming that you create small modular components the switch should not be that bad.

a little late to the party, aren't we?