One of the issues with the #REPL (and #emacs which is just a great big text-oriented repl) is that it is additive in nature; it usually takes major effort or a restart to REMOVE things once they've been added (thinking on plugins which modify app state). #Clojure
> Unfortunately, most people seem to have taken the wrong lesson from Rust. They see all of this business with lifetimes and ownership as a dirty mess that Rust has had to adopt because it wanted to avoid garbage collection. But this is completely backwards! Rust adopted rules around shared mutable state and this enabled it to avoid garbage collection. These rules are a good idea regardless.
Yes, so much this! I'm using #Rust not because I'm building low-level resource constrained systems (far from it) but because it allows for local reasoning about state. Paired with the ML inspired syntax that makes pattern matching easy this leads to far more reliable programs.
This is also why I like #Clojure so much. Clojure's refs / atoms /agents allow for scoping mutability in an otherwise purely functional system. Scratch for the same itch. But Rust's compile time checking avoids pushing issues into the runtime, increasing reliability and hugely reduces time needed for debugging. The trade off here is no interactive / live development.
After 10 years of commercial experience in #cpp I think I’m ready for a new chapter. I have played around with #rust#golang#zig and #clojure but most job offers that I see are for people with at least X years of commercial experience in this exact languages. Do you have any hints how to approach this? I would think that my previous experience as a #software engineer would matter. Especially since I do not expect to move to another senior role, I’m checking junior positions too. #jobsearch
Another example that was created with Jean. Jean is a live coding software for visuals and sound. This example was recorded without sound and without the #Clojure code. Images in the background by Joseph Constantine Stadler (1780–1812).
I have a friend who is most of the way done making an open source app that handles supply chain interactions without centralization. It uses a SSB backend so there aren’t any central servers and it’s not crypto. There’s no angle for him to get rich doing this, it’s just a good idea that he wants to exist in the world. Written in Clojure.
OK, then, new GitHub repository, simulated-genetics, looking at the problem of generating thousands of character models for games, while ensuring that characters who are supposed to be related to one another have similar appearance.
This is very, very pre-alpha, but far enough along to be interesting.
I'm using #Emacs since 2008, I've been maintaining an Emacs bundle since 2010 (currently working on v4.1). Emacs is genuinely one of the programs that still gives me the goosebumps. After all these years, I still learn new stuff about it that blows my mind.
@lxsameer that's cool! I recently started using #emacs because I found file navigation annoying in other IDEs. I know how to touch type, so now I literally just have to type in what I want (with all the autocompletion benefits just like a shell). Still learning the basics but finding even that awesome!
By the way, I've been programming a bit of #Clojure too, although right now I prefer the #clisp vibes :clojure: :lisp:
The available open source libraries for generating human models (MakeHuman, ManuelBastioniLab) appear to be written in #Python. I need something like this, but I'm working primarily in #Clojure. I'm wondering whether it would be easier to load one of the existing libraries into Jython and try to call that from #Clojure, or just to bite the bullet and build my own from scratch.
one thing that I appreciate in #fennel is the ability to learn from the history of lisps
#clojure made a big splash and gathered criticism from the Old Guard of lispers by using parens a lot more sparingly than Common Lisp or Scheme; for example let bindings are done inside square brackets instead of a double-layer of parens:
(let [x 1 y 2] ...)
vs
(let ((x 1) (y 2)) ...)
apart from just being tidier, this had the benefit of greater consistency: in Clojure, when you saw an open paren, it usually meant a call to a function or macro, instead of ... some other structure in the language
however, Clojure still had plenty of exceptions to this; I think last I counted there were 7 or 8 distinct things an open paren could mean
in Fennel, we decided that wasn't what we wanted; parens always mean a call to a function/macro ... or in a binding context it could mean binding multiple values:
<sigh>
And when I install the latest Gradle, I still get failures, because the Gradle scripts of the current version of jMonkeyEngine (which is what I'm trying to build) are too modern for Gradle 4.4.1 but too old for Gradle 8.7.
Now I remember why I do everything in #Clojure these days: very stable APIs!
In my ignorance, I didn't have faith in #LISP because it is a very old programming language, and in my circle of acquaintances and friends, I never saw anyone using it. Behold, as almost always, I was wrong!!! What magnificent language. It's no wonder that #Clojure is there!
@simon_brooke Hey buddy, checked out #Scheme/#Scsh yesterday, super intriguing stuff. Actually, I've been digging into #Lisp and its dialects lately. Got curious about why there are so many dialects, you know?
Recently dabbled in #Clojure, which got me looking at Lisp in a new light. Unlike #Haskell, which is awesome for sure, #Lisp has been out of academia and in the market for quite a while... found it pretty cool.