On 21 April 2017 at 21:26, Steve Litt <slitt@...2357...> wrote:

> I'm very satified with Inkscape.

It's a great app.

To your points on my suggestions for new stuff in Inkscape: It's an old road, well worn. I don't wanna.

Bottom line is I don't think there's a good reason that software should be a false dilemma. There're ways to make it suit *many* kinds of minds. Look at what Firefox does with Addons, for example.

> "Right there in the app" is the entire issue I have with all of this.
> You have a perfectly good SVG file that secondary programs can
> manipulate to their heart's content. The minute Inscape becomes an SVG
> superset or SVG-noncompliant, this very valuable feature goes away.

I get it, and here's the thing: SVG, it's in serious trouble; fatal trouble if recent articles are to be heard. The Walking Doctype.

> > I think Inkscape could have, by now, matched what Flash, Freehand and
> > Corel et al. had 20 years ago!
>
> That 20 years point is a bit of an ad-hominem, don't you think?

Not intended as such.

My truth: I wish I could be as productive in design as I was in the late 90's. Linux has been my life for 17 years, but I could not continue in the design world because I'd left Windows, Adobe, yadda yadda... etc.

I have made-do. I have scripted and written Python apps. I have done All The Things to massage vectors into pixels and back. To squeeze HTML and ebooks and PDFs and images out of the stones in my $PATH. It's fun, but time spent there is time *not* spent designing artwork for clients.


> Yeah. That's why I can put an Inkscape-created SVG on
> Troubleshooters.Com, and anybody with a halfway modern browser can see
> it. These days I don't even use .png as a fallback: Everyone can read
> my Inkscape-authored graphics. SVG is THE standard for EPUB images.

Sure. I agree. The core of SVG that is respected by browsers (into the future) should be sacrosanct and Inkscape is unlikey to throw all that code out. Software accrues thus.

/d