bajablast

Unrelated, but I often notice that lots of stack overflow and github issues get translated into chinese by someone. It's kinda interesting to see

Half of my personal projects are set as private because I am afraid the code is not worthy

Let me see. A lazy developer that only knows Ruby compiles the entire Ruby interpreter into WASM just to run Ruby. Then the user clicks a button that does an API fetch and the whole browser freezes while it waits for the response. . . . Yeah not happening. WASM was built and meant for high performance low level languages, there is no way in Ruby and Python will make the cut.

Python and Ruby will never compile to WASM since they would need to have the entire interpreter compiled with it and it would be extremely slow and bloated experience. Not to mention those languages do not have very good support for async operations and the lack of closures make it a terrible idea for the web.

I remember a while ago someone shared a SSR C implementation of React.

So I am guessing if a prop is `instanceof Promise` or some other constructor then it must trigger this response . . . is that correct?

honestly, who in their right mind would use the new Angular it's objectively worse in every area. In my experience only Angular development is maintaining Legacy code. Picking the new Angular would be insane it's slow, buggier, less flexible and more expensive to develop and find talent to build it's truly a lose-lose (unless you are a Angular team consultant that is)

Well actually a lot of things that say made in China are actually just assembled there. Like the essentially all of the core components of the iPhone are made in Japan/SK/Germany/US and then shipped to China to be put together.

I'd prefer to be a blacksmith personally

Drinking Beer takes the edge off the massive amounts of adderall pumping through my veins after working 15 hours straight

Whoa, I was just looking at some examples of this library and it seriously looks just like JS, only give away is the patten matching(which is a feature I wish JS had)

This is awesome! Thank you for writing this Buzzword/Jargon free tutorial it's so much more helpful to have things explained in terms of concepts the reader already knows.

Good stuff!

Personally I have learned that TDD and unit tests are only useful in OOP settings that have side effects and have mutated state overtime. But with a more FP approach all you need to do is verify the feature works since you know that state can't change the output.

I kind of also feel that TDD has a kind of cult like following, especially with the Rails crowd