No, the pro pipeline is PDF. You might argue that, if you are risk averse, you only trust Adobe’s tools to produce optimal PDF. This is of course Adobe’s moat. But Scribus’ export to pdf is excellent, in a pro setting

Thats not what I am talking about. Your PDF might be identical but printers often require either their specific InDesign settings or straight up packaged InDesign project as source for printing (they used to require postscript lol).

I am not gonna argue if they are correct or not but the reality i've experienced is that at minimum socially the printing industry is married to InDesign.

It seems there are multiple initiatives. Have you also read this one?

https://iabtechlab.com/announcing-content-monetization-proto...

Maybe people have agendas, or maybe they have different perspectives that should be reconciled?

This approach builds on the persisted queries approach: https://docs.wundergraph.com/docs/features/graphql-to-json-r...

It gives you all the benefits of GraphQL during development while in production you’re only dealing with JSON-RPC

There is: https://rxdb.info/replication-graphql.html

WebAssembly (Wasm) executables compiled from Go source code can be interactively debugged in Chrome DevTools

Has the issue with juju on LXC not surviving reboots been fixed?

LXC support in the latest Go juju landed earlier this week, and reboot persistence landed yesterday. So, yes, but it's still very new.

OK, thanks. This was a deal break for us a year ago. The issue was even partly solved and with a few hacks juju did survive reboots, but it was later on removed.