Re: Web Development Using Ada?

["G.B." <rm-dash-bau-haus@dash.futureapps.de>]

On 31.07.13 10:30, Michael Erdmann wrote:

> BUT there is more to consider: What is about the future of your
> web application ... do you want to develop in the next years with your
> core team or do you intend to outsource the maintenance to some
> external company. In the later case i imagine you might have problem
> to find a company. This is just one aspect of the missing ecosystem
> for Web design in the Ada community.

It's not so bad if compared to the alternatives:

For contrast, the Java+Web market is similarly filled with
idiosyncratic "solutions" in need of specialized maintainers.
The number of frameworks, the number of database "solutions",
the number of configuration tools, the system integration
problems, "architectures" left behind, the next fad, the mobile
challenge, etc. etc. have all created a need
for seemingly hard-to-find skilled workers.

As with Ada, neither Java nor .NET mean "standard solution".
Not even within .NET is there a portable, hence maintainable,
solution. E.g., a Delphi application without its original
developer may be as easily moved to C#/.NET as an Ada+AWS application
is moved to J2EE---the difficulty of either effort will be
influenced by the prior project's use of standard techniques as
opposed to standard "technologies", or "framework stew".

The staffing situation doesn't seem any better in the "scripting
languages" market: Idiosyncrasies abound, and not just in the wild.
The big players happily add to that by adding proprietary
extensions to their editions of the languages, again requiring
specialization. Cf. the sorrow that porting away from Google's
app engine is to those who need to do so.

So, justifying maintenance seems more of a psychological
problem, one of perception, rather than one of language,
or one of technical assets.