Apple is hard at work for making it's entry to the Search industry. It's crawler, AppleBot is now scouring the web for results and you may have seen this in your server logs:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_1) AppleWebKit/600.2.5 (KHTML, like Gecko) Version/8.0.2 Safari/600.2.5 (Applebot/0.1; +http://www.apple.com/go/applebot)
RESTful interfaces and headless implementations have been on the minds of developers and less technical people alike. This has been the state for a number of years now and frankly the REST hype is getting a bit long in the tooth.
While REST is a technology with merits, the problem is that REST is only used as a baseline technology definition in most cases. There is no specific definition on what a REST API is, that's why many resort to calling them RESTful - to describe that they sort of fulfil the definition. But without knowing exactly what is meant by REST, it's hard to say.
JWT (JSON Web Token) is a contemporary authentication method that is gaining popularity. Instead of sending back and forth cookies with each request, the JWT token is stored by the client and then sent to the server on each request.
Once the server receives the request with a token in the headers, then it is validated and the server then acts depending on if the user is considered valid or not. This is very commonly needed when working with a decoupled setup using GraphQL or RESTful APIs with rich front ends built with technologies such as Angular or React.js.
At the Angularconf 2016 Matt Davis from Mediacurrent discussed the collaboration between the Angular 2 and Drupal communities. Currently Drupal is missing a comprehensive front end framework and is looking at coupling together with Angular to provide a more contemporary administration editing interface.
Drupal and Angular communities are forging a relationship that might have a significant impact on the future of both systems. It seems like a good match to couple Drupal 8 with Angular 2 as both have gone through large changes in the future, but Drupal 8 still lacks a coherent de-facto SPA framework.
Drupal 8 has now been out for six months or so. Adoption looks to be faster than that of Drupal 7 was in it's time. But between January 2011 a lot of water has passed under the bridge. The world of web development is continually changing, but while Drupal 8 has done significant improvements it's still playing with the same hand as Drupal 7 did. Not only technology wise with old (but reliable) MySQL, PHP, jQuery, etc, but conceptually it's a somewhat of a relic.
Recently a giant information leak revealed a number of individuals practising tax evasion using the Panamanian company Mossack Fonseca. In wake of the stories revealing the culprits behind the evasion itself Forbes has done investigative journalism to find the reasons that lead to the leak itself.
The surprising suspect is Free Software. The championed tools that are related with freedom of speech and freedom from evil corporations are indeed used largely everywhere - for good and evil.
Decoupling Drupal and working with a front end framework has been a hot topic in the Drupal Community for a while now. Dries Buytaert has discussed the prospects of different options, and has even credited the Angular 2 team for changing their licensing to be compatible with Drupal.
Drupal 8 is a leap forward in terms of architecture. It's a significant overhaul of the rather ancient imperative codebase from 2001 to something that is a mix of that and modern Object Oriented Programming methods familiar to developers using Java or other similar more advanced languages than PHP was fifteen years ago.