I had a short and eye-opening talk with @tuzin.arts today about Glide Big Table. I’ll rephrase what I understood (my apologies, Art, if I misunderstood anything):
- By default he will build on Glide Big Tables and not on Glide (Regular) Tables
- If a table will expand in terms of number of rows, even if it’s a few rows every so often, he will use a Glide Big Table
- He will only use a Glide (Regular) Table for helper tables which have a fixed number of rows
- Glide Big Tables forces us the developer to build cleaner
I’ve stayed clear from Glide Big Tables because in general I am more comfortable staying away from the edges of experimentation. For a long time, I’ve felt that GBTs were still in the prototype and testing phase, and not yet a product I would be comfortable building on, certainly due to my own limitations.
But Art’s comment made me wonder: is it now time to make the switch and to seriously (for me) start building on Glide Big Tables? If so, for all tables like Art does it – expect for the Users table and helper tables – or would the adoption of Glide Big Tables be more nuanced, such as suggested by Darren below (transactional tables, chat)?
Thanks in advanced for any insights and personal experience you might be able to share.