Stream: ideas

Topic: Letting the platform decide where to show errors


view this post on Zulip Jasper Woudenberg (Sep 09 2026 at 17:09):

I'm working on a static site generator platform, Jay. When ran, Jay starts a development server showing the current site. Any changes to source code will cause a reload of this site.

When working with a static site generator I typically have three windows open:

  1. My editor, for making changes to source files
  2. The browser preview of the site
  3. My terminal, for showing build errors

For Jay I'd love to combine (2) and (3) by showing Roc compiler warnings, errors, and ideally test results in the browser preview. That way you only need two windows open instead of three, which I think is a pretty big improvement in UX: two windows typically fit side-by-side on a screen, but not three.

I wonder how well this idea generalizes to other types of platform, and whether Roc can/should support platforms running "headlessly", i.e. in the background, showing compiler output through some other channel.

(split out from #beginners > Hook for hot reload )

view this post on Zulip Richard Feldman (Sep 09 2026 at 20:25):

yeah I definitely like this idea! (for sometime after 0.1.0)

view this post on Zulip Richard Feldman (Sep 09 2026 at 20:26):

this was something I appreciated about Rails - showing errors right there in the browser instead of a blank page and needing to go back to the terminal to see it


Last updated: Sep 24 2026 at 15:59 UTC