Inkscape 1.1.1 Is Released
21–30 of 110 posts
Re: Inkscape 1.1.1 Is Released
#22I absolutely love this program. Few times per year I need a vector tool. After some toying with proprietary vector tools (Illustrator), I learned Inkscape (as it was readily available in my Linux envs). I never looked back. It does the job. I never have to look for cracked software in order to open my old files or use my acquired skills. It just works.
I just wish designers were more familiar with the SVG format and its caveats. Several times I've wanted to do some quick change in an SVG that was exported from Adobe Whatever and Inkscape was incapable of rendering it correctly, if at all. I'm pretty sure Adobe has been pushing the boundaries of SVG in the last years, while other tools stick to the basics.
The solution was Affinity Designer. Too bad, but at least it's an easy purchase rather than a subscription.
Re: Inkscape 1.1.1 Is Released
#23I love Inkscape, but really the performance in mac is completely insufficient, each action takes at least 1 second to load. Probably is not their fault or main target OS, but is so hard to find a free or open source alternative with the same functionality for mac.
Re: Inkscape 1.1.1 Is Released
#24Does anyone knows if it works fine on macOS yet?
I have been using Inkscape on mac for years now and never had problems.
Re: Inkscape 1.1.1 Is Released
#25Earlier quoted context omitted.
By "pushing the boundaries" do you mean "violating SVG standards" or is it the other editors who aren't keeping up with SVG2.0 etc?
If Adobe changes the spec, they can, simply by being the market leader (bit like Chrome is) Not nice, but there you have it. It would be great if there was an Adobe SVG format in those cases perhaps.
If you are going to even hint that an Adobe product produces non-compliant SVG, please detail your claim so others can assess it.
To not do so would be the first step towards a rumour, and might invite FUD that might devalue SVG’s status as an open standard supported enthusiastically in web and vector graphics ecosystems.
We don’t want that, do we?
Re: Inkscape 1.1.1 Is Released
#26I adore Inkscape. If you haven't tried it, painting with the marker tool and a pressure sensitive tablet is really fun. Drawn look but infinitely scalable. Good for "cell" style art.
Re: Inkscape 1.1.1 Is Released
#27Earlier quoted context omitted.
If Adobe changes the spec, they can, simply by being the market leader (bit like Chrome is) Not nice, but there you have it. It would be great if there was an Adobe SVG format in those cases perhaps.
Adobe is a W3C member and played a lead role in drafting the 1.0 spec, which was edited by Adobe’s Jon Ferrailo. If you are going to even hint that an Adobe product produces non-compliant SVG, please detail your claim so others can assess it. To not do so would be the first step towards a rumour, and might invite FUD that might devalue SVG’s status as an open standard supported enthusiastically in web and vector grap…
Re: Inkscape 1.1.1 Is Released
#28There are issues of course - memory leaks and odd GUI handling on Windows in particular - but I've had the same sort of issues with Adobe products as well.
A really awesome thing about Inkscape for me is how it uses standard SVG as its default file format. It makes a lot of sense and makes the raw artwork highly exportable and flexible.
Re: Inkscape 1.1.1 Is Released
#29I absolutely love this program. Few times per year I need a vector tool. After some toying with proprietary vector tools (Illustrator), I learned Inkscape (as it was readily available in my Linux envs). I never looked back. It does the job. I never have to look for cracked software in order to open my old files or use my acquired skills. It just works.
I mostly agree, though for me it's 'winget install inkscape' right now :-)
Re: Inkscape 1.1.1 Is Released
#30Earlier quoted context omitted.
I run an older 2012 Mac and don’t experience that often.
I have an M1 mac and on standard configuration it’s unusably slow. I’m talking about 1 FPS. In low resolution mode (removing the high res flag from the manifest) it’s just usable (and still painful). I have yet to try it, but maybe there’s a way of going through XQuartz, which might help. I hear they recently switched to GTK’s direct Quartz backend, which I can imagine is causing the problems.
Is that using a native build or via Rosetta?