Message from JavaScript discussions
December 2018
— You then run that code
Hz pushes the code to a higher abstraction level at which it can be interrupted or preempted, that is all
— So you tell me, after you google "use cases for interrupts", what the re-usability is
— The problem is people who write JS are not familiar with the use cases
— For me it's easy to understand
— Because i did threading a lot in the past
— But for web devs maybe difficult
— That's why we are doing evangelization
— It's hard to convince someone hz is useful determin1st you are helping me actually, because I need to talk to more people who have never heard of such use cases
— 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
— 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