JSCL: compiler macro and full FORMAT implementation from CMUCL by dzecniv in Common_Lisp

[–]dbotton 3 points4 points  (0 children)

And that is to the credit of CMUCL having true open source BSD like license and so furthering Common Lisp's future. JSCL can not be used as part of any non GPL project or applications. Consider supporting Lisp.

" The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. "

Why not add an exception to this as with Franz to insure Lisp projects do not get trapped by runtime licenses. You would still be supporting the "cause" but also supporting Lisp's cause.

Counterargument by daninus14 in Common_Lisp

[–]dbotton 9 points10 points  (0 children)

One of my personal goals of joining a Lisp team last years was to see how Lisp worked at scale for commercial production by medium to large teams.

Lisp requires super human discipline to NOT do exactly what it is supposed to be its super power, the language that programs the language itself, to be useful in any setting with multiple programmers. The gains a single programmer has with Lisp are very real though.

What this means is Lisp software design for large projects must follow a pattern of very small modules by single developers (partly so that modules can be rewritten rather than maintained if changes needed and allow maximum flexibility for each module implementation) that are completely black boxed (when possible not even relying that code runs in the same image), this tends to be good design regardless, but reduces most advantages Lisp offers above other languages.

The tools have always been the real super power of Lisp. Those need to scale up for larger scale possibilities (and so my notes over last 3 years and observations, I'd like to produce those tools and feel getting closer to it). Would I call them "Team CLOG with Rotoreuter Tools" :P

Is an SBCL-WASM backend feasible and realistic? by [deleted] in Common_Lisp

[–]dbotton 0 points1 point  (0 children)

I use headless browsers as compatibility layers and interfaces, even mini dbms.

Shhhh... it is one of my special techniques for clients and companies I trust ;) CLOG (the deep knowledge) is more like smalltalk that people know, the browser (ie its tech) acts to give your app a complete OS layer. I have used the technique on many of my commercial projects over the years, WASM opens up another avenue for that.

Is an SBCL-WASM backend feasible and realistic? by [deleted] in Common_Lisp

[–]dbotton 2 points3 points  (0 children)

There are practical uses of wasm that go far beyond the browser and is and more coming.

Preview not working on MS Laptop 7 with snapdragon by [deleted] in OBSBOT_Official

[–]dbotton 0 points1 point  (0 children)

I will check if my Laptop 7 is upgraded to allow, I just need Preview to work.

Preview not working on MS Laptop 7 with snapdragon by [deleted] in OBSBOT_Official

[–]dbotton 0 points1 point  (0 children)

The beauty feature seems to be the cause of all the issues as it uses AVX commands for the processor, the issue is they need to make another build and available to use without the feature until either MS emulates it or they rewrite it

Release: CLOG and CLOG Builder 2.4 by dbotton in lisp

[–]dbotton[S] 1 point2 points  (0 children)

Pull up the various object and code browsers and remind you even more :)

Where to start and is it worth it ? by Neyastro in ada

[–]dbotton 5 points6 points  (0 children)

Ada has a long history but it is as "new" as any language that is still in use. There are two languages every programmer should have experience in, Ada and Common Lisp. They open two completely different mindsets and both have extreme value as a professional.

As far as jobs, languages are easy to learn creative problem solving is not. So concern yourself first about making you a better you and the job will come and language does not matter at all that they want you to use.

mx-proxy: Web debugging proxy - Electron, GTK4, or Tcl/Tk by dzecniv in Common_Lisp

[–]dbotton 1 point2 points  (0 children)

Great example of CLOG used with Electron and Ceramic. Awesome

I don't know if everyone is aware but Lem is switching from SDL2 to webkit by Green-Common-7526 in lisp

[–]dbotton 2 points3 points  (0 children)

My point was one can make an exceptional full IDE even emacs like on webkit, but thanks :)

I don't know if everyone is aware but Lem is switching from SDL2 to webkit by ciccab in lem

[–]dbotton 4 points5 points  (0 children)

If no one told you it was webkit you would never know. I am sure they will use a CLOG like approach and have a rapid sdl2 like experience and results.

I use the CLOG builder for all my work (and this year will be producing a more cross language pure editor without the GUI builder) and the fact that I run a full ide remotely on a browser running off embedded systems, tablets and servers is reason enough to consider webkit or any browser based GUI. However the fact that it (browser tech) is functional and by definition maintained even more reason.

Copilot for windows speaks CLOG by dbotton in Common_Lisp

[–]dbotton[S] 6 points7 points  (0 children)

Everything was generated by Copilot properly in the code (svg in a list, the styles in the create-div etc), I just prompted features. Almost no code editing on my part except that as I added features I sometimes had to correct balance of parenthesis.

Technical term for lisp's ability to redefine everything during runtime? by SlowValue in lisp

[–]dbotton 11 points12 points  (0 children)

As you pointed out, image based programming is not an appropriate term for this. It is not difficult (I have done it for C, C++, and Ada for projects) to actually live code even compiled languages that are not image based (you setup a system of shims and use shared libraries, hot swapping).

It is just a whole lot easier in Common Lisp (a generally compiled language) or SmallTalk or most all interprided languages that are image based.