React, Flux, GraphQL, Hack, HHVM...? All of this and more!
With Angular 2 release just around the corner, there is now discussion on how will the new version take off. Is it just too different from the 1.x branch to catch significant marketshare in the squeeze of React and a multitude of other options?
At the BlinkOn 2016 event held in Munich office of Google on June 16th and 17th 2016 Adam Klein, a Software Engineer working on the V8 JavaScript engine gave some insight on the future of the project. V8 is a significant project as it is powering both the Chrome browser as well as the Node.js server environment.
Google is in a unique position as it is both the market leader in seach engine market. In addition it's providing tools for developers to work work. Google's own JavaScript Framework Angular.js saw great success from 2010, but the first iteration had some technical shortcomings. This is why Google is investing heavily to a major rewrite in Angular2.
Keystone.js is pretty much the first search term when you're googling with terms like JavaScript CMS or Node.js CMF. There are gazillions of other options out there, but after three years of tracking down the perfect Node.js CMS it's the one that keeps coming up.
Many technologies fall down to obscurity only to be rediscovered later. This is especially true for IT technologies where concepts are thought of well before time, but the supporting infrastructure is simply not there yet. One of these is the Opera Platform from the Norwegian company Opera.
At Google I/O in 2016 there were two browser focused technologies from the company. These are the Polymer project and Angular 2. It might be a bit hard to make sense of why the company is investing in these two overlapping and competing projects.
Riot is a lightweight library for building user interfaces. It springs out of the Muut project which is similar to Disqus, for example. This is why the library is needs to be lightweight and work with a lot of other technologies.
The name GraphQL might suggest that it's a language for working with Graph Databases, similar to SQL for relational databases. But GraphQL is actually a technology that is meant for high level communications between applications that can (but don't have to) connect to a Graph Database.
Headless CMSes have been a hot topic for a number of years. In addition to pure platforms that offer a content API, there are also numerous CMSes with a public API that can be used to power a rich front end application.
Directus is a new player in the Content as a Service field. With many options for available for decoupling with a headless CMS, there is an abundance of options out there for people and organizations looking for a robust Content Platform. Is Directus worth a look and what advantage does it hold over more established players?