clog
Vacietis
Our great sponsors
clog | Vacietis | |
---|---|---|
150 | 7 | |
1,419 | 294 | |
- | - | |
9.2 | 0.0 | |
3 days ago | almost 2 years ago | |
Common Lisp | Common Lisp | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
clog
- Embracing Common Lisp in the Modern World
-
Use any web browser as GUI, with Zig in the back end and HTML5 in the front end
Reminds me of the approach of CLOG (Common Lisp Omnificent Gui[1]) and its ancestor GNOGA (The GNU Omnificent GUI for Ada[2]).
They also integrate basic components and even graphical UI editor (at least for CLOG), so you can essentially develop the whole thing from inside CL or Ada
[1] https://github.com/rabbibotton/clog
[2] https://github.com/alire-project/gnoga
-
Common Lisp: An Interactive Approach (1992) [pdf]
For me David Botton [0] with his work including code, support and videos is doing very nice work in this direction.
I use SBCL for everything but work because I cannot get; we are getting there, but like you say, it’s such a nice experience working interactively building fast that it is magic and it’s painful returning to my daily work of Python and typescript/react. It feels like a waste of time/life, really.
[0] https://github.com/rabbibotton/clog
- CLOG - The Common Lisp Omnificent GUI
- Clog The Common Lisp Omnificent GUI
- Clog – The Common Lisp Omnificent GUI
- Tkinter Designer: Quickly Turn Figma Design to Python Tkinter GUI
-
Want to learn lisp?
I was following along on the Windows page and didn't check back on the main README to see if any of the other instructions would help.
-
All Web frontend lisp projects
It the answer is "latter", then you could look at Common Lisp and Reblocks (https://40ants.com/reblocks/) or CLOG (https://github.com/rabbibotton/clog).
-
How to Understand and Use Common Lisp
I haven't used Clojure professionally in 10 years so with a grain of salt here are my thoughts as only one other person answered...
CL over Clojure: it's the OG Lisp that the creator of Clojure used and wanted to continue using but faced too much resistance from management afraid of anything not-Java/not-Oracle, or not-CLR/not-Microsoft, etc. Clojure shipped originally as "just another jar" so devs could "sneak" it in. If you don't have such a management restriction, why Clojure? If you want to integrate CL with the JVM, you can use the ABCL implementation, there's also something from one of the proprietary Lisps. Some useful CL features that are nice in this domain: conditions and restarts mentioned in a sibling comment (very nice to help interactively develop/debug e.g. a selenium webdriver test), ability to easily compile an exe (perhaps useful for microservices, or just to keep your deployment environment clean and not having to care about Lisp), and ability to easily ship with an open local socket allowing you to SSH in (or SSH port forward) and debug/fix/poke around in production (JVM of course lets you attach debuggers to a running process, even certain billion+ dollar companies will have supervised/limited prod debugging sessions for various hairy cases, but it's not as interactive). You should never hear CL advocates claim you can't scale to large teams/groups of engineers or large multi-million-lines sized projects, though you might oddly hear Clojure advocates sometimes claim you can't (and shouldn't) scale to such large projects -- large groups of engineers are a non-issue for them as well though, the challenge is in hiring, not in the language somehow making it impossible to modularize and keep people from stepping on each other.
Clojure over CL: its integration with the JVM is nicer than ABCL's, so if you do actually want a lot of the great world of Java stuff, it's easier to get at. Database integration libraries are better. Access to libs (Clojure or Java) is via Maven, so it's a larger ecosystem with more self-integrating components (especially around monitoring/metrics) than what's available for Lisp via Quicklisp. Clojure is very opinionated, much of it quite tasteful, and that gives the whole ecosystem a certain consistency. (You can have immutable data structures in CL, you can if you want use [] for literal vectors and make them syntactically important e.g. in let bindings, but not everyone will be on board.) Even though its popularity seems to have stopped growing, at least at the same rate as e.g. Go which it was keeping pace with for a while, it's still popular enough with a bigger community; as a proxy measure there are multiple conferences around the world and good talks at adjacent conferences, whereas Lisp mostly just has one conference in Europe per year and only occasional branching outside of that.
If you're doing a client-side-heavy webapp, ClojureScript is still amazing, CL's answers there aren't very compelling with the exception of CLOG (https://github.com/rabbibotton/clog) which takes an entirely different direction than the usual idea of translating/running Lisp on top of JavaScript and its popular frameworks.
Vacietis
- List of (open source) C compilers
-
Rust's Poor Composability
Yes. Not because of the developer, but because of how extremely flexible and dynamic the Lisp-family languages are. The power and joy of Lisp is in how it's almost a meta-language, so every project can become its own EDSL. The most famous (infamous?) example of this is Vacietis[2], which is a Common Lisp library that allows C code to be imported directly(!!).
[0] IIRC the Yesod framework's Warp does well on benchmarks, and when you look at code like https://github.com/yesodweb/wai/blob/master/warp/Network/Wai... you can see the lengths they had to go through to work around the choice of implementation language.
[1] Go has a garbage collector, but exposes the stack/heap distinction more directly than Haskell, so it's easier to write allocation-free code in hot paths.
[2] https://github.com/vsedach/Vacietis
-
Any attempts at a "distro"/"package manager" for building a programming language?
racket and common lisp both offer reader interfaces which allow parsing non-s-expression languages. see https://github.com/vsedach/Vacietis , a c compiler implemented in common lisp which uses the common lisp reader.
-
C to php converter online
Very funny. One might be interested in e.g. Vacietis which does manage to compile enough of C correctly to a higher level language (in this case, Common Lisp) to be interesting.
-
CLOG Needs You :)
https://github.com/vsedach/Vacietis - C in CL
-
Compiler in Lisp
C
-
Wisp: A light Lisp written in C++
How about C?
https://news.ycombinator.com/item?id=25531871
https://github.com/vsedach/Vacietis
================
Vacietis is a C compiler for Common Lisp systems.
Vacietis works by loading C code into a Common Lisp runtime as though
What are some alternatives?
kandria - A post-apocalyptic actionRPG. Now on Steam!
foth - Tutorial-style FORTH implementation written in golang
stumpwm - The Stump Window Manager
yale-haskell - HASKELL: Yale Haskell system written in Lisp
awesome-cl - A curated list of awesome Common Lisp frameworks, libraries and other shiny stuff.
sectorlisp - Bootstrapping LISP in a Boot Sector
electron-sbcl-sqlite - A simple boilerplate that builds an Electron app with SBCL and SQLite3 embedded
quilc - The optimizing Quil compiler.
weblocks - This fork was created to experiment with some refactorings. They are collected in branch "reblocks".
wisp - A lisp👽 written in C++
kons-9 - Common Lisp 3D Graphics Project
sb-jonesforth - 64-bit jonesforth using the SBCL assembler