Re:Command line interfaces are reified UIs
by b0rsuk on Friday November 03, 2017 @07:45PM
(#15623015)
I think if you use JS your website has broken history by default and you need to go an extra mile (or use a nice framework) to remedy this. And there are things like infinite scrolling pages. And then you find yourself arguing with the developer why it should be fixed ("Yeah ? But nobody uses history anyway.")
Re:Command line interfaces are reified UIs
by firethief on Friday November 03, 2017 @08:57PM
(#15623251)
If you use C your program has broken history by default and you need to go an extra mile (or use a nice framework) to remedy this. I guess the difference is that in C world, we've more or less standardised on a few nice frameworks (Qt, GTK, etc).
Re:Command line interfaces are reified UIs
by pcmaffey on Friday November 03, 2017 @05:21PM
(#15622279)
Unless you sync app state with the router, then you cannot "Enter a command / url" => "Output a state / action".
Re:Command line interfaces are reified UIs
by horsawlarway on Saturday November 04, 2017 @04:59PM
(#15626875)
I'm sorry, but that's incorrect.
It's not something most users do, so if your argument is "Reification is not on by default for all users" then sure.
But that's a meaningless statement. Most users don't want that ability, or aren't willing to spend the 10 minutes it takes to configure.
Otherwise, you absolutely can enter commands and output state: https://sites.google.com/a/chromium.org/chromedriver/downloa...
Further, there are a HOST of tools that make this process very easy, complete with replay solutions, detailed logging, real time monitoring and all sorts of other fantastic, modern tools.
Just because you choose not to use them doesn't mean they don't exist. Sorry your understanding of web dev is out of date...
There are several ways to capture that state, and the nice thing is that the browser allows sites to either opt in or out depending on their requirements.
See: Insights, FullStory, or any other event hooking library.
We can also play back those actions using the very nice WebDriver apis available in modern browsers.
There is zero reason to assume that we've lost reification simply because we've moved away from an approach that requires at least one RTT in latency before updating what the user sees.