You would use Spring Boot as the backend web framework and Qwik as the fullstack web framework that, instead of using a database*, uses an API powered by Spring Boot to access information.
Everything in the Spring Docs about HTML/CSS/JavaScript would cease to be relevant. https://spring.io/guides/gs/serving-web-content/
* Qwik is perfectly capable of using a database despite being a frontend-heavy framework. It's like Next.js in that the backend runs in Node.js and you can use any npm package that runs on Node. The server-side part of Qwik would be lighter weight with it just passing requests on to the Spring Boot app.
Personally, I don't like much where the frontend is trying to lock people into.(javascript)
That isn't how I read it. To me it sounded like the issue was having to run a JavaScript web server. They might like JavaScript on the frontend.
> I think any problems it has on BE would also apply on FE, and should be improved?
Isometric js isn't all-or-nothing, but it sometimes feels that way with a fullstack js framework.