[pollen] Why is render-from-source-or-output-path function quicker than get-source and then render?

So pollen-rock used to use the following code logic to decide whether to render a pollen source when a HTTP request coming in (let ((pollen-source (get-source filepath))) (when pollen-source (render-to-file-if-needed pollen-source)) (next-dispatcher))) For small projects, this wo

Re: [pollen] Why is render-from-source-or-output-path function quicker than get-source and then render?

> On Feb 9, 2018, at 10:55 AM, Junsong Li wrote: > I noticed pollen server is using a function called > render-from-source-or-output-path , which is defined here > https://github.com/mbutterick/pollen/blob/5f338b5ecf9bbca7d7a44ca0e721b22a6cf8210a/pollen/render.rkt#L71 > > And once I switch to t

Re: [pollen] Why is render-from-source-or-output-path function quicker than get-source and then render?

I think I might have hit a bug in racket serve/servlet. The actual blocking point is the pollen get-source. It runs only half way through for certain js files (it detects markup, markdown, and are blocked before null-source/scribble-source/...), and running get-source alone never had the issue.