8,390 karma · joined September 5, 2010
http://chris-granger.com http://www.witheve.com http://www.lighttable.com
will get fixed tomorrow.
LT will be open source, just want it to get a bit more stable first.
I await my lynching. :D
FTW.
If there was a decent way to handle dynamic evaluation though, it could certainly be added, and without too much issue I would imagine :)
In all seriousness, the plugin architecture will certainly allow for exactly that to happen. If you're interested in trying your hand at adding CL, I know a guy who could probably sneak you into the beta when it turns private ;)
It surprises me how little we really know about the human aspects of our own field. The practical/pragmatic side of understanding how we really program, what's hard, where we stumble, what we do easily, etc is something that we're trying to address with Light Table. LT happens to be the perfect playground to do this sort of experimentation, so at the very least we'll be making it easier for researchers already in the space. But as we get further along and have a few more hands to spare, we'll start picking off research questions ourselves.
The more the merrier, right? :)
To address if this is enough, I'd say you'd be surprised how much you can make things stretch if you absolutely have to, but most companies also raise a small amount of money after YC's demo day as well to help them continue. You can think of YC as a startup bootcamp at the end of which you have to prove yourself to get the opportunity (further investment, usually) to continue on. With the startfund though, you get more than those three months to do so.
In short, yes, YC invests $20k and produces $6.1bn in value across the alumni.
To some degree I think I agree with you that what this ultimately comes down to is trust - trust that I can fix this, or that I can make blah happen. I've worked for some great people who did trust me, but unfortunately someone up the chain didn't. To make any real impact I think you have to be willing to take some serious risks and when you're that far away from the problem, it's hard to imagine why those risks are worth taking.
In any sufficiently large organization, preaching a disparate vision is bound to hit a wall, because somewhere in there is another guy just like you - someone crazy enough to start a company because they believe in their own vision.
M&A only really makes sense to me in the #2 case, where the merger actually better enables us to deliver our product. I certainly think there are cases where acquisition can be a boon to your users, we just don't hear about them as much.
For money to be a motivating factor, though, it would have to be enough to ensure that I could fulfill our promise to our users and also bankroll working on one of the problems from #1 :)
Robert and I really want to see people using LT to learn programming and I think we have some very compelling things to offer there. :) Robert is going to be making some rounds once 0.4.0 is out to see what we need to do to get folks like Hackbright Academy and dev bootcamp and all the others around here using it.
1) Open your html file
2) run the `connect to browser command` and copy the script tag
3) insert script tag into your html file
4) bring up your page in the browser (it has to have the output of lein-cljsbuild on it to get the initial cljs dependencies and such)
5) open a cljs file
6) eval an expression with cmd/ctrl+enter
7) select the browser instead of LightTable-UI
This process will be getting much simpler in the next release. :)
[1]: http://www.chris-granger.com/2013/02/27/light-table-030-expe...
In no way have they solved the actual issue (a poor queuing strategy). And so even if you now know that you're getting awful performance due to queuing and you even try to get a multi-threaded strategy going per their suggestion, you will see the exact same issue at scale. That is not a fix.
Their stance on actually implementing a strategy that removes the root issue has been one of silence. Suggesting that "this probably won't be the end of it" isn't useful if you're running a business that relies on Heroku. If that isn't the end of it, then they should be far more communicative about the steps they're taking. Given their blog posts, we have no evidence that further solutions to this problem are being worked on or that they even acknowledge it's something they should fix.
So no, I do not agree with you that that is a lot of "fixing".