Message from JavaScript discussions
December 2018
— I studied them closely and their status, how much progress they made, what their technical debt was
My original vision of hz was very very large because I wanted to do what they were doing, but it took me 4 years of research to reduce the size and scope down to a singular point, becoming sure of purpose and having a clear vision to proceed coding it very carefully to avoid any kind of over-engineering whatsoever
— Because of this, the core concurrency is ubiquitous, can be used for literally any use-case, and has no limits
— It can also be used with all existing interfaces transparently, without changing them
— Take some use-case and make a test, why not
— I am to demonstrate it, so that people may understand, but it is not needed to prove the ubiquity of it
— One must only simply look to almost any other popular programming language to discover the ubiquity of concurrency
— This is a range slider prototype ive been making for jquery-ui... generally scrollbar is a range-slider
— As an example, my original vision was not coroutines, but rather Linux-like Green threads, and it just so happens that coroutines pave the way for true preemptively scheduled Green threads in JS, impossible until now no matter where you look
— To compare your existing interfaces and environment to it is naive, but not unexpected as almost all other developers immediately do this and prefer to stay locked inside their padded cell
— Someone said to me, "Why can't I use promises?", and it was after I said Promises are not needed because hz makes them obsolete, but their perception of this news was negative and uncomfortable, as I presented entirely new ways of programming they were not familiar with or prepared to understand
— Maybe they are not locked, just done it *manually* and okay with the result