On Mon, Dec 17, 2018 at 06:11:09AM -0800, Jérôme Martin wrote: > I'm also occasionally writing posts about Racket on my blog. Only one is > public for now, and is a multi-parts tutorial about writing DSLs in Racket. > > I'm trying to summarize and reformulate some of the things I learned by > making small languages in Racket. If you already read Beautiful Racket, I > guess there's nothing new to learn, because I'm mostly targeting developers > not aware of lisp languages. > > You can find the first part here: > http://rilouw.eu/article/the-programming-language-of-your-dreams-part-1 > Feel free to contact me if you want to share some advice and feedback!
Definitely not ready yet. You've written a start to an exposition on how write a #lang module, and actually showed how to do it in an incremental way, testing and checking what you do while you do it. An exposition I'd very much like to read the rest of. I too have racket tweaks I'd like to implement. (1) You start out with an imaginary UI language (which hapens to look like XML; I noticed that!) and you seem to indicate that you're going to show how Racket can choke that down. (2) But all you do is show how you can, via your (incomplete) ui-lang.rkt module, get Racket to behave like Racket. This isn't likely to impress. Since I already know about Racket and appreciate it, I can appreciate what you've accomplished, and how this is a reasonable base for further development. But the non-Racket-initiate isn't going to get that. And he's likely not to get around to episode #2 of your exposition. (3) In the end, you present a different language from the one at the beginning -- something that's not XML. It might have been better not even to mention the XML version at the start, but instead mention the one you are actually going to implement. XML, for the reader you are targetting, is old-hat anyway. I'm not at all sure how to rewrite this in a style that is likely to grab and maintain the interest of the reader you are aiming for. Writing is *hard*. Maybe you need to use the textual freedom the web gives you and, early on, have links to the actual implementation details. Or mention the translation of this special-purpose language is. Or how it's executed. Or what the menus look like (a screen-shot, maybe?) Anywaay, I'd like to see the rest of what you're doing. Perhaps just email me the actual implementation code so I can look it over before you rewrite your short series of article. I'll be happy to provide prepublication critique of what you write -- what works for me, what doesn't work, and what I do and don't think will work for the intended audience. -- hendrik > > I'm not confident the article is worth a post on HN for now, and I don't > know if my Racket server will sustain a mention on HN anyway, but if you > feel it's worth posting, feel free to do so. > > On Monday, December 17, 2018 at 2:30:55 AM UTC+1, Alex Harsanyi wrote: > > > > > > > > On Sunday, December 16, 2018 at 12:48:09 AM UTC+8, Peter Schmiedeskamp > > wrote: > >> > >> I’m probably guilty of already being part of this task-force. To add, I > >> wonder if there’d be value in some longer, blog-form replies to > >> interesting > >> HackerNews queries. > >> > >> For example, someone was extolling the virtues of some new system for > >> building and packaging simple GUI apps for Linux using Python. I’ve poked > >> around with the GUI and packaging facilities of Racket enough to feel like > >> Racket has a pretty good story to tell, at least for smaller > >> cross-platform > >> apps. A short blog showing the end-to-end creation of a small GUI app, > >> with > >> emphasis on showing the symbiosis of the GUI library and the excellent > >> raco > >> packaging and distribution facilities would be a great “reply” to such an > >> article on HN. > > > > > >> I wonder if there's a way that these use cases could at least be > >> collected... maybe as an RFB—Request For Blog. Time is always at a > >> premium, > >> but I could imagine picking off a blog post here and there even though I’m > >> a decidedly rank novice Racketeer. > >> > >> Maybe there’s already a list somewhere? Maybe RFBs could be a section of > >> the Racket Blog? > >> > > > > > > I have written a few blog posts on Racket GUI topics and I have a few more > > planned. They cover some more advanced uses of the GUI library -- I think > > the basics are already well documented. You can find them here: > > > > https://alex-hhh.github.io/tags/racket.html > > > > Alex. > > > > > > -- > You received this message because you are subscribed to the Google Groups > "Racket Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to racket-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
