6 ms·
CIEL Is an Extended Lisp
- draven 2y agoLooks like SBCL plus libraries. The author, vindarel, is here on HN.
- vindarel 2y agoHi o/ Hopefully the goal of CIEL is well explained. I use it daily (with the core image, in my editor), I ship products with it. It saves me a load of time, when I start a new project, when I need to interact with the outside world, when I want to write a little something and ship it on the server without Python's mess, etc. Speaking of which, Django is of course difficult to replace, but I started an automatic DB dashboard for CRUD operations, something's on the way (unreleased). I integrated CL step by step for my clients' work, and CIEL is another means to this end. To use CL, for real. None of my projects need CL's superpowers, but I want them for development, deployment and monitoring! --- Today I fixed a few issues and released a v0.2: https://github.com/ciel-lang/CIEL/releases/tag/v02 https://github.com/ciel-lang/CIEL/releases/tag/v02 The key point is that CIEL should be much easier to install, specially on Mac. We now rely on many less system dependencies. If you find out that CIEL is still difficult to install on your platform, don't hesitate to send details on an issue. Thanks in advance. --- TLDR; May CIEL ease and soften your CL journey. ps: you have no idea how much time it took me to discover certain things! Now you have them here, ready, packaged :-]
- andxor 2y agoI absolutely love this and will be using it extensively for scripts. I was wondering - do you also use it for larger (multi-file) projects? Any recommendations on how to structure those when using CIEL?
- vindarel 2y agoAwesome, thanks for the feedback. Yes I do, of course, and I actually use it nearly exclusively for multi-file projects: I don't write short scripts everyday, but I have bigger projects that need more features. The one I am on: extract data from an existing DB, format it, save it to a csv, send it with SFTP. I build a binary and send it to my servers. For this I use :ciel as a dependency, I use a typical project structure: a system definition in an .asd file (that :depends-on (:ciel)), and sources. I also start my editor with CIEL's core image. I build a binary the usual way out of this, I don't run this app as a script, specially if I added a couple dependencies. But that's OK, I benefited from CIEL during development. I recommend to start with a file packages.lisp that defines 1 (one) package for the whole application, to use it across multiple files, until it makes sense to create a second package. Otherwise, one can easily loose oneself into export & import symbols hell, specially when we are new at it. So I don't recommend the "one-package-per-file" approach. Hopefully the Cookbook gets you covered if you need examples. Happy real-world lisping!
- qup 2y agoCan you easily compile a binary? (I assume you just use standard CL methods?) > [CIEL custom REPL ] has a shell pass-through: try !ls (available in the ciel-user package) That's a kickass feature.
- amelius 2y agoWhat's wrong with Ctrl+Z?
- zipy124 2y agoForgive me if I'm wrong but I thought that was a fairly standard thing? The Ipython kernel uses exactly the same format, or you can go for a full shell and use xonsh. Or is python the odd one out in its REPL implementations here? I'm only familiar with python and e-lisp for REPL's.
- qup 2y ago> CIEL's REPL is more user friendly than the default SBCL one. In particular: > ... > * it has a shell pass-through: try !ls (available in the ciel-user package) It was specifically mentioned as a reason why CIEL is better. But I don't use enough languages to know overall, sorry.
- 2y ago
- Y_Y 2y agoI'd love to see one of these revitalizations of CL that gets rid of the ALLCAPS. I know it's a small aesthetic thing but it drives me crazy. I found a snippet somewhere that messes with string interning and so symbols don't instantly get capitalized, but there's still way too much shouting.
- aeneasmackenzie 2y agoYou're looking for (setq *print-case* :downcase), no need to mess with the reader.
- perihelions 2y ago(You can put this in ~/.sbclrc or your implementation's equivalent dot file!) (Tangentially: I've encountered Common Lisp libraries in that wild that actually break if you do this, highly surprising bugs where the author was doing something too-clever with symbols and compared their representation against hard-coded strings, such that changing your *IDE's default print case* had the effect of breaking a very low-level library. This isn't important to anyone else here; I just wanted to vent. I have so much programming pain that only I know about and no one else in the world shares).
- kagevf 2y agoCL is case-sensitive, but it handles things so you typically don't have to be aware of it. I don't think I'm smart enough to try to do something clever on top of that, so I hope I can avoid your pain.
- tmtvl 2y ago> compared their representation against hard-coded strings Ah, used string= instead of string-equal, did they? Simple mistake to make, not keeping CL being case-insensitive in mind.
- martinflack 2y agoI always liked it. I type lowercase, the computer speaks back uppercase. We know who said what. It's also nostalgia for BASIC. ;-)
- anothername12 2y agoThis is great. I personally have an image with Alexandria, Serapeum, Dexador, Bordeaux Threads, some JSON stuff, but it might be handy to have something others use as a similar target. Probably stands a better chance of success than the over-pontificated CDR proposals, and CL21 which preceded it. Curious if there’s a bunch of reader macros set up by default?
- aidenn0 2y agoI did a quick search of the code, and only clesh[1] seems to be enabled by default for shelling out from the REPL. 1: https://github.com/Neronus/Clesh https://github.com/Neronus/Clesh
- vindarel 2y agoIt's enabled by default for the terminal repl, but not in the ciel-user package, that we would use on our editor's REPL. In that case we can enable it with CIEL-USER> (enable-shell-passthrough #<NAMED-READTABLE CLESH:SYNTAX {1003EE7F13}> CIEL-USER> ! ls
- vindarel 2y agoOnly one is enabled in the terminal repl, but none when we use ciel as a regular Lisp library. We don't want to mess with the readtables by default. (see below to enable the shell passthrough in your editor's REPL)
- Blackthorn 2y agoHaving a standard set ofwell documented things ready to go as if they were part of the core language, all with a single snazzy name, is soo important. I love this; Maybe it can become the new standard target. All it needs now is a good mascot or logo.
- notfed 2y agoWhere is this documentation? Honestly I don't see much here. I'd call this a readme, not documentation.
- Blackthorn 2y agoIt's linked on the GitHub front page, for some reason it's not in this link at all.
- vindarel 2y agoHow so?? You should have a sidebar with menu entries. Try on http://ciel-lang.org/#/libraries http://ciel-lang.org/#/libraries oh, the sidebar disappears quickly when we scroll and it disappears when we click on "show me"… not great.
- Blackthorn 2y agoI was on mobile when I looked and I never saw the sidebar. Might be something that needs fixing. Love the project regardless.
- dleslie 2y agoThere's a hamburger menu on the bottom left.
- the-smug-one 2y agoHey vindarel, I don't get it: ciel-user> (disassemble #'(lambda (x) (+ x 2))) Error: Missing closing quotation in string (line 1): (disassemble #'(lambda (x) (+ x 2))) ciel-user> (disassemble (lambda (x) (+ x 2))) ; disassembly for (LAMBDA (X)) ; Size: 35 bytes. Origin: #x54354A64 ; (LAMBDA (X)
- tonetheman 2y agoThis seems really useful! Good work
- vindarel 2y agoThanks! Encouraging feedback is my nectar.
- a012 2y agoIt looks fun to learn it for scripting. I often use Python to manipulate JSON and YAML and with Python requests library, this seems like a fit
- aidenn0 2y agoCL is better than Python for very short scripts that will be called repeatedly (e.g. from a makefile), since a python already has a slower startup time than a CL binary, and for every import you add it gets even slower.
- beders 2y agoNice to see that the approach taken by Babashka (https://babashka.org/ https://babashka.org/) is now also available in the CommonLisp world. Good stuff!
- rootnod3 2y agoWatching it on Safari gives me the same Javascript warning. No extensions loaded. Otherwise, checked with chrome, that looks like exactly what I wanna use. The CL sodlib is a bit overloaded already, but if you wanna go batteries included, it was definitely missing stuff like Alexandria and Bordeaux etc, so I dig this choice. Brings a sense of "best practices" or standardization to the slightly fractured CL ecosystem.
- mgdev 2y agoAhh, the siren song of Lisp I wrote Lisp (Clojure) professionally for several years. It was the most fun I ever had. My only problem was it was an ongoing battle to convince people - especially management - that I wasn't crazy. Sure, I was crazy-productive, but they also thought that there was some nutjob in the corner that was quietly adding risk to the business. If someone could give me the ergonomics of Clojure, but without the JVM and the ability to easily target 1/ native (incl easy bidirectional C iterop), 2/ wasm, and 3/ support both in aot and runtime + JIT modes, I would switch in a heartbeat. Is that too much to ask?
- masijo 2y ago>If someone could give me the ergonomics of Clojure, but without the JVM and the ability to easily target 1/ native (incl easy bidirectional C iterop), 2/ wasm, and 3/ support both in aot and runtime + JIT modes, I would switch in a heartbeat. Might want to look at Jank (https://jank-lang.org/ https://jank-lang.org/, https://github.com/jank-lang/jank https://github.com/jank-lang/jank). It's still in it's early stages but it's basically all you're hoping for!
- mgdev 2y agoWill check it out!
- rootnod3 2y agoThe name might be hard to push to management, but I love that it is s-expr based. I'll definitely check it out, but if you don't mind me asking: how good is the REPL side on Jank? If it is remotely close to SBCL, then I might become a fan.
- Jeaye 2y agojank will have full nREPL support, so the REPL story should be at parity with Clojure. I'm working on the nREPL server now We're JIT compiling C++ code, so there are indeed more dragons.
- whartung 2y agoI don't consider it an extended Lisp, rather I just consider it a "batteries included", bundled library distribution of Lisp. Common Lisp is still Common Lisp. And I know it's a slippery slope. Someone posted (here?) a list of the language changes to Java over the years. And for something like Java, you "have" to "change the language" to get the results they wanted. Much of these changes could not have been done with just more classes in the JRE distributions. Whereas with CL, most of those things could have been done natively with just macros and functions, rather than having to update the core. Of course, this is the Scheme story from day one, just with a much smaller core. But CL, due to the happenstance of the time of uniting several commercial efforts under one banner, has a larger core, but also, by definition, more opportunity for the actual compiler to be "better" with the higher level constructs it works with. Contrived example being that Lisp "knows" about Structs and CLOS, whereas while you can add Structs (records) to Scheme, at a Scheme level you can only reduce them to the given Scheme primitives (vectors or lists), when the compiler finally sees the result, all it will see is a vector or list, with no knowledge of it actually being a struct (and thus can't potentially optimized for it). If you want "native" structs, you need to actually extend the particular Scheme compiler. So, anyway, the point being this is a nice package of libraries (it is, really, quite nice), all bundled into a single image. Batteries included. But it's still CL at its core, there's nothing necessarily new there.
- gus_massa 2y ago> Contrived example being that Lisp "knows" about Structs and CLOS, whereas while you can add Structs (records) to Scheme, at a Scheme level you can only reduce them to the given Scheme primitives (vectors or lists), when the compiler finally sees the result, all it will see is a vector or list, with no knowledge of it actually being a struct (and thus can't potentially optimized for it). I don't know every single implementation of Scheme, but at least the Chez Scheme compiler has a lot of special code for records. The compiler sees them as records, tries to inline as many getters and setters as possible, and has low level support for the tree of subrecords and I may be missing a few more tricks. You can go to https://github.com/cisco/ChezScheme/blob/main/s/cp0.ss https://github.com/cisco/ChezScheme/blob/main/s/cp0.ss and Ctr+F record . For example https://github.com/cisco/ChezScheme/blob/main/s/cp0.ss#L3816-L3822 https://github.com/cisco/ChezScheme/blob/main/s/cp0.ss#L3816... The old implementation of Racket also had some tricks, but now the structs are transformed to Chez Scheme records.
- breck 2y agoLooks different than Ciel, another Lisp from 2010 (https://pldb.io/concepts/ciel.html https://pldb.io/concepts/ciel.html), by Ron Garret, rocket scientist (https://flownet.com/ron/ https://flownet.com/ron/).
- 082349872349872 2y agoEveryone has their own paradis.
- floxy 2y agoSince everyone likes something just a wee bit different, I'd also like to see something where most of the functions in :COMMON-LISP are made generic, so you can overload '+, etc. to work on vectors, etc.. Obviously you can do it yourself on a per-project basis.
- Blackthorn 2y agoThat's part of Ciel!
- floxy 2y agoThat's great! Is that described in the documentation? I can't seem to find it.
- vindarel 2y agogood catch! It is only mentioned at the end of the install section: http://ciel-lang.org/#/install?id=use-in-the-repl-and-in-new-packages http://ciel-lang.org/#/install?id=use-in-the-repl-and-in-new... This feature is based on generic-cl, a high quality library. To be franc, I didn't test much the integration with generic-cl, it's on the todo list. When I started out, I was carving for a library like this. Now, I don't feel the need anymore.
- tmtvl 2y agoYou mean something like generic-cl? https://github.com/alex-gutev/generic-cl https://github.com/alex-gutev/generic-cl
- BoingBoomTschak 2y agoI think https://github.com/CodyReichert/awesome-cl https://github.com/CodyReichert/awesome-cl with a bit more trimming/tagging and interactivity (e.g. show all "stars") to empower users to explore the ecosystem and build their own image is a better way. There should also be a large disclaimer saying "Consider disregarding portability in favour of SBCL to get a more modern experience".
- begueradj 2y ago"Ciel" means "sky", in French language.
- medo-bear 2y agoHow come Ironclad is not included?
- michael-ax 2y agoCould this get a wrapper for building ncurses & sdl cores so that maybe one day lem could run right on top of ciel and a true lisp environment could emerge? https://news.ycombinator.com/item?id=41357409 https://news.ycombinator.com/item?id=41357409
- lsh0 2y agoI like to bring up Joker (https://github.com/candid82/joker https://github.com/candid82/joker) whenever there is a discussion of some lisp that is fast and convenient. Clojure syntax implemented in Go. I'm not affiliated I just think it's brilliant. CEIL's example in Joker: (prn {:a 1 :b 2 :c 3}) Gist for downloading, installing and executing the above example: https://gist.github.com/lsh-0/f7df23777ef35a8cc3d85e1dcbf0eb3d https://gist.github.com/lsh-0/f7df23777ef35a8cc3d85e1dcbf0eb... Executing script took 2.1s overall. Execution of example took 0.007s.
- fhd2 2y agoLove the approach! I was ready to see "yet another Lisp", which is cool, but not something I'd readily use. Expanding and improving things that already exist can be harder and less fun than starting a fresh thing, but it's infinitely more valuable. I already use Common Lisp (it's quirky, but also incredibly robust, productive and fast), and this seems to make it a little less quirky, especially for newcomers and smaller projects.
- deleted 2y ago[deleted]
- pizza 2y agooff-topic: is there anything that aims to be a 'universal stdlib'? Something that lets you write eg some small spec about how your language operates and then it lets you add a fullblown polyglot batteries-included stdlib to your language? Would be a dream for language devs I imagine. I guess you could go pretty far by just linking to some C library probably though.