I agree! That was kind of my point in saying 5 to 10 years. Everyone has different needs and different priorities. If it takes them that long, clearly their priorities are not aligned with mine, and if enough of us engaged users don't like that and let them know, then they hopefully can realign their priorities with ours. After all, we are the customers.
If I wanted to be a coder, I probably wouldn't have chosen QuickBase as my app building platform. The fact that I did means I really don't want to lead with code. It has its place, but I would argue that if you are constantly needing to implement things in QB with code as a first choice, you are missing out on the biggest strength of QB, which is that it doesn't require coding for 85+% of what we all need to get things done. I've been a coder for 39 years of my life and I see all too often the great expense of code, especially when a small business has changes in its personnel, and the new people don't want to touch the old code. This is a problem everywhere in the business world, and one of the biggest reasons why I chose QB. I don't want to get hit by the bus and have our CEO cursing me under his breath every time he has issues going forward with someone's old F*&%ing code. So, in my opinion, better to not code unless absolutely necessary.
Dan, you are clearly a brilliant guy and a great resource to this forum. But most of your responses to these questions read like you are fighting a current by swimming upstream. It's not pragmatic or even desired by the vast majority of QB administrators to add gobs of code to their apps to get basic functionality to work. Sometimes it's absolutely necessary and appropriate. But that shouldn't be the rule. That's what we are all fighting for with our UserVoice suggestions. Coding can be fun, but nobody wants to support it later, especially when it's been written by someone else who understands it a lot more deeply.
Code can be implemented quickly by someone like you who really knows what they are doing, but its cost of maintenance and support over its lifetime will consume way more time than 5 to 10 minutes. That's why I want a robust platform that doesn't require me to code for every little thing. I think that is basically QB's mission. Why do you seem to be fighting that?
I'm sincerely asking this in a very respectful way. You are a great resource, but you seem to have an attitude about people wanting to do things simply without code. Creating code is simple, especially for someone like you, but it is indeed not simple at all to support it indefinitely. That's its achilles heel.
