| Blog | # of Comments |
|---|---|
| The Unofficial Apple Weblog (TUAW) | 27 Comments |
| Divester | 2 Comments |
| Engadget | 4 Comments |

Now that we've thrown 'em off the trail, use the form below to get in touch with the people at Engadget. Please fill in all of the required fields because they're required.
There are several shortcomings with using a unique templating language like Yuma. First it doesn't support any time of abstraction or MVC architectures. Developers are putting database and business logic directly in their views.
As the Yuma forum points out, it will be difficult (and currently doesn't exist) to find hosting to support Yuma built sites. Developers will be required to host their own applications.
Lastly, because Yuma isn't open-source, developers are beholden to a single company for support, updates, and longevity. What happens if the company goes away? The sites and applications created in Yuma will not be maintainable, requiring complete rewrites of any sites.
Just some things to be aware of for developers considering picking up a proprietary development environment.