On Thu, 2019-03-21 at 23:19 -0500, Ole Ersoy wrote:
Not at all. You can have two versions of the same app. Eventually
this will be done under Inkscapes control or not under Inkscapes
control. Inkscape is built on old tech. Inkscape can take control
now and start reinventing the platform, or wait until someone else
does it, and become irrelevant.
Two versions of the same app has never been a winning strategy.
> I don't think the project's best interests lie in abandoning the
It would be an enhancement. Expand the developer tools, expand the
developer pool, expand the use cases, expand Inkscapes shelf life,
expand the ecosystem of SVG components. AND nail your concern about
Inkscape being able to run on any platform.
Even with all those advantages, it's just not worth it. Firstly, you'd
be gutting Inkscape's brand, skinning the project alive and grafting it
on a new project... Just to make a new project. Better to develop a
brand without Inkscape's baggage. If it's Free and Open Source, the
Inkscape project is going to be kindly uncle to any online or electron
vector editor pointing users to it.
Inkscape doesn't have to "win", it doesn't have to be afraid of being
made obsolete. Inkscape is a project for it's users, and when it's
users move on, it will have done it's duty and will quietly live out
it's retirement in the internet archives.
A brand new vector editor made in Electron or nodejs, is fascinating
stuff. A project experiment that is one to watch. But not something we
need to actively replace Inkscape with.
But Ole, you seem VERY into the idea, so you should set about this
I'm not sure they're atuned to Free Software, so YMMV) but
bootstrapping such a project can be done on GitLab very easily. Then
when you have made it, keep us up to date here. There are likely
developers who would be interested in helping out from the Inkscape
Best Regards, Martin Owens