Message from JavaScript discussions

September 2020

— If it's not taking user input, it's not a controller anymore

— 

I guess you could make the argument that all routes take HTTP requests which come from a *user*, but the problem there is that the router is *also* the view

— Except for that it doesn't really get updated when the model changes

— Which is what a view is supposed to do

— Ye, and how do you call it, if it's not user input🤨 any input, imo, input that is generated by the "real" world

Message permanent page

— ERR_CONNECTION_RESET on my side🤤

— According to previous problems, it's some sloppy browser

— Hooky🤤

— Or, all or nothing strategy🤤

— That's not user input though

— Could be input from another server, so "controller" is the wrong word

— I'm skeptical about using it to only build some sloppy frame helper