Hacker News Reader

Comment by davidgerard | Hacker News Reader

I know exactly what you mean. Approximately everyone uses Inkscape in practice, but I too have had occasion to go into gvim and edit the Inkscape SVG by hand. I will say that it really helps to know what's going on, but having to is less than ideal.

("approximately everyone" to the point where Wikimedia occasionally considers just using Inkscape-as-a-service as the SVG renderer instead of rsvg, for best quirk-compatibility.)

View on HN

Right!? I have another "fun" story, where I found using SVGs a bittersweet experience. The firm I was interning this summer had a third party project of extracting waveform data in PDFs generated from ECG machines. Since parsing PDFs are another horrible experience, I used Inkscape to generate SVGs, and then used XPaths to parse the SVG's XML to get the data. All was good except that the XML tree was ~30-40 nodes deep at places.

I do wish that XML based formats were more deterministic to generate. Order should matter, however, I have seen several tools generating something that looks like this:

    <foo transform="translateX(10)">
      <bar transform="translateX(-10)">
        <...>

Inkscape has less than ideal UX on Mac though, which is why I use Sketch.

I couldn't get Inkscape to work on Mac at all.

I used Inkscape recently, and found it quite a nightmare to use, even if its UI reminded me of Corel Draw quite a bit.

That's what I get for spending like a decade primarily using Photoshop, I suppose.

Inkscape is defiantly software where reading the manual is a good idea. I tried to use it with out doing so, and found it unusable.

It is impossible to use Inkscape without running through at least some of the tutorials. Once you have a good conceptual understanding and have found some of the stupid bits that make no sense (what, you expected "Object Properties ..." to contain, ooh I dunno, properties of the object?) it's entirely suited to doing proper work. But no, its interface is very bad on discoverability.

rsvg has had a bunch of annoying bugs and in general seems to be further behind in terms of sorted compliance and feature support. When I was creating SVGs for Wikimedia Commons I had to work around a number of rendering bugs. And I didn't even use Inkscape, I wrote SVG by hand.

In contrast, the lead developer of Inkscape is active both in code and on the SVG specification mailing list, oftentimes implementing new features ahead of time to see how well they fit into SVG and where the spec might still need to be changed.

In practice, when valuing spec compliance and feature support, Batik and Inkscape are the only sensible options. This has nothing to do with quirk compatibility.

Reply on news.ycombinator.com