Personally, I think that in future dltk could be extension for LSP4E, as a provider of ast, indexing and other advanced stuff. But, for this have to support multiple language toolkits in same project.
On 26 April 2017 at 09:37:12, akurtakov (akurtakov@xxxxxxxxx) wrote:
Hi everyone,
_javascript_ ecosystem is moving quite fast, which can't be said for
DLTK one. Even the WTP one is considered badly outdated now [1] and
looking for new path. Should we just give up on _javascript_ module
in DLTK and disable it from the build? I don't think anyone will
join working on it especially with the current push about language
servers and friends. WDYT?
P.S. I have similar thoughts about Python but this one could
probably be reformed as language server based one, while the JS
have definetely taken another path.
Regards,
Alex
_______________________________________________
dltk-dev mailing list
dltk-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/dltk-dev
