AssertJ VS Apache Wicket

Maybe not the feedback you want, but would you consider developing something that looks like plain old (and frankly beautiful) AssertJ?

AssertJ - fluent assertions

AssertJ https://github.com/assertj/assertj

Truth or AssertJ for easier assertions in tests with better exceptions

While we are at it: AssertJ is very powerful for writing assertions.

In OO you can make beautiful DSLs that allow really declarative use within that domain, e.g. test assertions in AssertJ, but everybody in the OO world is sensible enough to not try and claim OO as such being declarative. I guess they don't feel a need to try to prove the superiority of the paradigm.

AssertJ comes with a variety of assertions that can be chained together and are specific to the type of your "actual" variable.

At any rate it comes from a library called assertj.

While Hamcrest add some fluentidity to unit tests ä, I prefer the fluent assertions of AssertJ.

Sort of sounds like Apache Wicket (https://wicket.apache.org/). I used it for a few projects in the mid-late 2000s. I really liked it being server side and the concept of having object-oriented HTML (code paired with HTML snippets). I haven't had a need to use it since 2014, so haven't kept up with the project.

You can use Java for Backend and Frontend. A relative new kid on the block for Frontend is Qute. The general keyword you are searching for is Java Templating Engine. Specific examples would be Thymeleaf or FreeMarker. There are some framework, which offer a lot more than templating like Vaadin or Wicket. Some are just specifications like Jakarta Faces with some of their implementations MyFaces or Mojarra.

Perhaps, a good competitor for JSF is Apache Wicket.

I have used https://wicket.apache.org/ in the past and I think it matches your needs. It's a simple mvc that focuses on the actual java code writing and uses html only on the layout of your components in your page.

Is this the Wicket you're referring to? https://wicket.apache.org/

What's the best intro you know to how it's components work, and the benefits and tradeoffs over other approaches?

You should consider Apache Wicket. It is widely used for business apps.

I think Apache Wicket takes a similar approach for Java? https://wicket.apache.org/

I like the approach, and it's good to see more projects in this space.

I believe Wicket is somewhat similar (and still actively developed).

https://wicket.apache.org/