Hi all,
in Quarkus we're using a plugin which automatically reformats the code
and sorts imports.
In our older projects we've been using checkstyle; the goal has always
been to try to avoid conflicts and improve readability, but to try to
impose such consistency typically leads to a significant a
Historically we made a terrible design mistake with the event system as a
whole. This has both a confusing design impact and a very real performance
impact. The main problem is the smashing together of things that handle
events and things that listen to such events.
In working on a problem in v6
Hi Steve,
looks like you're getting rid of the "event object"? No more events to
be allocated?
I think that's a great idea, but I wonder about the readability of the
code. With "inline types" coming soon to the JDK, the event object
types could be great candidates to be converted into inline?
If
It is an interesting idea. Guess it depends just how configurable it is to
get what we want.
On Tue, May 26, 2020 at 5:03 AM Sanne Grinovero wrote:
> Hi all,
>
> in Quarkus we're using a plugin which automatically reformats the code
> and sorts imports.
>
> In our older projects we've been u
