Instant results etc are fun things to play with, but they will not matter for most use cases there are.
For me it's these two lines you mentioned:
1) You should never have to look for documentation
2) Files are not the best representation of code, just a convenient serialization.
First one is easily doable and there are a lot of plugins that help you with that.
The second is what makes this project interesting and almost made me write my own editor the moment I first saw Light Table.
Files are indeed good way to serialize stuff, but handling each separate section of code as independent (and at the same time, dependent on other sections of code) could actually be a better way. At least it's something I'd like to try.
That's also something that's doable for most languages there are.
Only thing needed are the rules that tell what parts are separate, and additional logic that links those parts to the parts that are called from that one to connect the whole thing as one big entity.
Comments
Instant results etc are fun things to play with, but they will not matter for most use cases there are.
For me it's these two lines you mentioned:
1) You should never have to look for documentation
2) Files are not the best representation of code, just a convenient serialization.
First one is easily doable and there are a lot of plugins that help you with that.
The second is what makes this project interesting and almost made me write my own editor the moment I first saw Light Table.
Files are indeed good way to serialize stuff, but handling each separate section of code as independent (and at the same time, dependent on other sections of code) could actually be a better way. At least it's something I'd like to try.
That's also something that's doable for most languages there are.
Only thing needed are the rules that tell what parts are separate, and additional logic that links those parts to the parts that are called from that one to connect the whole thing as one big entity.