Java 8 is released since 2014. If you are working in an enterprise oriented company, chances are you are only now getting experience with usage of Java 8. You may ask yourself what this warning is telling you.

VM warning: ignoring option MaxPermSize=128M; support was removed in 8.0

If you have previous programming experience but are a newcomer to frontend JavaScript development, the array of jargon and tools can be confusing. Without getting bogged down in detailed discussion, let’s take a general survey of the current “JavaScript landscape”. This should orient you sufficiently to start your journey into frontend development.

The articles touches everything from:

How does client-side JavaScript work, and why use it?

What’s a framework? Do I need to use trendy.js?

Should I be writing JavaScript, or something else? What kinds of JavaScript exist?

If you ever wanted to start with JavaScript development and you are coming from another programming language experience (say Java for example), you might be a little overwhelmed by the JavaScript ecosystem. Maybe you are hearing about Grunt, Angular, Gulp, npm and a lot of other stuff and you don’t know what they are. Infoq.com has an birds-eye view of the JavaScript ecosystem allowing new developers to make somewhat more educated decisions about the the direction they want to go.

In this article we are going to introduce you the version 5 of the framework. We will develop a simple Create/Read/Update/Delete application using Tapestry 5 and show a few of the productivity benefits provided by Tapestry.
We will describe different aspects of Tapestry applications, such as page navigation, dependency and resource injection, user input validation and application state management. You will also see how to use the Ajax functionality built in to Tapestry and how to create your own Ajax-capable components.

If you are interested in the field of SOA technologies you may have noticed that there are two technologies rivaling against each other.
The older on of the two is SOAP/WSDL-based Web services.
The other one is called REST.

Stefan Tilkov has written another article attempting to addresses the 10 of the most common doubts people have about REST when they start exploring it, especially if they have a strong background in the architectural approach behind SOAP/WSDL-based Web services.