Re:How Bubble bootstrapped a visual programming tool for non...
by aeorgnoieang on Monday November 13, 2017 @10:48AM
(#15687272)
> I think the most interesting way of doing this would be something like embracing Bubble for a lot of work and having the "serious" code relegated to places that are easier to manage, like complex API or some custom widgets
This is basically what I do now at work. I was hired to, in part, work with several RAD-tool projects. I pretty quickly ended-up tho working on mostly backend code that the RAD tool projects interact with via, e.g. web requests. That's been a pretty good division of labor given that most of the RAD tool project's features are fairly simply in terms of UX. They're definitely not good enough to be widely used by lots of users tho, e.g. there's no real error handling.
Re:How Bubble bootstrapped a visual programming tool for non...
by bluedino on Monday November 13, 2017 @10:00AM
(#15686897)
>> The Bubble model is to write the core website functionality using our super-simple language, and plug in Javascript to handle algorithms that are hard to build in Bubble
Programming without code...until you need to actually do something
You could also likely put a layer in front of Bubble to only serve some pages with Bubble, other with your replacement.
Also from the FAQ: > The good news is that Bubble is fully extensible via Javascript plugins. The Bubble model is to write the core website functionality using our super-simple language, and plug in Javascript to handle algorithms that are hard to build in Bubble.
So you could probably add shims and move around.
I think the most interesting way of doing this would be something like embracing Bubble for a lot of work and having the "serious" code relegated to places that are easier to manage, like complex API or some custom widgets