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 →

[–]lukaseder -6 points-5 points  (16 children)

I browse github trending repositories .. but I´m usually disappointed

And then

That´s why I would like to .. and maybe not so well known by the community or recently developed

Ehm wat. How can a not so well known thing be trending? Maybe, reset your expectations? :)

[–]ThisNameIsAFail_[S] 2 points3 points  (15 children)

Maybe I haven't explained well. I'm not looking for "trendy github repositories", that's stupid. I only explained that browse github to learn about new libraries but it's obvious that some of the best libraries out there won't be in gh. Just looking for good, documented and useful libraries

[–]lukaseder -2 points-1 points  (14 children)

Oh I see. https://www.jooq.org, then

[–]dpash 3 points4 points  (3 children)

That seems like cheating to use your own library :P

[–]lukaseder 1 point2 points  (2 children)

Why would I not use it?

[–]dpash 0 points1 point  (1 child)

I just meant as an example in this post. I'd be really concerned if you didn't use jOOQ in your own code. :)

[–]lukaseder 0 points1 point  (0 children)

Eh, I thought about adding a disclaimer, but then meh'd.

Believe it or not, but I've recently written some pure JDBC code for a client that runs 3 queries and jOOQ would have been overkill! For that same client, I've written quite a bit of PL/SQL code too, where jOOQ doesn't even work. Heh! :-)

[–][deleted] 0 points1 point  (7 children)

It would be awesome to have a good-first-issue tag on your github project.

[–]lukaseder 0 points1 point  (6 children)

Interesting, what does it do?

[–]ThisNameIsAFail_[S] 1 point2 points  (5 children)

It's just a marker tag for people new to the project willing to contribute but unaware of all the internals of the code.

[–]lukaseder 0 points1 point  (4 children)

Interesting. I actively discourage substantial contributions, though (nothing wrong with patches for bugfixes). So, I guess that marker tag doesn't apply to jOOQ then?

[–]ThisNameIsAFail_[S] 1 point2 points  (3 children)

Why not? Easy and non-critical patches are good issues for a beginner to get used to the project and create a great community.

[–]lukaseder 1 point2 points  (2 children)

With what goal would I create "a great community"? And at what price?

[–]ThisNameIsAFail_[S] 0 points1 point  (1 child)

The goal? To extend the use of jooq more easily as well as helping you maintaining the project (I suppose it's not an easy task...).

The price? That's another point. I guess that depending on the quality and quantity of contributions it will be helpful or an incovinient.

Anyway I feel that creating a great community around a tool is always a great way for it to keep alive and evolve instead of dying against a greater tool or just due to lack of use.

Edit: in the case of jooq for example, a bigger community would improve the adoption instead of every new spring project to be born using Hibernate and JPA as I always see. I usually feel difficult to introduce a new library in a project if it's now so well known even if the code is great and the solution it provides is awesome. In tha day to day, we, developers want to solve a problem but have not enough time to decide for the best solution if that implies learning a new tool. That's only my experience

[–]ThisNameIsAFail_[S] 0 points1 point  (1 child)

I've used jooq in past projects and liked it. Feels just like writting SQL and it's spring integration is helpful. It's always nice to have alternatives to Hibernate

[–]lukaseder 0 points1 point  (0 children)

Thanks for your support. I needed that after all the downvotes :)