[stavros]

I really like these presentation-as-code tools in principle, but in practice I find that they can be a bit limiting. However, I haven't used them enough for this to be anything more than a general sense. Does anyone have an opinion on this?

[yencabulator]

You could pick an ecosystem with more power to control the finer details if and when that's needed. Typst is a LaTeX replacement with a syntax sort of in the markdown family of syntaxes (https://typst.app/docs/tutorial/writing-in-typst/), but fully programmable and with nice visualization options.

https://typst.app/universe/search/?category=presentation

e.g. https://typst.app/universe/package/touying

Gets you powerful "frame by frame animated" slides when you need it, like this tracking program execution: https://raw.githubusercontent.com/typst/packages/main/packag...

Gets you decent diagramming e.g. https://typst.app/universe/package/fletcher/

[NicuCalcea]

I rarely need anything more than bullet points or an image in my presentations, so I don't find them limiting. However, most of these allow arbitrary HTML/JS/CSS, so I wouldn't say they're that limiting. I occasionally include iframes, for example.

The big downside for me is you don't have easy pixel-level control over layout like you do in PowerPoint or Google Slides. Even changing font size, for example, is a little clunkier. I hear some people also miss being able to draw diagrams and flowcharts.

[bluGill]

Limits can be good. I - like most people put too much on slides. Simple slides are good.

the reason complex tools can do so much as each feature is needed in some obscure case. However because it is there presenters are tempted to use it when they should not.

[ghaff]

I tried out reveal.js for a while but, especially with Google Slides coming in, I found it limiting and increasingly the collaboration component of Google Slides was becoming more and more important to me at the time.