7 ms·
I don't mind if the future is specific. But its really wrong to say IDE's like Eclipse don't do one specific task well. Eclipse really makes Java programming v
by kamaal 14y ago
I don't mind if the future is specific. But its really wrong to say IDE's like Eclipse don't do one specific task well.
Eclipse really makes Java programming very easy. And I can tell you minus Eclipse programming in Java would be a very frustrating experience, given the verbosity, configuration mess and XML's all over the place. Eclipse these days is advanced enough to really blur the difference between and novice and a expert Java programmers. So by any measure I would say eclipse already does what light table aims to do. The only problem with eclipse is its too heavy, chews a lot of memory and becomes very heavy as things go on.
What we expect from light table is really what things like Emacs and Vim already are, plus what they miss. Which is modern GUI candy, easy configuration, availability of packages, stuff like refactoring, bench marking, auto complete and Intellisense easily available out of the box. Along with evolution with modern needs and demands.
So that is why what we really needed was an Emacs + all that I mentioned.
I think it will be nice if at some point requirements are frozen for Light table. Because things like this really slip into Second systems effect easily.
According to me Light Table must be Emacs for the Modern Generation. Anything else, and it won't be impressive. A thin editor, extensible by lisp. All lisp and other Emacs editor goodies but with all the modern demands.
We already have enough of other kind of IDE's.
- ibdknox 14y agoThese were examples of extensions to make a point and not at all what we'll be focusing on. What we're making sure of is that the platform for such things exists and enables all of the things that old UI's and such don't allow. I think the parallel to emacs is a good one and while I certainly won't say at this point that we'll be the "modern emacs", it's our hope we can come close.
- mattbriggs 14y agoout of curiosity, is js going to be your "elisp"?
- phyzome 14y agoClojurescript, actually -- a Clojure dialect that compiles to JS. Well, Clojure too, on the server side of things.
- Arelius 14y agoAre we really gonna need the JVM running the backend for this? That seems so unnecessary.
- mattbriggs 14y agoyou could probably just precompile your extension
- Arelius 14y agoafaict, precompiled java still requires the jvm.
- frio 14y agoGiven the initial goal was for a Clojure editor (which runs on the JVM), running the JVM was a prerequisite anyway.
- Rayne 14y agoI'm pretty sure the core of it is to be written in Clojure, so yes, you'll need the JVM running. It is necessary if it is to be written in a JVM language. Eclipse and a number of other IDEs also require a JVM to be running.
- kamaal 14y agoI think from the discussions and other threads what I infer is that we need a total re-look at the concept of an editor, Your way actually looks good. Except that we need to retain the 'Emacs infrastructure'. We need to really keep Lisp as the extension language. I think what we need is Light Table with something like this : http://www.kickstarter.com/projects/568774734/emacsy-an-embeddable-emacs http://www.kickstarter.com/projects/568774734/emacsy-an-embe... You have to develop Light Table ON the Emacs OS!
- ibdknox 14y agoLisp is the extension language :) Everything so far is Clojure + ClojureScript with the language backends written in the language they support (python in python and so on)
- deleted 14y ago[deleted]
- stcredzero 14y agoHow about Stallman's idea for GUILE (Scheme) uber-alles. Do source-to-source translation of approximations of the supported languages to Clojure. This would allow everyone access to almost everything in the tool.
- lucian1900 14y agoThat effort hasn't even materialised for Scheme+Elisp for Emacs. The whole approach is guaranteed to not produce a perfectly compliant of any other language.
- stcredzero 14y agoYes, that is the price. That's the price for native access to the entire codebase of the underlying editor. So long as it's close enough, you don't need perfect compliance.
- mtrimpe 14y agoIt might have been better to demonstrate this with examples like: truth-tables for (nested) if statements petri-nets for a state machine etc. etc. etc.
- chrismcbride 14y agoI think Light Tables target is dynamic languages, which the current crop of IDEs dont have great support for.
- roguecoder 14y agoIf we assume dynamic languages are the future, then scripting is absolutely the right answer. However, what I see is people using dynamic languages because they are what frameworks are written in, not because they want to use a dynamic language. I hope that LightTable incorporates a packaging mechanism such that we can have a Ruby on Rails package, for example, and the 60% of RoR developers who never tweak anything can be more productive. The problem is that you can give an excellent developer an unspecified tool and they will make it serve their purpose. We need the ability to pass those productivity improvements down the food chain, which is where Emacs fails utterly.
- inportb 14y ago> minus Eclipse programming in Java would be a very frustrating experience I'm not sure about that... Eclipse gets fatter and slower with each release. Of course, I still use it because Google really wants Android developers to do so. In my opinion, the most frustrating thing about using Eclipse for Android work is that it crashes every time I try to export a package, unless I close every open file and restart Eclipse before trying. (the problem is mitigated by disabling automatic builds) I guess that's because Eclipse runs on Java and Java is wasteful. It would be really nice if we could have a "native" equivalent of Eclipse, with less bloat.
- why-el 14y agoI face similar issues at work but I don't think Eclipse's issue is Java, else you're saying that anything developed in Java will face a "boated" fate. Eclipse's problem is exactly what Chris mentioned in the article, ok on most things and awesome at none. Edit: Typos.
- inportb 14y agoIndeed, it's not all Java's fault. But I think Java does contribute to the overhead because my experience with Java programs in general usually involves long startup time and excessive memory usage. (And then there's the UI bloat, which makes Eclipse look like this by default: < http://www.flickr.com/photos/geofharries/5145925147/sizes/o/in/photostream/ http://www.flickr.com/photos/geofharries/5145925147/sizes/o/... >. But that's a totally different issue. Thank goodness for Fast View.)
- why-el 14y agoI see your point there. I myself tolerate Eclipse on Ubuntu, where the UI surprisingly fits, at least for me. Its almost indistinguishable from other UIs, except maybe Spotify which is (IMO) way ahead of the rest. But I cant stand Eclipse on my Mac OS X and there you can see all the stuff you mentioned.
- lnguyen 14y agoAt it's core, Eclipse is really good at Java. It's why it killed off Visual Cafe and most other commercial IDEs (was sad to see Borland go). The issue is that it's more than just a Java language editor. Once you load it up with all the extras to accommodate development models, frameworks, runtimes, build processes, etc. it does become an unwieldy mess. But it's really hard not to considering how moving parts large-scale development has.
- Arelius 14y agoWhat I worry about Light Table is what it won't be from Emacs. At the end of the day, Emacs is still a text editor, and still edits files. This means that I really can use it for anything, doesn't matter if I have a mode for it, or an embedded compiler/REPL. It still just works, and we can't forget this if we want a modern Emacs. Emacs was born in a world of textfiles, Light Table shows us a post-textfile world, but before we can get to the future, it needs to be able to survive in the world we live in today, which is one where textfiles are king.
- ibdknox 14y agoFrom the bottom of the post: "If you couple [DSTs] with the generalized editing capabilities I showed last time, you have what we believe to be the future of tools: an environment that you are able to mold to the exact shape of your problem." I agree, we have no intention of removing general editing - you need it as much as anything else at this point.
- heretohelp 14y agoI'm more deeply concerned about the fact that Emacs is something which, roughly speaking, I can control. Emacs is a community project. Your project appears to be commercial in nature, regardless of whether or not it's open source. Your project will also be a dictatorship by dint of the fact that it belongs to you. Why should I trust you to provide the most fundamental tool in my work?
- ibdknox 14y agoIt will probably be under the GPL just like Emacs, so I'm not sure I understand the concern?
- Arelius 14y agoI think the fear is in the "probably". YCombinator, for instance, doesn't have a good record of doing things just for the community good, they are after all profit seeking. That's not to say it won't happen, but the fear is there.
- stcredzero 14y agoI would say eclipse already does what light table aims to do. Can you come to a realization in the middle of an Eclipse debugging session, get a great idea for making yourself more productive, take time to script yourself a working and fully debugged extension of Eclipse and continue what you were doing 20 minutes later? I've done precisely this in Smalltalk on many occasions. You can script something like a custom browser that shows you everything that uses function A and also function B and has a reference to class C (and with complete syntactic accuracy) in around that time. I suspect that this kind of very small grained toolsmithing is common for really good programmers in dynamic environments. The only problem is that it's been harder than necessary to integrate that with the most commonly used coding tool. (TextMate's ability to export selections to scripts is very nice, but it can go farther than that. Emacs is very powerful for this, but not everyone wants to script in elisp.) It's not that Light Table is going to do something unprecedented. It's more like what git did with quick access to diffs: a quantitative change can become a qualitative change. Change the cost-benefit of toolsmithing, and you can use it in new ways.
- catenate 14y agoAcme supports constantly improving how you work in little ways, better than tools with plugins or extension languages, by not having many features, and providing a good interface to route text through shell pipelines. For a simple example, Acme has no paragraph justifier, but it doesn't need one, since fmt exists. To use it, highlight a paragraph of text with the left mouse button, highlight a typed-in |fmt command with the middle mouse button, and release the middle mouse button to run the paragraph through |fmt and replace it in place. With this I can leverage anything I can call from the command line, in any language, to be part of my editor. No need to rewrite tools in the program's specific extension language, whether Elisp or Smalltalk or Clojure. As another example, since it's so easy to just run a shell command from Acme (highlight the command text and middle-click it), I'm constantly customizing pre-written shell commands to e.g. grep for lines in code (to the point of creating indexes on the fly for files), and then right-clicking on grep -n output to jump to a specific line in a file.
- TeMPOraL 14y ago
- adeelk 14y ago> But its really wrong to say IDE's like Eclipse don't do one specific task well. Eclipse really makes Java programming very easy. “Making Java programming easy” is not one specific task!