synon

Split: company and product. Product bias. Lack of context and comparisons.

edit

Is this page about the (defunct?) Synon company or the Synon/Cool/Advantage/AllFusion (or whatever its name is this week) 2e product? Suggest split.

Parts of this article reads more like sales materials than an objective description. Not to denigrate the 2e product/platform, but it is hardly an object oriented language in any accepted sense of the term (i.e., by folks outside of marketing land!). Figures on how many lines of high level language (COBOL? lack of citations!) code are typical marketing -- surely we all have experience with what generated code tends to look like? It might be tight, but bloat is the norm.

When it appeared, I believe the sales hype was more focused around it as a 4GL (fourth generation language) platform rather than 'ARAD', whatever that is supposed to mean, which it remains today: heavily data centric, excellent for generating standard interactions which are close to one's data model and conform to one of its templates, but monolithic, unlayered and hard to extend or adapt for new usages (e.g. service interfaces, workflow automation, web and mobile UI's). Much like other 4GL tools: clear strengths when working within its original scope, but with decided drawbacks in a modern context.

I don't quite feel I have the requisite depth of experience to amend the article, and wouldn't want to get into any religious issues unneccessarily. Any takers?wish you all the best --Pgagge 12:12, 4 August 2006 (UTC)Reply


Agree, the article tastes pretty much like a salesmen' soup. The article also fail to describe about Synon, as an ever popular midrange AS/400 CASE type system which still has its own share in the IT legacy systems market worth millions in US, UK and Europe. I think we don't need to go to the level of detail of data model or the latest industry jargons that Synon is not capable of supporting (now that will sound like a techy web service coder not impressed !) Smet (talk) 20:41, 17 February 2008 (UTC)Reply