weblog VS ergolib

I started using Common Lisp at work as a way to develop features more quickly in a Java Sprint Boot application.

For the last several months I have been using SPARQL Anything to triplify non-RDF and I've been blogging about it here. The post about Google Sheets might be a helpful intro. With SPARQL Anything you can triplify tabular and non-tabular data.

I blogged about CEPL a while back (for vim users). You can use the approach in my blog post even if you don't have hardware acceleration.

I have a macro in my personal library called BINDING-BLOCK that eliminates many though not all of the parens in common code idioms:

https://github.com/rongarret/ergolib/blob/master/core/bindin...

But like many of the sibling comments say, if you think getting rid of the parens entirely is desirable then you have missed the point, which is that Lisp code is not text, it's a data structure, a linked list, and the best way of serializing a linked list is with delimiters a the start and end, like so:

(1 2 3)

I believe the OP's ergolib provides an example. From https://github.com/rongarret/ergolib/blob/master/core/bindin..., the examples show code like:

;;; (bb

Yes. It was awesome. I used P-Lisp on an Apple II in the late 70s and it pretty much laid the foundation for my whole career. In the 80s I did my compiler class assignments in Lisp while everyone else was using Pascal or C. I got my assignments done in an hour while everyone else took days. I still got an A. I did my masters and Ph.D. thesis work using Coral Common Lisp (now Clozure Common Lisp) first on a Mac Plus, then a Mac II, then a Quadra. Nowadays I run CCL on an MBP. I still use some of the library code I wrote back in the 90s.

to get a list of primes under 100.

See https://github.com/rongarret/ergolib for an implementation of WITH-COLLECTOR and lots of other constructs that are IMHO the Right Way to write code.

Any code modification is a potential security issue. There is nothing special about dynamic class redefinition in this regard.

I use it for deployment. I can deploy new code without having to take my application down. In fact, not only do all my existing instances get updated, but I also use an ORM [1] that automatically updates my database tables too.

[1] https://github.com/rongarret/ergolib/blob/master/layer1/sql....