> I was wondering whether anyone had managed to build a system that
> allowed us to create smalltalk backend and front end.

Not yet :)

In Aida this will happen gradually and without noticing it, but
certainly without introducing another language, being JavaScript or
another Smalltalk like Amber. In other worlds, client-side programming
will come in Aida seamlessly and using the same techniques as we are
already using now, like realtime, Ajax etc.

Idea is to introduce more MVC techniques to Aida first (see my this year
ESUG talk) like JavaScript guys are doing in Backbone, EmberJS
AngularJS, then slowly moving more and more processing to client "behind
the scenes". At the end Aida will be able to generate an autonomous
application, which can run standalone without Aida server needed and can
therefore be installed as an App on mobile devices.

We will probably use Amber's compiler to "emit" JS code, but I doubt we
will ever use Amber Smalltalk for development. To avoid "yet another
language" as said at the beginning. Amber is because of deficiencies of
JS VM just different enough from other Smalltalks that is annoying for
everyday work.

Aida needs to stay simple and for everyday business app development, yet
we need stay on the bleeding edge with new web technologies. These two
goals contradict that's why we need to be even more careful choosing the
right strategy for the future. 18 years so far Aida managed to chose
well, so be sure we will find such strategy now too :)

This is at least how I'm currently thinking how to proceed Aida
development in area of client-side/front-end development.