HNHacker News
TopNewBestAskShowJobs

ibdknox

8,390 karma · joined September 5, 2010

Previously co-founder of Eve and Light Table. YC alum. Ex-Microsoft Program Manager for C# and VB in Visual Studio and head of product at Relational AI.

http://chris-granger.com http://www.witheve.com http://www.lighttable.com

submissionscomments
ibdknox··on Rap Genius (YC S11) responds to Heroku’s call for ‘respect’
What did they fix? They've side stepped any real solution for the root problem. As such, the only thing they've "fixed" is new relic, by making it report what is actually happening.
ibdknox··on A new Light Table experience
Currently 2: Robert and I.

I code, Robert makes sure I'm just coding.

ibdknox··on Show HN: Tiled Text – a Different Approach to Editing Text
This is really neat, great work! I wonder, do people perform the kind of edits that this makes efficient very often?

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/

ibdknox··on A new Light Table experience
You have to toggle Vim mode - then it is modal.
ibdknox··on A new Light Table experience
rumor has it I'll be keynoting :)
ibdknox··on A new Light Table experience
"eval" in the CSS case just means injected into the context. Nothing gets computed :)
ibdknox··on A new Light Table experience
eval is only for Clojure, ClojureScript, Javascript, and CSS right now
ibdknox··on A new Light Table experience
All files in Clojure require a namespace form at the top:

   (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 :)
ibdknox··on A new Light Table experience
it actually uses neither, and doesn't rely on any specific implementation. You could fairly easily wrap a swank client to make it work, or an nrepl one (which is something we'll probably get to soon). One of the nice things about the way we architected it is that there are very few assumptions when it comes to "clients" and that will allow a ton of freedom in using established stuff when it exists.
ibdknox··on A new Light Table experience
Created an issue for the first [1]

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

ibdknox··on A new Light Table experience
I'm curious as well, since most of the programmers I've met prefers a dark theme. :)
ibdknox··on A new Light Table experience
it's not currently configurable, but I agree that the highlighting should be more like that. Filed an issue to track it: https://github.com/Kodowa/Light-Table-Playground/issues/277
ibdknox··on A new Light Table experience
Check out my previous post: http://www.chris-granger.com/2013/01/24/the-ide-as-data/
ibdknox··on A new Light Table experience
in the command bar, type "skin" and press enter. You can change it to a light skin. :) You can also change the editor theme, by using the "change editor theme" command.
ibdknox··on A new Light Table experience
10.8? and all you're doing is scrolling quickly? If you close the app and bring it back up, it still does it?

EDIT: tracking in this issue: https://github.com/Kodowa/Light-Table-Playground/issues/271

ibdknox··on A new Light Table experience
fixed, sorry about that.
ibdknox··on A new Light Table experience
This is OSX's gatekeeper going crazy because our codesign included the icns file (which then got compressed and no longer verifies). I'm uploading a new package right now. As a workaround you can go to security in system settings, set it to allow anything to run, open LightTable.app, close it and then re-enable the old gatekeeper setting. LT will open fine thereafter. Or you can just redownload in about 2 minutes.
ibdknox··on A new Light Table experience
It's not going to be more useful to a Java developer than Eclipse is currently, but that's because we're going after a very different end goal. FWIW, all our work is done in LT and it is far more efficient than I used to be with Vim.
ibdknox··on A new Light Table experience
Think of LT as something more akin to an editor in spirit - you won't see watch windows and all the craziness you often see in "big" IDE's. In that regard, you use it like you use any editor. If you're working with Clojure, ClojureScript, or Javascript code, however, you can evaluate a block inline by pressing Cmd-Enter (or Ctrl-Enter).

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

ibdknox··on A new Light Table experience
It'll definitely be before 1.0, but I'm not exactly sure when. Right now it's still just me on the code side, so it depends a bit on how hiring goes.
ibdknox··on A new Light Table experience
It's a general editor and can open most things out there, however the eval stuff is limited to Clojure, ClojureScript, JavaScript, and CSS.
ibdknox··on A new Light Table experience
I think that might be a bug in CodeMirror[1], does it happen consistently? I'll see what I can track down.

[1]: http://codemirror.net/

ibdknox··on A new Light Table experience
a ~3500 line file? What do you mean by open? Could you put up an issue [1] with a bit more information so we can track it down?

[1]: https://github.com/Kodowa/Light-Table-Playground/issues

ibdknox··on A new Light Table experience
It is, but that's because we have to have a solid editing experience for the "simple" stuff before we can do the more interesting things. What good is it to have these awesome function oriented editors when you can't even modify a file efficiently? :)

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!

ibdknox··on Heroku - Bamboo Routing Performance
My argument was built on the premise that random routing isn't acceptable given the potential slow downs it can cause (as pointed out in the Rap Genius post). If you believe otherwise, then there's no real argument for me to make :)

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.

ibdknox··on Heroku - Bamboo Routing Performance
To be clear, I'm not saying the naive solution I proposed would be "easy". Just suggesting that better solutions do exist and given that solving this very problem is one of their biggest value propositions, taking the easier way out isn't acceptable.
ibdknox··on Heroku - Bamboo Routing Performance
Atomic counters are pretty fast. Redis, for example, should be able to handle it without breaking a sweat: http://redis.io/topics/benchmarks
ibdknox··on Heroku - Bamboo Routing Performance
Ops guys cost a lot more than just using Heroku, not to mention the cost of simply having the responsibility of servers (even if they are virtual). Never underestimate the value of just not having to think about something, especially when you're small group of people.
ibdknox··on Heroku - Bamboo Routing Performance
I'm not sure that should be a concern at the routing layer or even necessarily a concern of heroku. It's not their job to ensure that your code isn't blowing up.

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).

ibdknox··on Heroku - Bamboo Routing Performance
It's a good response in that they are taking responsibility, but it is pretty obvious that they are reluctant to say anything about a fix. In my mind, "it's hard" isn't a valid excuse in this case, especially when there are relatively straightforward solutions that will solve this at a practical level. For example, you could imagine a naive form of intelligent routing that would work simply by keeping a counter per dyno:

- 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.

← PreviousPage 9 of 17Next →