To enable an improved update flow, we explore the idea of a plugin mechanism for the CLI to allow integration of externally provided tooling to help during development. We intend to have a more common structure and also use more advanced client-side technologies for a richer experience. Even though it was easy to add content, it required a lot of duplication and some workflows were just impossible to implement. The Dev UI is built around the Qute template concept, which is "tiles" that provide development-relevant information. Next, we focus on improving their integration as well as their visual experience. They allow you to explore and try things out without complex setup, restart and still apply TDD. Max Rydahl Andersen: Quarkus has three capabilities that enhance the developer’s productivity: InfoQ: Quarkus 2 delivered continuous testing as part of your promise for a joyful Developer Experience. To find out whether version 3.0 will follow this tradition, InfoQ continued the conversation with Andersen. More than speed and cloud nativeness, developer joy and support for both reactive and imperative coding styles that are part of Quarkus’ mission statement, Developer Experience (DX) and the focus on productivity were also an important part of each of the previous major releases. In our previous conversation, we focused on the technical changes that they consider to be the following steps to deliver on their mission. InfoQ reached out to Max Rydahl Andersen, Quarkus co-lead and distinguished engineer at Red Hat, to learn more about the features that would improve the developer experience. Qaurkus is heading towards the final version, currently reaching 3.0.0.Alpha5.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |