On Sat, Jan 13, 2018 at 1:58 PM, Matthew Butterick <[email protected]> wrote:
> > > On Jan 13, 2018, at 6:16 AM, Joel McCracken <[email protected]> > wrote: > > > > Nice! I was planning on doing something similar for my own blog/personal > site. Is the source available anywhere so I can examine some of your > techniques? I do not see it on you github. > > > Because I had no idea what I was doing, the server-side code is pretty > sloppy. So I'm not in a rush to post it. At least until it reflects better > on Racket ;) If you want to know how certain things work I can describe the > approach. > No worries. I'll ask for tips if/when I get around to it then. > Barring that, I would imagine having pollen be usable as a > "library"/plugin application for the racket web server would be another way > to go. This would be akin to the notions that I know Django and Rails both > have (or had in the past, I have stopped paying attention to each > community). > > > Perhaps. My impression — dim, as I also steer clear of the web-dev world, > lest my face melt off — was that server-side page generation had fallen out > of vogue in favor of async HTTP requests. > It depend upon what you're building. If it is not an "application" it is probably easier (and faster to render) to use server page gen. If you have heard the term "isomorphic web applications", this refers to having the ability to generate a website's DOM on the server and the client. This makes the site content accessible to anyone not running JavaScript (especially webcrawlers) and faster to render on page load. -- You received this message because you are subscribed to the Google Groups "Pollen" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
