View/controller separation, view models and query abstraction are framework-level features. The author of this language is seeking to take the qualities of PHP that make it a 'hypertext preprocessor' and mixing in the no-frills syntax and vocabulary of ruby or python.
I don't understand why you wouldn't just use a framework like Sinatra. It's simple in every way that qualifies it to contend with a 'hypertext preprocessor'. Add it to your gem file, bundle, git commit, push to heroku, deployed! It even has inline templates[1].
You could argue it has a learning curve, but is resistance to learning a good argument against a solid & simple, versatile framework?
I am a big supporter of building applications in consistent way, and the big part of that is being able to code components which do not know anything about the presentation layer. Building these components on hypertext preprocessor is exactly the thing I would not want and would avoid at all costs. We already have it with PHP, and we have learned to follow some practices to live with it.
Well, you may say, this is just for small stuff to run some scripts easily. Well, the reason behind the PHP was the same. And look what it has become :)
Please don't assume I will not use Sinatra just to plug Sinatra here :). I might.
I don't understand why you wouldn't just use a framework like Sinatra. It's simple in every way that qualifies it to contend with a 'hypertext preprocessor'. Add it to your gem file, bundle, git commit, push to heroku, deployed! It even has inline templates[1].
You could argue it has a learning curve, but is resistance to learning a good argument against a solid & simple, versatile framework?
[1] http://www.sinatrarb.com/intro.html#Inline%20Templates