News for hackers. Stuff that matters.
Re:Chris Granger on the LightTable architecture by seanmcdirmid on Wednesday April 15, 2015 @07:16AM (#9380130)
A lot of tech comes and goes because either (a) the time isn't right or (b) it isn't that good and gets superseded by something else.

Those guys from the 60s and 70s were smart, but we are smart also! It is time for us to stop living in the past and start moving to the future. Full on live programming hasn't been accomplished yet, the best achieved are simple REPLs, hot code swapping in Erlang/Smalltalk (which does nothing with state), and...direct manipulation (you can just update your objects directly, screw any code).

Some things just haven't been accomplished yet, and to claim they have been is just seriously dishonest and damaging since it dissuades people from trying. (I'm not referring to RPG here, I bet he is as frustrated as I am).

So ignore the haters and just get things done, I guess.

Re:Chris Granger on the LightTable architecture by TeMPOraL on Wednesday April 15, 2015 @08:12AM (#9380378)
> the best achieved are simple REPLs, hot code swapping in Erlang/Smalltalk (which does nothing with state), and...direct manipulation (you can just update your objects directly, screw any code)

I think that sort of supports the point of the GP. Lisp had all the above and more (e.g. a proper REPL, live recompiling of everything in your image) since almost forever and yet not many people know about that. There's a lot of knowledge that was just forgotten by the fashion-industry IT is.

So I don't think we should stop trying - but it's really worth to go through the work done in 60s and 70s, because we could use it.

Re:Chris Granger on the LightTable architecture by seanmcdirmid on Wednesday April 15, 2015 @08:24AM (#9380438)
It's just not useful, they needed to go farther and wound up with a PX that some liked, but most didn't feel was worth it. Take the REPL for example, you are stuck in a linear command driven level of interaction if state is involved (and if state isn't, it is only useful as a fancy calculator). Take fix and continue in smaltalk - you can change the code, but you can't really fix the state (I.e. By time traveling), leaving your program in a seriously fragile state. And take morphic: where you can change the state (by directly manipulating objects) but not the code, so if you change something driven by code, your changes are completely ephemeral.

Each experience is serious lacking, and there are good reasons they haven't taken over the world. Chris Hancock does a better job than me in describing this, which is why I keep bringing up his dissertation: https://llk.media.mit.edu/papers/ch-phd.pdf

Re:Chris Granger on the LightTable architecture by marktangotango on Wednesday April 15, 2015 @08:32AM (#9380498)
>>So ignore the haters and just get things done, I guess.

Not sure if you're implying I'm a hater here or not, but being charitable I'll assume not.

>> It is time for us to stop living in the past and start moving to the future.

The old saw about those who don't know their history and repetition springs to mind. Edit: not imply you don't know the history, as you clearly do, but many don't.

Re:Chris Granger on the LightTable architecture by seanmcdirmid on Wednesday April 15, 2015 @08:45AM (#9380559)
I was referring to the sentiment in general, with specific people in mind that I dare not say out loud.

I know my PL history pretty well, from Sutherland, McCarthy, Kay, Steele, Papert, Lieberman, not to mention all the VPLs, constraint programming systems, and so on. Ya, there is a lot of work, but that is no excuse to stagnate.

Edit: I'm not sure it is useful to shame people for not knowing their history. There isn't much wrong with reinvention, and who knows, it might be better than what was invented before. Our legacy sometimes does us more harm than good.

Re:Chris Granger on the LightTable architecture by lfowles on Wednesday April 15, 2015 @12:16PM (#9381980)
Yep, there's nothing intrinsically magical about that time that made language designers better than now. In fact, 30-40 years later we even have more collective experience under our belts!