have added many more technical and strategic reasons, including
> expanding the potential developer pool (There are a lot more
> client), but the main reason I would do it personally is because it's
> fun and it would expand my skill sets in new and creative ways:
Fun is good. So is expanding your skillset.
If you look at my general blog posts you'll see I'm all over it ... perhaps a bit
Most people writing a cloud platform for logistics stay clear of developing their vector
graphics skills. I enjoy that as well. In addition to things like this (Which I authored
all the repositories for, setup Travis Integration, etc.):
So go ahead and rewrite
calls to rewrite perfectly functional code
Transfer - not rewrite
for an extremely well
functioning program. Those of us who actually use Inkscape for:
* Active images
* Flyers and newsletters
* Mailmerged certificates
* eBook covers
And it is amazing already for all those use cases, but not for
collaborative ones where we want to embed Inskcape in the browser and collaborate, save,
and fork SVG projects. All the use cases you site will be greatly enhanced if Inkscape
had the ability to be browser embedded.
appreciate having developer time available for fixing any bugs (I've
never found any) or carefully adding new features, rather than
rewriting a hugely featureful implementation of a solution to a
naturally complex problem domain for fun and experience.
Last time I checked Inkscape was open source and all ideas were welcome. It could easily
be something that accelerates Inkscape development, by drawing more contributors,
modularizing platform components, increasing developer collaboration, and in general
making development of Inskcape more interesting by increasing the number of use cases that
the Inkscape platform can handle.
Who had heard of VSCode a year ago ...