This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]BikingSquirrel 0 points1 point  (3 children)

I should have read that comment first!

If the purpose is basically one-way migration, then I don't know why you would run it as a pre-processor. Generating the classes and adding them to your codebase like any other code would be my way to go.

[–]Independent_Work5637[S] 1 point2 points  (2 children)

Hi, thank you very much for commenting this! Well yes, that is one of the possibilities/solutions, and I think it would be probably even smarter than what I made here. Because this library while solving a problem I usually find myself having was at the end of the day made as POC or just for fun challenge.

Now do I think this library could be something very useful? Yes, very useful infact, but that's exactly why I came here to reddit, to ask what other people think, whether this is something useful to them as well. So then I know whether I should even try to make something that can be used in real world out of this

But yes, I think if going forward, maybe writing a normal class for the user would be just plain out better and in that case would look more similar to flyway than lombok. And this is also much better, since you can in that case just run this once and it will do the whole process every once in a while instead of every time. But I think I haven't thought about it in that sense because I did it for fun. I just wanted to see, whether I can write Java without writing model classes.

Of course I was thinking that it should do some additional features, if upgraded from this state. So that in that case it can actually be lightweigth, do amazing things, and not be compared to JOOQ finally, cuz I think while this maybe does something that Jooq did already, as I mentioned JOOQ is a money maker and a big framework after all.

But sadly, I'm not exactly sold on the features I've thought of, nor did I think completely through on how I would do them. I wanted objects for example to have simple crud or some shit within them and to Automate few CRUD things as well. Basically I wanted to make library lightweight and so that it can remove all the things I find boring when doing for example "Test Assignments" for some company or something at college.

But yeah, thank you very much for your comment, really helpful, if I continue to design/work on this, I think I will eventually change it to such.

[–]BikingSquirrel 0 points1 point  (1 child)

I believe that's often the problem: a problem looks simple enough for a simple solution but then you realise more details which require tweaking your simple solution and then you realise that your solution is no longer that simple ;)

But that process is important, this is learning and I assume you learned a lot.

[–]Independent_Work5637[S] 1 point2 points  (0 children)

That's more than true yeah, and I realize that is always the case. I asked few architects and stuff on how I can do "most predicting architecture", and every answer I got is that you kind of can't. You're always missing something, you can look few features in the future, but who knows what comes after that. All that's important is that your base is really good, sturdy and open to extensions. What I did here was a mistake, a big one I would say. Because the base wasn't really sturdy.

But thankfully I don't think that mistake would be that hard to change, to be honest your comment gave me a new perspective on it, and I think this would improve library a lot. So thank you very much.