If you use clojure-mcp/clojure-mcp-light that problem goes away, and that gives it the ability to run a repl and work from it directly. It’s night and day.
HN user
mpenet
Thanks! Long time lurker indeed.
I also forgot the very solid ClojureDart.
Clojure will be around as long as the jvm. It’s mostly done at the core level, most updates are to leverage new host features nowadays. The rest is happily provided at the library level by the community (which is still very prolific).
And it’s not tied to the jvm per say, look at clojurescript (and derivatives) or the upcoming jank.
It’s far from dead. As much as I like CL, the ecosystem is a bit of a desert compared to the jvm.
And not enclosed
Editor Code Assistant (ECA) - AI pair programming capabilities agnostic of editor
That’s quite common, it means they host the control plane for free but not the kubelets (worker nodes).
If there’s any hardware issue on your dedicated box it might take a lot of time until your box gets back up (hours, days…). On a vps it’s less likely to happen in the first place (hvs are usually better quality) and if that happens migration takes minutes.
That doesn't work well in some conditions, it's not new either. Some cruise missiles that have TFR (Terrain-following radar) and actually do this already.
It also is not really applicable when you are on a balistic course at *very* high altitude, course correction has to happen early in these case given the reentry speed/constraints.
That. However that works just fine for ICBMs and the like…
The future is more likely to be quantum accelerometers and quantum gyroscopes, as they have no “external dependency”.
There are plenty of very ergonomic languages on the JVM (for instance clojure).
I wouldn’t dismiss the JVM as a whole, it is a marvel of engineering and is evolving quickly nowadays (see loom, panama, leyden, etc…).
My dad used to work on certifying, servicing and making custom instruments for planes, subs, prototypes of all kinds of that era (60s to mid-90s).
His “lab” was basically all about testing and simulating environments for the instruments. He had tons of sayings about not having room for error in his line of work. This is as close as you can get from “building bridges” and to this day I don’t think I have seen this level of attention to detail/perfection in any other profession.
His job involved electronical engineering , mechanical engineering and programming amongst other things, not to mention a deep knowledge of the physics of these environments.
Back then also the tools or source of information that were available to them were quite crude compared to what we have now.
His spare time was all about flying, pimping his ham radio gear with all kind of “home made” electronics, build antennas and messing with computers. I guess he’d qualify as a “Hacker” nowadays.
Because it’s an extra runtime check vs a direct lua call
Yeah it’s quite personal at this point. I have used both but I am way more efficient with emacs. I also find the investment in emacs pays back more over time. Generally I also find emacs a lot more snappy.
But that’s just me, and to be fair I have used emacs since the mid 90s and vscode only for half a year. The past few years emacs developement/experience also improved massively.
It’s good to have choices ultimately and they both pulled good ideas from each other.
There’s vterm nowadays
consult-grep (and it’s variants using git or rg etc) let you do that, with results as you type in mini buffer, with full live previews in a separate buffer (if you want). With an extra keystroke you can export all the results in a buffer and edit/save them in place too.
It’s quite easy to have non trivial, reproducible configs on a single file nowadays (ex using straight/use-package). The rare times I needed to use emacs on a remote server with my config my full blow setup is a copy/paste, or curl call away.
Same. It really was the best screen size/ratio for me. I was basically carrying it everywhere.
'ish.
datahike would be the closest to datomic in terms of features/implementation (support for as-of, transactor etc).
Then in terms of maturity I think the choice is between xtdb and datascript, both are very solid/maintained but they are also vastly different.