“loops are done with backend recurring workflows”
I’ well aware of that, thanks. I use plenty of them on my site. My point is that many things which are standard logic require specific workflows built for those purposes. Loops for example shouldn’t need to be an extra internal service/backend, but a normal part of the logic in any workflow. Or would you consider creating something akin to an internal API just to run a loop as performant? Maybe if the page isn’t’ so complex, but once you have several layers of complexity, each “this is how it’s done in bubble” adds up.
When it comes to global variables I earlier searched for solutions for having a varible that keep tracks of things such as customer number, or order number. I do use a “bubble solution” and I’ve seen how others have solved it by using backend flows etc, but that again requires more work-around then if done programmatically. Bubble is great for many things, but then there are some basics which just isn’t there and needs to be done in nested ways, which slows down the performance even more.
This is the discussion and solution I use for global variables: Global variables in Bubble? It’s “easy” but still workaround as compared to just having a global variable. Instead a custom data-set, a search function, and a back-end workflow is required. For a variable.