![]() ![]() We are a bit different in that you have even more freedom to change things (you could rip out everything we've done and replace it), but I think the community will do a good job of using what works and ignoring what doesn't. InfoQ: Do you have any concerns that LightTable might become diluted or bogged down by an excess of plugins? Chris: In general I think ecosystems are pretty good at regulating themselves - there are many thousands of plugins for emacs/vim/sublime/textmate and they all seem to do ok. InfoQ talked to Chris about LightTable’s future. During the campaign the project was accepted as part of YCombinator's 2012 summer batch, securing its creation. ![]() A successful Kickstarter campaign followed, showing that there was wide interest in such a tool being created. Chris set out to create an IDE that aims to give developers immediate feedback on the code they are writing. Originally taking inspiration from Bret Victor’s talk Inventing on Principle, where Bret outlined his guiding principle as “creators need an immediate connection to what they create”. All of which are made available via LightTable’s built-in plugin manager. The community has started to contribute additional language plugins to support Haskell, Ruby, F#, LaTex and Markdown, as well as several focused on the core editing experience ( Bracket Glow, base16 theme, match highlighter, etc). Third party plugin support was the highlight feature of the release. Chris Granger has open sourced the LightTable IDE with the 0.6 release. ![]()
0 Comments
Leave a Reply. |