X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Envelope-From:	hsank AT nospam DOT chipforge DOT org
X-Envelope-To:	<geda-user AT delorie DOT com>
Date:	Thu, 05 Feb 2015 06:47:26 +0100
Message-ID:	<20150205064726.Horde.V1AXI7ZprtQJDACe67EL8g1@webmail.in-berlin.de>
From:	Hagen SANKOWSKI <hsank AT nospam DOT chipforge DOT org>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] FOSDEM
References:	<1420499386 DOT 3521 DOT 3 DOT camel AT cam DOT ac DOT uk>
	<20150202152654 DOT GA13336 AT cuci DOT nl> <54CFD589 DOT 9040702 AT xs4all DOT nl>
	<CAHBYzfRkn-nJb4JfrDYyaD0WwPrpZvAgi0QdHCusgz185iNoHA AT mail DOT gmail DOT com>
	<CAGde_xN-iNZUvHh-E47kx1EyoPRt1018wWiDwHhYQ9+od+cJwA AT mail DOT gmail DOT com>
	<20150203112631 DOT 3507a0c1 AT Parasomnia DOT thuis DOT lan>
	<20150204054256 DOT Horde DOT Pm1JV8RJbICk9SHvIGwZ7A3 AT webmail DOT in-berlin DOT de>
	<CAOP4iL2stWVCy3WK0=SNu2zAbs8t6B0uyAgFuOnzG8v_MrYNfw AT mail DOT gmail DOT com>
	<CAGde_xN5gs5r_on=HP2RN7cy6E=2EL9eK3cp+sd9BfBaWNLVew AT mail DOT gmail DOT com>
	<20150204193720 DOT Horde DOT 42xUN-NzhCJRWZne-M5eCQ1 AT webmail DOT in-berlin DOT de>
	<90236728-E79D-47C7-BFB1-34140DB85ACB AT sbcglobal DOT net>
	<CAOFvGD4M48Ap=UQzL_T3yzas2rJrNFfxXRUOkOe8gA8J3bQCHg AT mail DOT gmail DOT com>
In-Reply-To:	<CAOFvGD4M48Ap=UQzL_T3yzas2rJrNFfxXRUOkOe8gA8J3bQCHg@mail.gmail.com>
User-Agent:	Internet Messaging Program (IMP) H5 (6.2.0)
MIME-Version:	1.0
Reply-To:	geda-user AT delorie DOT com

Hello.

Quoting Jason White <whitewaterssoftwareinfo AT gmail DOT com>:

> I really like Lua (for ease of use) and Python (for the language and
> libraries). I suspect Lua is lighter-weight and more straight-forward
> to technically implement.

As worker in the ASIC business for more than 15 years, I highly recommend
file formats and languages (for scripting) which are

- already saturated; this means no changes in syntax over night which drive
   you crazy handling different version (e.g Perl 3 -> Perl 5)
- well and open standardized; by well established authorities like ISO,
   IEEE, ANSI etc. (quick & dirty kitchen-sink language hacks are a no-go)
- comfortable for the the community (do not follow current short-living
   fashions)
- quite easy to use (without to much head ache in writing new stuff)
- usable in even two or more decades ahead (did someone still remember the
   hottest languages like Pascal, Modula, Smalltalk, Prolog, Occam .. from
   even the 80's?)

Every small change in language or file formats can cause customers to waste
away effort they already did for circuits and flows.
Sorry, while the kids today at universities have courses in Java for learning
programming, Java is only *one* example of a torture language, nothing more.

Imaging, your teacher is using Klingon as the language to describe common
grammars, does that mean you use this Klingon as language for your  
daily live???
I guess, you do not.

Respecting the points above, languages which seems to be quite  
old-fashioned to
Youngsters and  
Visual-/Java-/Ruby-/Lua-/Go-/Scala-/<younameityourself>-Hipsters
might be even better.

I am comfortable with Scheme and Tcl for scripting and pur ASCII (7-bit got an
standard now - yeah) for file formats (YAML?). Quite easy to parse, even with
the next upcoming fancy holy language. And yes, the incompatibility between
different EDIF versions was a toxic gift.


Regards,
Hagen Sankowski


-- 
"They who can give up essential liberty to obtain a little temporary
safety, deserve neither liberty nor safety." Benjamin Franklin (1775)

- Raw text -