We're very pleased that you want to get in touch with us. Please fill in the form below:

or   Close this form  
Some content

Peter Pilgrim :: Java Champion :: Digital Developer Architect

I design Java EE and Scala software solutions for the blue-chip clients and private sector

Hey all! Thanks for visiting. I provide fringe benefits to interested readers: checkout consultancy, training or mentorship Please make enquiries by email or call +44 (0)7397 067 658.

Due to the Off-Payroll Working plan for the UK government, I am enforcing stricter measures on contracts. All potential public sector GOV.UK contracts engagements must be approved by QDOS and/or SJD Accounting. Please enquire for further information.

Moving Beyond Java on the JVM: To Be Or Not To Be

21 December 2010 Comments off

2 minutes


Recently, I have been thinking about Java and Moving Beyond Java. I ruminated aloud in a couple of Audioboos and so here are a summarised listable version of these thoughts and ideas.


  • The Mother Language – Lingua franca of the Java Virtual Machine platform
  • Java SE 7
  • Java SE 8
  • Work related. Programming language is risk-averse, it changes slowly and carefully. Oracle steward ensure that it is safe. Business owners and web site owners will be able hire or contract.
  • A de-facto programming language for new learners, students of computer science
  • Die-hard stalwarts can stick with Java the programming language, because eventually some of the benefits of the other languages could make it into Java ecosystem as frameworks and libraries
  • Performance-related Java programming: There is a native-like programming approach for writing Java applications like they do C++ / Speed performance

Beyond Java on the JVM

  • Neil Ford, Ted Newark and Myself are examples of external luminaries (the forces) that are telling you why you should be thinking about moving beyond Java
  • Continued learning
  • Reduction of Boilerplate (Almost all)
  • Declarative programming (JavaFX Script)
  • Ease-of-Development
  • Dynamic typing (Groovy)
  • Scripting language approach
  • Closures (Almost all)
  • Control abstractions (Scala)
  • Improved concurrency models parallel algorithms, actor, CSP and software transactional memory
  • Better simple abstract data types (case classes and objects in Scala)
  • Better language support for immutable object (@Immutable in Groovy)
  • Better annotations (Groovy has loads)
  • Some languages support an object functional approach (Scala, Groovy, Fantom)
  • Other object functional languages may support Higher order functions (Scala, Clojure)

General behaviour, psychology within the movement of herds "staying up to date and getting good".The decision is yours in 2011

No Comments

No comments yet.

RSS feed for comments on this post.

Sorry, the comment form is closed at this time.

Contents of this blog entry are under copyright © 2017 by Peter Pilgrim and associates. For enquiries after republishing, please contact us for permission. All requests for syndicated content will be ignored /dev/null, consider yourself warned!

I help to design, create and build JVM components and services that are behind popular e-commerce websites.

My Blurb

Please get in touch , directly, to establish hire availability, contract & consulting opportunities.

Speaking at Your Conference

Contact by invitation

What Peter Does