However, sometimes the first question overrules the second. If I was answering the second question as server side right now I would probably pick htmx+alpinejs. That is no longer the case for the second question, the state is increasing moving to the client side, and that's why I joined the team. The project I'm on when they first asked those questions, the answer was, Perl CGI and server side state in a database. where is the state? Is it predominantly in a database on the server or client side in the browser? what do my team and myself know well, what will be the most efficient? There are two main things to consider when picking a toolkit or architecture for a web app/site: You are complete right, to many people chose a tool based on fashion. We have kept the old Perl CGI server architecture, just refactored it to return JSON. Have moved the whole thing to a VueJS frontend. Massively grown past the point where that is suitable, with plans to add interactive features that would be crazy to do with the old architecture. I have just spent the last year doing the literal opposite.ฤก5 year old software product built on Perl CGI with a server rendered html+jQuery front end.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |