3 ms·
Use events & async functions instead of frameworks Funny, the runtime required to support that async abstraction sure sounds like a thing that's responsible fo
by al2o3cr 9y ago
Use events & async functions instead of frameworks
Funny, the runtime required to support that async abstraction sure sounds like a thing that's responsible for running the system while you plug pieces of code into it at defined extension points. But that's unpossible, since we just learned that doing that is EVIL.
Snark aside, we've seen (more than once) in the Javascript space that "libraries not frameworks" can breed something even worse; ad-hoc copy-pasted cargo-cult setup files, pseudo-frameworks that use StackOverflow as source control.
- willtim 9y agoI would argue that Async in F# is just a library. Async tasks are essentially just functions that are composed using the more general "workflow" syntax. The final composite Async must be explicitly run with a choice of scheduler. I suspect Libraries-not-frameworks is only advice for those using sufficiently expressive languages. So probably not appropriate advice for JavaScript.
- chrisco255 9y agoI see no proof that JS frameworks lend themselves to less StackOverflow questions. Let's take React vs. Angular 2+ for example. Despite React.js having three times the popularity and being 4 years old at this point, it has 50,762 questions on SO [1] vs Angular 2+, which despite being less than one year old...has 63,932 questions on SO. [1] https://stackoverflow.com/questions/tagged/reactjs https://stackoverflow.com/questions/tagged/reactjs [2] https://stackoverflow.com/questions/tagged/angular https://stackoverflow.com/questions/tagged/angular