On 03/11/2016 11:13 AM, Vladimir
Piskarev wrote:
I'd rather keep Handly separate for the time being,
with perhaps moving parts of it down to the Eclipse Platform
(LTK?) eventually. I believe that it is not necessary to be part
of another project to be used by it, right? :-) I mean that DLTK
could depend on Handly, not the other way around. (Handly is
really much more generic while being much narrower in scope.)
In theory yes, in practice, there are other things to consider than
just code:
* Handly is currently a small and young project: very few
contributors, not much community... Those are things that need to
tremendously grow to consider Platform or DLTK relying on Handly.
Indeed, adopting an upstream project as a dependency is a critical
strategic choice, so it requires real sustainability to be
considered. However, in the other way round, if Handly gets part of
DLTK, then it will immediately get a boost of contributors and/or
users, and be perceived as more "reliable" by other projects such as
JDT, CDT, JSDT, PDT...
* Moving a piece of code to Platform or JDT comes with a bunch of
constraints about API or release schedule, so it's clearly not
something recommended for any piece of code that didn't reach a high
enough level of maturity.
If you want to succeed in your goal of factorizing language tool,
that cannot be a one-man project. It seems easier to join an
established project that already share parts of this objective.
My 2c.
|