Last week Stefan and me took part as guests at the para//el conference in Heidelberg. The actual program was separated into 2 keynotes, one per day, and 36 talks, 18 per day, three at a time (in parallel). Right at the beginning it was said, that we were two out of 150 participants, which, I would say, leads to a nice atmosphere. It wasn't difficult to attend a discussion or meet other people during the pauses and I haven't further experienced, quite contrary to other conferences, any large queueing at launch. Why? Well, someone encountered that a table, if placed correctly, offers space for more than one line at the buffet, which is quite a good news! 🙂
If you nowadays visit a conference, you still might get into contact with sessions where people are talking about monitoring or at least some aspects of it and ALM (application lifecycle management) is a really important discipline a team or project should should take into account right from the beginning and no, this doesn't mean that you should trim or optimize prematurely, but to have an eye on it. Next to the developers and operators we can identify many more stakeholders who are interested in the data, but generally they prefer a different view on the data.
Today's post targets an API, which has been released on Dec. 11, 2006; the
javax.scripting package  and a lot of good articles that have been written around it.
The intention for this post is not about 'how to use the scripting packaging', but about gluse. So what do I mean with the phrase gluse? Gluse is a coinage
for glue and (re)usage. As many of the Java developer know about the plenty of good libraries from maven central / github and the integration process, a few of them
might ask how to integrate libraries from other languages as well. As many of the every day problems have already bean addressed, there is a good chance that someone else has done the job for you and is willing to share.