In technical, no buzzword terms, it means writing the whole website, backend and frontend, as one application and one codebase, in one programming language, like you would write a Desktop software. In this particular case, the language is Java, but I know of similar frameworks for Python at least: The likes of Panel, Dash, Streamlit, FastHTML, Flet, etc.
back
1 comments
Thank you. This explanation makes sense. That’s what I thought article meant, but wanted to confirm.
Now, I don’t understand what problem this “full-stack” is trying to solve. Writing websites in different languages is not a problem. You use the right tool for the job. HTML for layouts, CSS files for styling, some server side language for logic, etc. that’s not a problem. That’s just how things work.
Again. When you use different languages/technologies for different things in an application you are using the right tool for the job.
I have used Vaadin and Streamlit for various small/medium projects. Apart from the obvious benefit of not having to touch JS(:D), the benefit is really, well, one codebase, one language for everything: There is no context switch, no need for various skillsets (to some extent), no need for explicitly designing/thinking about client-server communication, doing everything in the language you (or the team) know best, ...
Of course, your argument is totally valid and if things get complicated or you need to "dig deep" you have to make the separation.