On Thu, 15 Mar 2018, 13:40 Wade Chandler, <[email protected]> wrote:
> > > On Mar 15, 2018, at 8:54 AM, Neil C Smith <[email protected]> wrote: > > > > Anyway, this whole thing is going a bit in circles. We need to look at > > improving the POCs in NetBeans to be able to show where (and where not) > > this approach is viable and useful. > > > > Agreed, but I think, so IMO, those just take us off the things that will > actually have direct and immediate impacts. We can work on NB just as it > is, and work to fix the index lock issues, add new Java parsing, add better > language and feature support for some things like Groovy and Python, and > generally move ahead, even while fixing some issues in Swing/AWT, or bog > down in all this talk of web UIs which starts to make a lot of work which > in the end didn’t really move the needle because we’ll still have a desktop > IDE, but a lot of time would have been spent to just get further behind. > Agreed, 110%! To clarify, by proofs of concepts here I'm talking examples and build systems that people can use within projects in the IDE, not bits of the IDE UI itself. Having an Electron-like build and deploy system that uses the HTML/Java library and a JVM rather than node. That sounds like a powerful thing to have in our armoury for developers to use. The question of whether the IDE should migrate to that if it proves viable - that's a whole other distraction for a future time IMO. Best wishes, Neil -- Neil C Smith Artist & Technologist www.neilcsmith.net Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
