Hi Michael,

thanks for your input. Just finished the next article about the new scss file by file build and got a moment now.

The dev mode runs using the real code as it is, which makes using tools like jsx tricky (everything needs to happen at run time). Inside the dist/development mode it is a different story though. We could adjust the webpack dev server to apply hot module replacements here and then you could work on this level.

I am open minded in general. If someone wants to implement something like this, it is fine for me as long as it stays optional.

I have talked about the neo project a lot with my former PlayStation project manager. In his opinion the project is brilliant from a technical perspective. The main problem is a different one:

Most developers don't really care about next gen technologies, but look at how many projects and jobs are available on the market for a given scope.

Most companies on the other hand are looking at how many developers are using a library / framework. There is still a mindset that projects based on main stream technology attract talent. Very few companies feel comfortable to jump into the early bird role, no matter how great the benefits could be.

It would be an entirely different story if the project was backed by a big company, but this is something I can not really influence.

Getting more contributors is tricky as well. Even most of my former co-workers at Sencha are no longer able to follow the internal logic. While I try my best to keep using neo as easy as possible, the internal mechanics are intense.

I would enjoy creating some demos using more functional approaches, but I am not sure when I will find time for it.

Best regards,

Tobias