Forum Discussion
GaryBoyd
7 years agoQrew Assistant Captain
Thanks - like it. It does what i want to achieve, but obviously don't want to do anything not secure in quick base.
Would be good if there was a safe way to suppress the headers when required, as they take al lot of screen space.
Would be good if there was a safe way to suppress the headers when required, as they take al lot of screen space.
_anomDiebolt_
7 years agoQrew Elite
>But is it fragile in that it could break without warning if QuickBase wittingly or unwittingly makes a change in a new release
I have to add a comment: While it could break, it probably won't for years. Software tends to accumulate and it is only willfully purged if some new project or initiative is started and there has to be greenfield development.
On this point it is interesting to read the most recent engineering blog post:
Death by 30,000 Files
I have to add a comment: While it could break, it probably won't for years. Software tends to accumulate and it is only willfully purged if some new project or initiative is started and there has to be greenfield development.
On this point it is interesting to read the most recent engineering blog post:
Death by 30,000 Files
Who Cares? Our largest build artifact was 256 MB and 30,000 files. ...https://engineering.quickbase.com/
... 20,000 � 66% � of those files were cruft.