Jens Halm

That's kind of cool how quickly you found two workarounds for the problem. I'm always a little afraid new developers get lost in the huge API surface of Laika. From...

Many thanks for authoring this proposal. While I generally think this presents an interesting and exciting opportunity, I also have quite a number of doubts, and they are less about...

Thank you for providing all these pointers. I'll comment on two of them here. > > one or more additional admin-level maintainers who can merge PRs and cut releases >...

> > I just have no idea what this means in practical terms, so someone would need to brief me a bit on this... > > @valencik can expand more,...

Thank you for the pointers, I'll probably write up a little proposal sometime in the coming weeks when I return to spending a bit more time on this project.

Welcome, and many thanks for looking into this. However, before you spend any more time on this I'd like to point you to the fairly recent debate in #360, which...

> > The short summary is that we established that increasing the platform support for Laika is valuable only if we also look into developing a CLI application > >...

> > Where do you see a use case for just having `laika-core` on Native? > > The same use-cases as on JVM (minus the sbt plugin) e.g. server-side rendering...

> Considering the above, it's a good question :) if you intend to keep Scala.js since it's already here, then adding Scala Native is probably straightforward. Of course, we have...

Writing back in markup format is currently not possible. I had it on the back of my mind, but it's not on the road map yet. But when I thought...