Overview for
php
Twig is everywhere. eZ Platform, Bolt, Drupal 8 and other popular projects have adopted it. At the same time Node.js and Web Components have risen to popularity. This article discusses merging the popular PHP templating engine Twig to Riot.js, a lightweight React-like user interface library using Node.js for server side rendering.
A new Content Management System has joined the constantly growing group of LAMP CMSes using Symfony components as their base. Pagekit is a product built from scratch using modern technologies such as Vue.js, Symfony, Webpack and others.
Written by Jani Tarvainen on Saturday September 12, 2015
Permalink -
Tags:
pagekit, symfony, php, cms
Blackfire is a product that helps developers profile their applications. It is a combination of various tools. It is similar to, Xdebug a PHP extension which provides debugging and profiling capabilities, but the major difference being that you can run it in production without significant overhead.
In autumn of 2014 two popular PHP Content Management tools hoped for more participation from the community. Drupal lead Dries Buytaert was describing Drupal as a Public Good in his essay Scaling Open Source Communities. Meanwhile Matt Mullenweg of WordPress fame was calling for people to spend 5% of their efforts on the WordPress Core in a post titled Five for the Future.
Written by Jani Tarvainen on Sunday September 6, 2015
Permalink -
Tags:
php, drupal, wordpress
The word legacy in the IT word almost exclusively negative connotations. Out of that context it is used more diversely. Consider the legacy left by individuals and organisations such Wolfgang Amadeus Mozart, Michael Jackson and the Greek and Roman Empires. The forementioned empires shed a lot of blood and caused misery, but they continue to live in our everyday lives after thousands of years. That is the power of legacy.
You can have good and bad legacy in IT as well. You could say that Windows ME was built on bad legacy where as Mac OS X was started on good legacy. But all of these have history behind them, just as the code you write today will have in the future. Most of your code is likely disposable, but it's still worth considering the legacy you leave.
RESTful APIs are on the lips of everyone currently. Everyone is got one or will have one very soon. They are always underlined as being full REST APIs. But if you're not fully utilising your API internally, is it really complete and a priority for you?