Along with Drupal 8 release there has been a lot of noise made about headless Drupal with the REST API. Headless Drupal maybe a great choice for data driven use (such as web applications or mobile apps), but for content driven applications (web sites) a pure headless implementation offers little improvement over more traditional site building methods.
The relationship of Drupal and Acquia is somewhat unclear to newcomers to Drupal. When they get into Drupal they're whole heartedly welcomed to the Open Source community known as Drupal. But the company Acquia keeps popping up when talks of Drupal and Business arise. Let's try to make this a bit more clear
On the internet information is free, but still locked down in relational database formats of CMSes like Drupal or WordPress. Exporting and importing content can be a chore, but agreeing on a proven format will help content migration projects.
WordPress Extended RSS is an extension to the RSS format and could be a universal language for content migrations. It is widely deployed in the WordPress world and offers enough structure for migrating common content structures like news articles and content pages.
We're well into 2015 and it seems that at the PHP 7 crew is holding on to their promise of releasing PHP on time this year. A few days back the PHP team tagged Release Candidate 1 for PHP 7 for release. This is a first sign of an actual release, since there is nothing stopping the PHP 7.0.0 RC1 being the release that actually ships. Probably it won't. but it's looking very good.
Drupal 8 is released soon and it's a great improvement, but still has some technical debt. There has been improvement in it, but there is plenty of legacy legacy left in the code base:
Projects with large codebases, such as WordPress or Drupal, are always going to have more technical debt than small projects such as Silex or Twig. However, large projects usually have lots of contributing developers and thus, technical debt could be more easily assessed on large projects.