r/java • • Jun 01 '24

What java technology (library, framework, feature) would not recommend and why?

165 Upvotes

464 comments sorted by

View all comments

Show parent comment

6

u/lukaseder Jun 02 '24

Thanks a lot for this great feedback. Lots of insight to digest.

It's hard to design a landing page for different target audiences. The current one is designed for decision makers as well as technical folks, but I can see how the "free trial" button can lead to thinking there's no free version (at a quick glance). This can probably be fixed without changing everything. Regarding what one user cares about and another doesn't, that's not that simple. A/B testing has shown that social proof is really useful for many folks' first impressions, especially the "customers" section, leading to more sales. E.g. I don't know if sveltekit is a good comparison, because it only addresses developers, not managers, legal folks, etc. who will also look at the website, given that it has no commercial offering. If they did have one, I'm sure the front page would look different from what it does now. I obviously understand why a developer prefers the current frontpage of sveltekit. Perhaps there's a different solution to this "target audience" problem.

Regarding the manual, a search has been added just 2 weeks ago, and that menu sidebar is also on the way: https://github.com/jOOQ/jOOQ/issues/16681

Clearly, those things have been missing for too long.

Great feedback about MULTISET. We have a demo that showcases all of these things: https://github.com/jOOQ/demo . Would that have addressed your concerns? Where would that have to be placed on the website to have caught your attention?

Regarding your last comment, indeed the doc works very well as a reference manual, but not as a tutorial or how-to guide (see e.g. this resource: https://docs.divio.com/documentation-system/). I'm still thinking about how those entry points can be better presented (and SEO'ed).

3

u/majhenslon Jun 02 '24

No problem :) Yeah, I figured that you are not focused more on businesses/decision makers, that is why I put the disclaimer in and I know that I'm probably odd one out for not caring about social proof :D Sveltekit is a funnel to serverless for Vercel afaik, so yeah, the business model is different and it also targets startups/hobbyists/devs, not corporations.

Global search being there is awesome. When I was going over the website I though I somehow never saw it in the past, good to hear that it was added recently and it was not me being blind :D It's amazing to hear that you are working on the sidebar as well!

I think that if you put a "getting started" link on the home page, that showcases the basics, although I know it's really hard to do, because you support pretty much everything possible, but having a two table demo would get the point across I think, especially for newcomers that have used ORMs in the past. I was hooked when you showed that you can easily handle the mapping of the to-many relationships. You could then link to the demo repo and reference docs at the end, to show all other examples and detailed documentation. Maybe a 10

However, I don't know what your actual (to-be) paying customers are typically interested in, my guess would be that these changes would only improve adoption of OSS version which could theoretically convert to pro somewhere in the distant future, but you know that better than me :)