Gregory's Server@daviwil In my very subjective opinion, one of the problems would be choice paralysis and kinda related to that the lack of enough standardisation.
It's nice that I can read files in a standard way, but that's not everything one has to do, and if I want to call a library or use any of the SRFIs implementations decided to replace with their own stuff then my code is just forever locked in. Which isn't bad per-se but seems to cause code to be developed for an implementation rather than just Scheme
|
Top-level
5 comments
 @michal_atlas @daviwil you can use r7rs by starting guile with --r7rs, or in the repl with Guile's r7rs and r6rs support is pretty good, but not complete, and there are some tiny divergences you have to figure out. But its good enough to build akku. @michal_atlas @daviwil (if you're interested in r7rs in particular, which is generally pretty portable, I'd recommend going with an r7rs implementation like Chibi, and using akku to sort out the cross-implementation compatibility for you)  @rml @michal_atlas @daviwil we're implementing r7rs small for the wasm compiler so I wonder if any of that work will fill in some gaps. @rml @daviwil Yessss, r7rs in general is awesome and something I'm massively looking forward to getting more widespread and I'm very grateful for its existence and all the work people pour into it. I was just voicing my subjective view on why it might be overwhelming for newcomers right now. And I also have to finally check out this akku thing I keep hearing about, thank you for reminding me. |
@daviwil And in the end for example I have the choice between learning Common Lisp and where the quirks lie, or the absolutely brilliant but separate languages/ways of doing stuff in Guile, Racket, Chez, ...
That's my feeling and I am ofc using Guile right now for many of my things, it was a strange choice to make in the beginning and hadn't it been for Guix I wouldn't have been able to make it I think.