@ross From Wikipedia:
> Scheme has a diverse user base due to its compactness and elegance, but its minimalist philosophy has also caused wide divergence between practical implementations, so much that the Scheme Steering Committee calls it "the world's most unportable programming language" and "a family of dialects" rather than a single language. -- https://en.wikipedia.org/wiki/Scheme_(programming_language)
carbonated some lemon + lime juice and sweetened @mlemweb's and drank mine straight
It's... verrrrrrry tart
@cwebber I like seeing projects like this because Emac's greatest strength for experienced users is its biggest weakness for new users. I didn't feel like I got Emacs until I learned elisp and that is a hard sell.
Another memory from FOSDEM this year is finding out that @clacke's name is pronounced like CLOS, the Common Lisp Object System. Obviously the most obvious way to explain how to pronounce that name!
Now this looks promising re: "how could Guile have its equivalent of DrRacket?" https://git.elephly.net/?p=software/guile-studio.git;a=blob;f=README.org;hb=HEAD
Guile Studio aims to build a simplified configuration of emacs aimed at the Guile + Emacs newcomer, kind of how like Spacemacs makes Emacs accessible for Vim users. I hope it works!
@maloki Anyway, in order for such an org to work, it would have to have a plan for funding and governance from day 0 that informs the desired structure. I don't know what that would be. It wouldn't be easy to set up, I think.
@maloki I've long been interested in a hacker/community-oriented standards org. IETF is the closest we have, but isn't quite that. Though one thing the W3C does have is its patent non-aggression policy, and the reason that works is that it's able to bring a bunch of corporate participants to the table. I don't think a hacker standards org could do that. (There's also some government groups that will only accept work that come from "official" standards groups.)
Maybe it's still worth trying.
The problem with this kind of corporate sponsorship is it can allow for compromised positions that never would have been taken otherwise, like https://dustycloud.org/blog/drm-will-unravel-the-web/
A lot of people find out that the W3C's governance is fucked up and overly dependent on corporate sponsorship (and it is) and then assume that the WHATWG must be a better institution (it isn't).
WHATWG is, for the most part, a "what-the-major-browser-vendors-say/do-rules" org. And keep in mind, that's now just two organizations (Google and Mozilla). That's good reason for pause.
The WHATWG has dropped the useful and simple ABNF representation of URIs in favor of a much more complicated algorithm. An appeal for them to... not do that: https://www.more-magic.net/posts/an-appeal-to-whatwg-uri-spec.html
gruel intentions Show more
banana gruel (with rice and buckwheat) is cooking in the pressure cooker and I intend to eat it later
whether or not to split seems split, but I did know I was asking friends to help me paint this #bikeshed
Hey, help me out... I want the #Spritely Golem demo to be as understandable as possible. I know, I haven't written all the docs yet, but what's easier for you to read:
- All in one file, like this: https://gitlab.com/spritely/golem/blob/master/golem.rkt
- Split into multiple files: https://gitlab.com/spritely/golem/tree/breakup
Pls let me know! Your #bikeshed feedback appreciated!
I wasted a bunch of time on this, but I did figure out how to do it. The right way to do it:
- pages.rkt (the controllers) lazily imports the templates and routes. This file has to be lazily importing the others and not the reverse, because the controller functions are actually used to reverse look up the routes. Every template imported in pages.rkt unfortunately needs to be manually listed.
- routes.rkt imports pages.rkt directly
- templates.rkt imports pages.rkt and routes.rkt directly