Message from JavaScript discussions

December 2018

— I have to teach someone what some computer science concepts are before I can describe hz, because I don't know how to describe it as a product, only as a system

Message permanent page


The concerns of an average front-end JS dev or even back-end are very high level and abstract, so they only know of the event loop and how to architecture programs to run within it, and my #1 struggle has been trying to figure out how to say "but this is different from that"

— I didnt even know beyond that, until I looked at Java, Crystal, Golang, Erlang, etc... and saw how differently their programs were architected, and the problems they faces VS the lack of the same problems JS faced

Message permanent page

— Callback hell is eliminated completely by hz when the callback is due to async

— And, really it's not hz, it's the low level concept of concurrency... so all the langs I looked at which supported the same kind of concurrency were more or less devoid of most forms of callback hell

Message permanent page

— As an example

— Are you guys some kind of united gang😅

— I spam the ever loving hell out of them constantly lol

— I brainwashed them

— Is it working on you? XD

— Also dependency. if i take, for example, jquery-ui slider and drag one handle to another and see how it overlaps, i think, it's not good for me (it lacks an option to stop the drag when handles meet). i throw it away, take another, or implement my own manually. With Herz, i wont be able to throw it, if im going to compile my code with Herz, then i should follow the usage rules, right?

Message permanent page

— I'm not sure how to understand this use case or how hz would help