8,390 karma · joined September 5, 2010
http://chris-granger.com http://www.witheve.com http://www.lighttable.com
I code, Robert makes sure I'm just coding.
For example, in the video it was predetermined exactly what was going to be moving and where it was going to go to. From my observations, these sorts of large scale changes are rarely handled so easily. Context helps people map things cleanly, and the contextual change of zooming in and out forces you to constantly rebuild that map. It's an issue I've seen over and over again with any zoom-oriented interface.
Regardless, this is cool work. We need new and interesting interfaces for code - I'm hoping to show some fun things myself at the Live Programming Workshop [1] at ICSE[2].
[1]: http://liveprogramming.github.com/2013/ [2]: http://2013.icse-conferences.org/
(ns foo.bar)
Since you don't have one, clojure.core isn't available and it freaks out. I'll look into setting the default namespace of file so that it's a little nicer for newcomers :)Not sure about the ctrl+shift+enter not working, I'll see if I can come up with a repro. Keys are delimited with -, so Ctrl-Shift-Enter
For (doc ..) take a look at the bottom console, click the little arrow which should be blue when there's new content in there. All prints go to that console.
Thanks for the report! :)
[1]: https://github.com/Kodowa/Light-Table-Playground/issues/281
EDIT: tracking in this issue: https://github.com/Kodowa/Light-Table-Playground/issues/271
Now that we have an experience we plan to stick with more documentation and getting started content will be coming in the next few days. :)
EDIT: I didn't think about SVN, we do filter out Git, but this should just be customizable. Added an issue for it [1].
[1]: https://github.com/Kodowa/Light-Table-Playground/issues/266
[1]: https://github.com/Kodowa/Light-Table-Playground/issues
We use tabs as a simple way of wrapping up a context. In the future they will include all sorts of neat things - and they aren't limited in any way. If we want, we can drop an infinite canvas into one, or a codex (a document made of many parts of different files). So yes, right now we wanted something beautiful and efficient to use while live coding, but as I said in my bit about 0.4.0, the really interesting semantic-oriented stuff (functions and the like) is what's next!
With that said, in your example, you could do one and two together and the response doesn't need to wait on the completion of #3. So it's one network roundtrip, which I would imagine is a tiny fraction of what they're having to do already. It is certainly another moving piece, but again my argument is that they have to have a solution and this doesn't seem infeasible.
That being said, health checks are nice for other reasons and could be used outside of the routing layer (which you need to sail along as quickly as possible).
- request comes in and gets routed to the dyno with the lowest count. Inc the count.
- response goes out. Dec the counter.
Since they control the flow both in and out, this requires at most a sorted collection of counters and would solve the problem at a "practical" level. Is it possible to still end up with one request that backs up another one or two? Sure. Is it likely? No. While this isn't as ideal as true intelligent routing, I think it's likely the best solution in a scenario where they have incomplete information about what a random process on a dyno can reliably handle (which is the case on the cedar stack).
Alternatively, they could just add some configuration that allows you to set the request density and then you could bring intelligent routing back. The couple of milliseconds that lookup/comparison would take is far better than the scenario they're in now.
EDIT: I realized my comment could be read as though I'm suggesting this naive solution is "easy". At scale it certainly isn't, but I do believe it's possible and as this is their business, that's not a valid reason to do what they are.