Blog Post
@Eric Evans Vargas There is absolutely going to be a challenge for us in the next few months here on community to help our awesome builders come together to share their experiences as they find alternatives to javascript and techniques to IOL and to pass on techniques from our team. What is great is that we have already had some community members so far share their concerns and start to work together to share the alternatives they have been using, but there are definitely going to be growing pains when it comes to methods. Your mention of copying and pasting JS code from here in community is actually one of the concerns that spurred on this change, as app builders without programming experience copy and paste these short bits without always fully understanding how it works, which can cause security issues and supportability issues. Someone getting stuck with JS could be in real trouble if it messes up their app and we aren't able to help them unravel the JS since it wasn't something we built or supported.
Our intent is to make it harder to stumble into using JavaScript in ways that is not appropriate, to make things simpler and more intuitive for our main audience of app builders who are not pro developers so that they aren't introducing an X factor into their app that might cause issues down the line. If you feel limited by what value you can get from the Quickbase platform by not being able to rely on JavaScript, we'd love to hear more about what you're working on. I would definitely suggest also checking out the public slack channel below as it is one of the places where we are chatting with people about their needs and sourcing some alternatives. If you weren't able to attend we also had a meeting yesterday with some of the community to talk through the change that we recorded as well.
To those with pressing questions on the Javascript change, for people interested in doing a deep dive on some of the JavaScript "holes" we need to close, supported alternatives and roadmap please join us on our public Slack right here.
Our intent is to make it harder to stumble into using JavaScript in ways that is not appropriate, to make things simpler and more intuitive for our main audience of app builders who are not pro developers so that they aren't introducing an X factor into their app that might cause issues down the line. If you feel limited by what value you can get from the Quickbase platform by not being able to rely on JavaScript, we'd love to hear more about what you're working on. I would definitely suggest also checking out the public slack channel below as it is one of the places where we are chatting with people about their needs and sourcing some alternatives. If you weren't able to attend we also had a meeting yesterday with some of the community to talk through the change that we recorded as well.
To those with pressing questions on the Javascript change, for people interested in doing a deep dive on some of the JavaScript "holes" we need to close, supported alternatives and roadmap please join us on our public Slack right here.