Let the new era begin!
As a community-driven project, we stick to a very important principle that helps us navigate throughout the new emerging technologies and focus on the right priorities:
Based on the feedback we have received so far, we had to take a few major decisions:
Moved to the standard Java/Maven development model for the core components
The OSGi-based development model coming with Maven and Tycho integration, Orbit repositories and target platform definitions was listed many times as something too complex by the younger generation of developers who tried to understand the project source code and become contributors. The comparison was often with Spring Boot and other similar frameworks and projects. The decision was not easy, but we jumped to pure Maven project structure. The major benefit from this decision is that now you can build your own stack including also external dependencies more easily and in a more natural way.
Moved from Eclipse RAP to pure Angular 1.x/Boostrap/GoldenLayout for WebIDE
Of all the technologies we have been using, Eclipse RAP has been the most stable one. As a Web port of the Eclipse Rich Client Platform (RCP), we expected that the thousands of Eclipse plugin developers would recognize Dirigible as the easiest way to port their existing plugins to the Web or just to leverage their experience to create some brand new Cloud-related plugins. This did not happen. We decided to go to pure Angular 1.x/Boostrap/GoldenLayout user interfaces even for the WebIDE parts. The front-end now uses a set of RESTful services for workspace management, lifecycle management, repository, database, documents, etc., following the standard Web 2.0 approach. We have chosen that approach for building applications with Dirigible, hence now we are developing Dirigible with Dirigible itself. Finally we can say that!
Adapt V8 engine in the API layer
Webjars for applications content
To comply with the legacy of CI/CD processes, where requirements such as reproducibility, immutability, testability are must-have features of the underlying framework, we had to add a new approach of packaging of the applications for production. We decided to follow the so called “webjars” structures, where the application content (e.g. HTML files, database definitions, extensions, etc.) are packed as a standard Java archive and are accessible at runtime in the same way as they reside within the repository. In this way, nobody can change them once they are built into a deployable archive. The side benefit is that they can be distributed in the same way as the rest of the core modules - as standard Maven dependencies.
The focus, the development model and the main goal - reconfirmed
What remained and was reconfirmed was the focus on the business applications development in the cloud. Not just a general purpose IDE or a platform, but tailored for specific scenarios required by the businesses to optimize their processes. In-system programming was the clear differentiator giving an unique development experience and the fastest turn-around time in the Cloud.
It was a hard period for all contributors to reimplement almost the whole stack from scratch - but we did it!
In the next few days, we plan to publish a series of blog articles explaining how exactly we did it and how you can use it - to extend, configure, and run Dirigible in the most optimal way.