607 karma · joined November 18, 2007
Thanks for posting this.
Microtik can be great value if you're willing to do lots of vendor QA (for other values of vendor) in your lab before going in to production. Most of the problems are to do with community: the docs are an unloved wiki which only staff can modify; release management, QA and bug tracking are third rate; and the forum is a passive-aggressive Engrish ghetto with poor moderation. But config management, CLI and Winbox are still better than straight Linux, and boards start at $40 which can make it worth it.
ServiceWorker (WIP) will do this. Its a WebWorker proxy in the browser's request/response pipeline for a particular origin, with a new cache API built on local storage.
It can process page requests and responses with similar semantics to what a WSGI/Rack/MVC controller normally does on the server. It does away with bullshit 'offline mode' divining and encourages apps to work 'offline first'. https://github.com/slightlyoff/ServiceWorker/blob/master/exp...
The polyfill is actually a node.js headless implementation, which makes this look more and more like an isomorphic controller API. https://github.com/phuu/ServiceWorker-Polyfill
Jake Archibald's talk at Chrome Dev Summit, December. https://www.youtube.com/watch?v=Z7sRMg0f5Hk
Chromium bug. https://code.google.com/p/chromium/issues/detail?id=285976
Your single example sells this more effectively than the entire OP. cf. http://bost.ocks.org/mike/example/
People who want IPv6, DTLS, decent cli tools (gnutls-cli), pkcs11.
"data centers connected to the antennas perform fast mathematical calculations to create a unique and coherent wireless signal for every person on the network" -OP
These are quite readable; worth a look. Thank you, ashwinl.
It's a REPL in the sense that when you click Run, the value of the current evaluation is used (Looped) as the input for the next expression, but this stretches the common understanding, and naming it this way fails to communicate.
The full page transition when you click Run loses the implicit history from a teletype or terminal scrollback. A shell works because you can see two or more values were visible at the same time. The second pane could then show the code of the currently selected value. You could even show the diff/patch between the values as well.
The 'Run' text should look like a button rather than a label, and be moved to the right. It might work even better to just evaluate the code on a timeout without an explicit gesture.
Edited: for more positive feedback.