Light Table VS Vagrant

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).

Vagrant

Take a look at Vagrant! https://www.vagrantup.com/ In my admittedly limited understanding I believe it offers closer to a nix like reproducable rather than repeatable deployments.

on the off chance one hasn't been tracking it, there were several "we don't need your stinking BuSL" projects when this drama first started:

https://github.com/opentofu#why-opentofu (Terraform)

https://github.com/openbao/openbao#readme (Vault)

and I know of several attempts at Vagrant <https://github.com/hashicorp/vagrant/forks> but I don't believe one of them has caught traction yet

There are also some who have talked about an "open Nomad" but since I don't play in that space I can't speak to it

It sounds like you're using Nix as a sort of configuration management solution. CM just isn't worth it for managing a single desktop IMO. It triples the effort for whenever you need to add or remove a package, as you must now add that also to your nix configuration. You're supposed to be able to make that back up in time saved restoring to the next machine, but inevitably the next machine will be different enough that you'll have to edit it all anyway. In the end I just got tired of trying to manage my own machine with infrastructure as code (though in fairness I was using puppet at the time not nix).

I keep a git repository with all my dot files in it[1]. This seems to work the best. It has a Windows folder as well, and I copy that out whenever I need to set up Windows.

A lot of people like using WSL but I hate how it hogs on my memory. Hyper-V is a terrible virtualization engine for consumer-grade use cases because it can't thin provision RAM. If I need to use docker, I will spin up a small Linux VM using vagrant[3] with Virtualbox[4] and put Docker on there. Vagrant is an extremely underrated tool in my opinion, particularly in a Windows context.

I use scoop for packages. Typically I will scoop install msys2 and then pin it so that it doesn't get blown away by the next upgrade.

Then I basically do all of my development inside of msys2. I can get most things running in there without virtualization. In my case that means sbcl and roswell for common lisp, senpai for irc, and tmux and nvim for sanity. Msys2 uses the pacman package manager and this is good enough.

All In all, I set up my Windows machine affresh after a while of not using it and it took me about 3 hours. Most of that time was just getting through upgrades though, I felt like it was pretty fast.

1: https://git.sr.ht/~skin/dotfiles

2: https://www.msys2.org/

3: https://www.vagrantup.com/

4: https://www.virtualbox.org/

Tools like Docker and Vagrant can be used to allow local environments to mimic production environments.

There's an open issue [1]. A scripting interface has since been added [2], and updated [3], so there's progress.

[1] https://github.com/hashicorp/vagrant/issues/12518

Someone should fork and maintain Vagrant with an MPL open source license:

https://github.com/hashicorp/vagrant

https://github.com/hashicorp/vagrant/blob/v2.3.7/CHANGELOG.m... ?

The changelog lists both improvements and bug fixes and there's even apparently some effort to port it away from ruby: https://github.com/hashicorp/vagrant/blob/v2.3.7/internal/cl...