The future is specific

I love it, especially the grouping of files: route + models + templates, in 1 view is something I see a use for. Does anyone know of an editor which can do something similar?

Re: The future is specific

#6

Post by lubutu » Tue, May 22, 2012, 3:16 PM UTC

I don't quite understand what the difference is between Light Table's modes and IDEs' plugins. Domain-specific components are exactly what make IDEs 'integrated'; without them they are generalised editors. But there is absolutely no difference, as far as I can tell, between Light Table's new SQL mode and an SQL IDE plugin.

I'm personally much more fond of the Unix 'tool approach', in which there are no task-specific modes or plugins, but tools can still be composed ad hoc, as in Plan 9's Acme.

Re: The future is specific

#7

Post by [deleted] » Tue, May 22, 2012, 3:16 PM UTC

nebiros wrote: post #3

RUUUUUUBBBBYYYYY SUUUUPPPOOOORRRTTTTT!

[deleted]

Re: The future is specific

#8

Post by pwny » Tue, May 22, 2012, 3:16 PM UTC

Boy am I happy I pledged for Light Table. And the benchmark mode looks so freaking great. I'm getting excited just thinking about it. I don't think I'll be able to wait until the early beta. ARGHH!

Re: The future is specific

#9

Post by mcrittenden » Tue, May 22, 2012, 3:18 PM UTC

With all of the demos and information posted I still have trouble visualizing this working for real-world applications. A specific example: in the Python/Flask demo, functions were added to the current view as it was called. How would this work in a more complex case with calls to many functions, each which call many more functions (and so on), each belonging to different objects, etc.? The view would quickly become a huge list of functions and code blocks, most of which you probably don't need to see at any given time, and at this point it's no more useful than plain old user-curated tabs.

That's just one example. The same conceptual problems pop up for stuff like on-the-fly code execution (what if your code depends on user input or many SQL queries or files that may or may not exist at that point), benchmark mode (benchmarking a complex app is obviously a lot more complicated than just running two code blocks side by side), etc.

I know this is just a demo and it's all very early in the process, and I'm not saying that this should be a solved problem yet, but I just can't picture in my head a way that this could ever be a solved problem as long as LightTable remains somewhat similar to its current state.

Re: The future is specific

#10

Post by DasIch » Tue, May 22, 2012, 3:19 PM UTC

The first time I heard about Light Table I was rather critical but this begins to look like something that could really replace vim for me. This is rather surprising given my general distaste of IDEs.