Add a "strengths and weaknesses" section?

[etiennebacher]

Hello @JohnCoene, I think that one thing that is missing in your documentation is a section about comparing strengths and weaknesses of ambiorix and shiny. As someone who first discovered R, then shiny, and then the world of web development (probably as several shiny users), I don't know what express.js is and I don't know why it is useful.

As you say in this section:

Designing applications will, in all likelihood, always be faster with Shiny.

As a reader, when I see this, my reaction is more or less: then why should I use ambiorix? I know that you show some examples in the docs, but the syntax is very different from shiny and it seems quite complicated. I think there should be a section where you show/explain common shiny problems, and how ambiorix makes it easier to solve them. Also, as a side question, is ambiorix a lot different than brochure?

I don't want this to sound as a criticism, I'm just trying to figure out if I should learn more about express.js and ambiorix. Thanks again for all this open source collection of tools! (PS: love the docs and the pictures used)

[JohnCoene]

(not ignoring this, just having a difficult time putting it into writing)

[matteckman]

I'm a full-stack dev working at a data science agency, and Shiny has been hard for me to get into since I don't know R. R itself isn't too bad, but learning R and the Shiny way of doing things without a ton of time to do that learning has been too steep of a learning curve. Our Shiny expert left recently, and I'm sweating bullets hoping nothing breaks. So I'm putting together a new stack using handcrafted HTML/TailwindCSS + Ambiorix + HTMX, which is really working well so far. It's super simple to understand which I'm convinced will make everyone here more productive.

If I had to summarize my thoughts on Shiny, it's great to start out with, but over time everything gets harder the bigger and more complex the application becomes.