Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Inkscape 1.1.2

inkscape.org

Post reply on HN
Print view View original

11–20 of 68 posts

Re: Inkscape 1.1.2

#11

Post by WanderPanda »

speedgoose wrote: post #10
nyanpasu64 wrote: post #7

Earlier quoted context omitted.

Do you think you or the parent commenter can look into debugging or fixing the bugs yourself? I'm also disappointed at buggy software, poorly considered changes, and maintainers ignoring bug reports. But (sometimes) I try (and occasionally succeed) to fix bugs I encounter.

Debugging and contributing to large and complex C++ projects is not trivial. I personally do debug and contribute to open source projects using technologies I’m confident with, but when it comes to Inkscape I can’t do much more than to do nothing and to hope for the best.

Filing reproducible issues is probably a good start and anybody can do it

Re: Inkscape 1.1.2

#12

Post by AdamBelis »

zibzab wrote: post #3
grenoire wrote: post #2

I am having some serious slowdown issues since 1.* on Win 10, so I'm stuck on 0.92. I have no qualms with it, but the issue plagues all my Win 10 machines and I just wonder what's going on, and if I'm a select minority with it. Besides that, thanks Inkscape for being such an incredibly useful vector tool!

To avoid the extreme slowdown (and crash after a while) on win10, close the document property tab (!!) Anyway, inkscape has really disappointed me with multiple serious regressions. This + UI issues + layout problems + zoom buttons disappearing + crash due to version incompatibility + not remembering what unit you use + DPI screwup got me wondering if the people in charge really got what it takes to run the biggest F…

It's easy to forget that Inkscape is run purely with volunteers, is a charity with 0 employees. I get that these problems are frustrating but maybe it would be more appropriate to wonder how is even possible that this project runs so well :D. Some technical problems are outside our power. Mainly performance regression was introduced by gtk3. Which was a big blow to the whole project because it took 5years of work. And in the end, we discovered that technology is just slow and we need to migrate once again if we want to fix it. Bugs are not ignored we just simply don't have enough manpower to fix them all

Re: Inkscape 1.1.2

#13

Post by zuzun »

zibzab wrote: post #3
grenoire wrote: post #2

I am having some serious slowdown issues since 1.* on Win 10, so I'm stuck on 0.92. I have no qualms with it, but the issue plagues all my Win 10 machines and I just wonder what's going on, and if I'm a select minority with it. Besides that, thanks Inkscape for being such an incredibly useful vector tool!

To avoid the extreme slowdown (and crash after a while) on win10, close the document property tab (!!) Anyway, inkscape has really disappointed me with multiple serious regressions. This + UI issues + layout problems + zoom buttons disappearing + crash due to version incompatibility + not remembering what unit you use + DPI screwup got me wondering if the people in charge really got what it takes to run the biggest F…

I'm pleased with their development pace. Every new release has lots of good changes, plus I believe they are fighting technical cruft under the hood.

Re: Inkscape 1.1.2

#14

Post by udbhavs »

grenoire wrote: post #2

I am having some serious slowdown issues since 1.* on Win 10, so I'm stuck on 0.92. I have no qualms with it, but the issue plagues all my Win 10 machines and I just wonder what's going on, and if I'm a select minority with it. Besides that, thanks Inkscape for being such an incredibly useful vector tool!

I've only used post 1.x versions and they've had a lot of freezing issues but I thought that's just the way the program was. After seeing this I'm going to try 0.92 and see if it's smoother

Re: Inkscape 1.1.2

#15

Post by realaleris149 »

WanderPanda wrote: post #11
speedgoose wrote: post #10

Earlier quoted context omitted.

Debugging and contributing to large and complex C++ projects is not trivial. I personally do debug and contribute to open source projects using technologies I’m confident with, but when it comes to Inkscape I can’t do much more than to do nothing and to hope for the best.

Filing reproducible issues is probably a good start and anybody can do it

Yeap! As a developer, having a well described bug, with clear steps and conditions, is sometimes 90% of the work needed to fix it.

Re: Inkscape 1.1.2

#17

Post by chrismorgan »

grenoire wrote: post #2

I am having some serious slowdown issues since 1.* on Win 10, so I'm stuck on 0.92. I have no qualms with it, but the issue plagues all my Win 10 machines and I just wonder what's going on, and if I'm a select minority with it. Besides that, thanks Inkscape for being such an incredibly useful vector tool!

