3 ms·
This is...ugh, I don't want to use the word but gross seems to be most fitting. I really don't understand why anyone would do this. Worst yet if your iOS app is
by BinaryIdiot 11y ago
This is...ugh, I don't want to use the word but gross seems to be most fitting. I really don't understand why anyone would do this. Worst yet if your iOS app is interpreting and executing this from an external source than it's against the Apple ToS for the App Store.
- wircho 11y agoAll the logic is executed on the back-end. Front-end is called only for user input and location. We've been using this syntax for a while and it works well for us internally, but we're soon releasing more appealing tools. Read comments below for more details.
- BinaryIdiot 11y ago> All the logic is executed on the back-end. Front-end is called only for user input and location. Fair enough; that wasn't clear to me from reading the article. I still think this is a solution to a non-existent problem. Essentially interfaces solved this type of problem 30 years ago. Today you can implement a set of interfaces and, depending on your language of choice, hot swap / add/ delete them as needed and those can all do exactly what your fancy JSON does but without the proprietary, new syntax and language being introduced.