Jhipster just useless framework, sadly.

[Kosha-account]

Jhipster developers wrote such complicated code that they can't add any more real needed features of the ORM code generation. Just can add some almost useless things like new technologies or Java versions. But the framework become useless because instead of configuration of technologies you almost doesn't get generated code and obliged write by your self which is just shows how this tool is useless

[atomfrede]

Sorry, but how does this spark any useful discussion? Does it have something to do with #29844 not getting the desired response? If you have any issues with the ORM code generation, maybe you should open a ticket or even better do a pull request.

[Kosha-account]

You're very welcome to contribute and make it useful. Maybe start with a discussion about what you don't like and would like to see.

And one more question, you so nicely invite me to contribute, did you contribute your self something?

[Kosha-account]

BTW, I tried to create a blueprint, but it is so badly documented and JHipster's code is so badly organized and badly structured so no chance to make something useful by using the blueprint mechanism.

[atomfrede]

I did contribute in fact yes. I totally agree we have Bad Developer Docs for blueprints as a lot of Things moved so fast and we could do better.

[Kosha-account]

Could you show your latest contributing commit if you don't mind?

[Kosha-account]

So the jhipster has become nothing more than a toy for children instead of a serious tool.
Moreover, its code is impossible to fix, it is so bad.
Actually, I said this so that the board members would know about it, if they haven't figured it out already.
Actually my goal is just to say "as developer to developers" to JHipster's maintaners that such an implementation is just a shame.
I am ashamed that we are colleagues.
That's the point.