I’m also fairly bitter about the handling of 1.0 on Windows. I reported various problems at the first beta in moderate detail, my report was more or less ignored and they went ahead with various significant regressions in performance and UI, largely because no developer was interested enough in Windows, and I and others evidently failed to convince them of just how bad it was on Windows; GTK+ 3 in general has shown a general disdain for doing Windows well, whereas GTK+ 2 had been worked over until it wasn’t too bad. Yes, Inkscape is done by volunteers, but I reckon that some of these issues should have been considered blockers to at least recommending 1.0 for Windows, if not its release. So I also stuck with 0.92 while on Windows.

But I very much like what I’m seeing in the draft release notes for 1.2: as well as some really nice-looking functionality improvements, they mention various performance improvements in approximately the areas that had the worst regressions in 1.0 (such as zooming and panning), and UI adjustments to reduce space consumed. I haven’t tried 1.2 alpha 1 out just yet, but I probably will in the next few days and I’m really looking forward to it. (Incidentally, I’ve been back on Linux for the last ten months, and using the latest releases, since it works better under Linux, though Adwaita is still horrifically wasteful of space given Inkscape’s habit of stacking many buttons side-by-side, so I installed Minwaita which reduces that problem a lot.)

Re: Inkscape 1.1.2

#18

Post by jarek-foksa »

grenoire wrote: post #5
hyakosm wrote: post #4

Earlier quoted context omitted.

Affinity Designer is a pretty good tool for vector drawings (for 55$ unique payment). It fills the gap between Inkscape and Illustrator.

Affinity seems like it doesn't have some of the more precise layout tools and SVG-editing capabilities that Inkscape does. I took the trial after seeing people suggest it as an alternative, but it didn't quite replace my workflow and I ended up dropping it.

Check Boxy SVG for an SVG-focused vector graphics editor. Its UI is heavily inspired by Inkscape and the Linux version is available for free (you just have to run "snap install boxy-svg").

Re: Inkscape 1.1.2

#19

Post by sprash »

chrismorgan wrote: post #17
grenoire wrote: post #2

I am having some serious slowdown issues since 1.* on Win 10, so I'm stuck on 0.92. I have no qualms with it, but the issue plagues all my Win 10 machines and I just wonder what's going on, and if I'm a select minority with it. Besides that, thanks Inkscape for being such an incredibly useful vector tool!

I’m also fairly bitter about the handling of 1.0 on Windows. I reported various problems at the first beta in moderate detail, my report was more or less ignored and they went ahead with various significant regressions in performance and UI, largely because no developer was interested enough in Windows, and I and others evidently failed to convince them of just how bad it was on Windows; GTK+ 3 in general has shown a…

GTK is a GNOME library and GNOME has shown in the past that they not only don't care about third party software but are actually extremely harmful to the community to the point that you might as well call it sabotage. The transition from GTK2 to GTK3 was extremely painful, had no benefits for anyone except GNOME and had many regressions across the board. The right course of action for Inkscape would be to switch back to GTK2 and be as independent from GNOME as possible. For everybody else it would be advised to make sure that your software runs well everywhere but GNOME. Simply check if getenv("XDG_CURRENT_DESKTOP") is equal to "GNOME" and exit(EXIT_FAILURE) if true.

Re: Inkscape 1.1.2

#20

Post by prox »

sprash wrote: post #19
chrismorgan wrote: post #17

Earlier quoted context omitted.

I’m also fairly bitter about the handling of 1.0 on Windows. I reported various problems at the first beta in moderate detail, my report was more or less ignored and they went ahead with various significant regressions in performance and UI, largely because no developer was interested enough in Windows, and I and others evidently failed to convince them of just how bad it was on Windows; GTK+ 3 in general has shown a…

GTK is a GNOME library and GNOME has shown in the past that they not only don't care about third party software but are actually extremely harmful to the community to the point that you might as well call it sabotage. The transition from GTK2 to GTK3 was extremely painful, had no benefits for anyone except GNOME and had many regressions across the board. The right course of action for Inkscape would be to switch back…

I hate this ivory tower way of developing. It holds back progress, learning by exchange, and so on.
Post reply on HN