From: David Botton <david@botton.com>
Subject: Re: Ada->Javascript?
Date: Thu, 22 Jan 2015 19:08:06 -0800 (PST)
Date: 2015-01-22T19:08:06-08:00 [thread overview]
Message-ID: <045b6ddb-7daf-458d-9ee9-c7f8289748ab@googlegroups.com> (raw)
In-Reply-To: <ae07eecd-8345-4ff4-85eb-1b620e71f997@googlegroups.com>
> There is also the templates parser for the Ada Web Server.
That wouldn't qualify as Ada running on the browser even in the most remote way of thinking. The idea of Ada -> JS or Ada -> ASM.JS (subset of JS) is to allow for complete client side applications. If Gnoga succeeds to draw interest and funds it will happen sooner rather than later. It's a far more solid solution to use a full client side Ada / Gnoga solution and it offers a better development model than yet another JS replacement language with the same typical DOM access.
When the kids are done with braces they can learn to be engineers :)
In general if there is already a server present using Gnoga it makes more sense for Applications. If just dumping pages of data, the traditional http server model of AWS makes more sense using templates.
David Botton
next prev parent reply other threads:[~2015-01-23 3:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 20:43 Ada->Javascript? tmoran
2015-01-20 21:32 ` Ada->Javascript? David Botton
2015-01-20 22:33 ` Ada->Javascript? Paul Rubin
2015-01-21 4:45 ` Ada->Javascript? tmoran
2015-01-21 20:07 ` Ada->Javascript? David Botton
2015-01-21 21:34 ` Ada->Javascript? tmoran
2015-01-21 21:57 ` Ada->Javascript? David Botton
2015-01-23 1:39 ` Ada->Javascript? brbarkstrom
2015-01-23 3:08 ` David Botton [this message]
2015-01-21 11:25 ` Ada->Javascript? Vadim Godunko
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox