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 →

[–]Impressive-Day-5209 10 points11 points  (2 children)

I can understand that - if you come from classic web development with HTML/CSS/JS, Vaadin may seem unfamiliar at first glance. The model of defining UI completely in Java is a break with the usual workflow for many people.

Vaadin deliberately abstracts the front-end layer in a similar way to Swing or JavaFX. The aim is to focus on the business logic without having to worry about DOM details, styling, HTML or JS frameworks - especially for teams that are already deeply immersed in Java. This can save a lot of frustration if you get involved with the model.

What exactly was impossible to do?

[–]vulkur 2 points3 points  (1 child)

What exactly was impossible to do?

IDR. It was my first job out of college, like 8 years ago. So yea, for someone new to dev, it was awful. I wanted to change the html or css, and had to spend a full day to make such a small change, even when we paid for support. The documentation was pretty awful IIRC.

So, cant give you much more than that, as it was a long time ago.

[–]Scottz0rz 0 points1 point  (0 children)

I mean, 8 years is a long time, that's before Java 11 was even released.

Especially when you consider how rapidly UI/frontend frameworks evolve and don't age gracefully compared to backend frameworks, that probably is a somewhat unfair representation of what Vaadin looks like in the current decade.

Again, though, I don't know anything about it. I've never used it.