It has its quirks and even some annoying bugs but where it excells its IMO way better than what any competing/proprietary design tool can do (vector and bitmap exporting, vector+bitmap combined layering, shape/colors/text layout, PDF editing/creating, vector pen tool, etc). I use it to create UI for games & apps and more generally to build sprawling UX scenarios and concept flowcharts.
In more recent builds its performance has become quite good which was a problem it had before. Granted, lots of room for improvement still particularly wish it had more natural flowcharting capability.
Disclaimer: I'm an engineer not a UX/UI designer, and I use Inkscape mostly for graphic designs and the odd super-simple CAD stuff where I don't think starting qcad is worth it. Still, I'm immensely happy that I can just get stuff done in Inkscape and that everything inside makes sense and is generally discoverable "solely by logic".
Is Inkscape good for svgs?
Because of the economics of software R&D. Professionals are not willing to stand around a tool that does not do what they need to make money themselves. They simply want to pay and use for a "finished" product, but never stop to consider that (a) software is never finished and (b) funding its development does not mean that you need to use it exclusively.
Companies/professionals would stand to benefit a lot if they funded FOSS alternatives, even if just as an hedge against their "main" tool. Imagine if every design agency got 5% of their "Adobe Tax" and donated to the devs of Penpot, Gimp and Inkscape. No strings attached, just with a "here, none of you need to worry about funding". In just a couple of years all these OSS tools would catch up, and the companies would be able to at the very least use the existence of FOSS alternative as a negotiation tactic when dealing with sales team from Adobe.
It's not like there aren't commercial design tools other than Figma either. People choose to use and pay for those tools instead of Figma. The idea that there's one 'industry standard' choice and everything else is wrong is obviously nonsense. Having an OSS option as well is only a good thing.
Its just mostly about focus of the project and agency of people trying to make UX better.
Arguably it's more important to create software that solves a problem first so there is an incentive for people to keep using it. But the less people use it, the longer it will take for the UX to improve organically (see Blender and Inkscape).
Whatever caused it to succeed and catch enough attention to be continuously improved, I'm thankful for that. Same as with game engines like Godot and other similar FOSS projects, maybe even LibreOffice not dying like OpenOffice did, though that's a whole tale in of itself. Actually, I'll similarly celebrate improvements in proprietary software, too.
Then again, I still think that Inkscape and some of the other software that gets touted as good is actually not very usable, so I'm a bit opinionated.
Honestly, so many projects simply reap what they sow here.
(As far as this program is concerned, my general thoughts are — give it a few years. It took Figma years to supplant Sketch, it took Sketch years to supplant the Adobe suite. I think that the desire from the community is there, as there are really scummy business practices that the Figma team has put in place, and it’s squeezing departments/seats/licenses, which is stupid obvious artificial scarcity that they’re using to extract as much as they can before something useful and FOSS comes around and eats their lunch.)
Figma is stupid expensive, especially when you onboard developers, so it seems like a GitLab esque play could be disruptive.
I wonder if over time a tool that blends the developer, product and design experience more seamlessly will catch on. Having reactive code that is driven by the underlying design in a cohesive way perhaps.
In this aspect, Blender is a very unique OSS project.
Uh, why? It's not magic. Sure, it's a problem that most OSS projects don't focus on UX and perf, but there's no intrinsic reason why they couldn't.