Light Table VS Visual Studio Code

https://github.com/LightTable/LightTable

Looks like the project has been archived

I think LightTable development stalled out when the original creator left the project in 2015. Likely the project was too ambitious and maybe ahead of its time. Or maybe Clojure was not the right language to build an IDE...

I think the closest we got to a closure of Light Table is this: https://chris-granger.com/2014/10/01/beyond-light-table/

Which includes:

> Light Table will continue to go on strong. We haven’t talked too much about it lately, but it’s used by tens of thousands of people and still growing. We use it every day to help us build Eve and thanks to the awesome people in the community that has sprung up around it, it gets better every week.

Judging by GitHub contribution data (https://github.com/LightTable/LightTable/graphs/contributors...), it seems there has only been 25 commits (from one author) since Sep 20, 2019.

Light Table - A customizable editor with instant feedback and showing data values flow through your code.

Most IDEs nowadays are as extensible as Emacs is, but most people don't think of them as app platforms, they think of them as IDEs, so they don't bother craeting Email or IRC clients for their IDEs: - Racket's own DrRacket IDE is pretty extensible, although no one seems to try to extend it with apps like Magit, Org-Mode, Calc, or whatever other useful features that Emacs provides. It is theoretically possible, but it just hasn't happened yet. - LightTable is a powerful programming editor written and extensible in Clojure. - Gnome's Gedit can be scripted in Python.

I think it would be better to create an Emacs Lisp interpreter in Clojure for the LightTable editor.

It looks like it's not completely abandoned, at least. https://github.com/LightTable/LightTable/discussions/2506

I'm no Bozhidar, but thought I'd share some links you might find interesting:

- https://github.com/LightTable/LightTable - Clojure editor made in Clojure, not sure if it's being maintained anymore, core authors moved on to a different project if I remember correctly.

- https://github.com/mogenslund/liquid - Clojure editor made in Clojure, fairly new and basic but has a pretty tight integration with Clojure (itself really) which makes it interesting and it can also be embedded into other applications (or embed your other applications into Liquid)

- https://github.com/Olical/conjure - My daily driver for Clojure development. Is not an editor by itself, but it's written in Clojure, and exposed to neovim as a vim plugin. Not only supports Clojure, but also Fennel, Janet and Racket so far. Pretty handy if you sometimes like to dive into Clojure-like languages that are not Clojure (or Racket).

Visual Studio Code (VS Code): Developed by Microsoft, VS Code is a lightweight yet powerful IDE with extensive support for Python development through extensions. It offers features like IntelliSense, debugging, and built-in Git integration.

In VSCode for example this can be easily done by adding the following .vscode/launch.json file:

I had a near-identical experience. I looked into switching in 2019 and ran into this 2016 bug which was a showstopper for me. Fixed it myself, grand total 4 line diff. https://github.com/microsoft/vscode/issues/10643

When working in Visual Studio Code (VS Code), always create a new Python file for your project.

Code Editor: Choose a code editor like Visual Studio Code that offers good support for web technologies and extensions for PWA development.

When working in Visual Studio Code (VS Code), create a new Python file for our music player project. It's helpful to have separate files for different parts of your project.

https://github.com/microsoft/vscode/forks

27,000 people seem to have done so.

Choosing IDE: Selecting a suitable Integrated Development Environment (IDE) is crucial for efficient coding. Consider popular options such as PyCharm, Visual Studio Code, or Jupyter Notebook. Install your preferred IDE and ensure it's configured to work with Python.

I was doing it all wrong, designing and developing on the fly, using the same tool - VScode; Making one step forward and ten back when I mess up with good code while trying to get rid of the bad. I had gotten away with it for three pages, but it had finally caught up with me.