This article lists a large amount of pitfalls when trying to do just that: https://fasterthanli.me/articles/just-paying-figma-15-dollar...
And this isn't some esoteric use case used as an excuse. The core need the author has is "export my diagram to SVG and have it render the same in all browsers".
I've used several tools over the years and am not afraid to jump into a new UI or workflow, but have come to believe that's an exception and probably driven by the dev part of my brain.
It could be that much of design tool "output" is source-of-falsity, i.e. experiments, drafts, non-production work that is left in an ideation stage. For stuff like that, there's more breathing room for less-sophisticated products to shine.
What they don’t have is the inertia of Figma and being as-good-as or maybe a little better isn’t enough to get the traction they need.
Based on the linked article's description it's much worse.
In browsers that’s not a big problem generally.
For other platforms, what would happen if OP printed to PDF from the browser instead of exporting the SVG to PDF with a separate program?
> No you don't.
> Cool, back to Figma.