Embedded has a use. It always had, ever since microlelectronics. And it most certainly always will.
But IoT is a fad. Pure and simple. It roughly is to the general population today what Ruby on Rails was to programmers 10 years ago. Truckloads of hype that will soon wither and fall back to niche cases when facing the real world.
Es ist mehr als 10 Jahre her, da kamen im offiziellen Kernteam die ersten Gedanken auf, Typo3 nicht nur weiter, sondern von Grund auf neu zu entwickeln. Die Gründe dafür lagen und liegen jedem, der mal mit Typo3 gearbeitet hat – egal ob als Redakteur, Web Worker oder Entwickler – klar auf der Hand. Typo3 ist, wie viele andere PHP CM Systeme auch, historisch und hysterisch gewachsen und ursprünglich von Leuten entwickelt, die mit Programmierung und sauberer Softwarearchitektur, vornehm ausgedrückt, nicht so viel zu tun hatten. Wie bei so vielen PHP basierten Redaktionssystemen hat eine naive Begeisterung für Gefrickel Typo3 zu dem gemacht, was es heute ist – im positiven wie im negativen.
Working with Drupal with a current project because it’s the prime go-to CMS here is like a live alice in wonderland trip. A strange historically grown mess, barely tamed by sanitiy and a relentless chaotic community that all by accident seem to come up with hacks that somehow solve the problem in some way. And yet there’s a solid global corporation building its business all around Drupal [acquia.com]. The surreal hacks with which the Drupal people solve their problems are mindboggling, and yet everybody seems totally OK with it. And Drupals track record of deployments is impressive.
I guess with PHP it’s somehow like the C vs. Lisp argument: C is so shitty compared to Lisp that you have to get yourself together and work as a team, or you won’t get anything done. Hence Lisp has this loner exisitance on the side and all the real work gets done in this ancient C thing.
PHP is a simular thing. It is so bad that no respectable programmer would pick it up voluntarly nowadays, but yet it grew out of Perl (which is worse in some ways), was somewhat of an improvement and was at the right place at the right time. The badness of PHP accounts for its considerable lack of arrogance (compare the PHP community to the Ruby community for instance) and for no one feeling guilty when he does a quick bad hack.
As a programmer you don’t feel dirty when you do bad programming in PHP, you already felt that when you picked PHP as the solution. Hence quite a bit of work gets done in PHP. That’s why PHP has Drupal and Typo3 and Joomla and the Java Community has nothing of that proportions. The barrier of entry into PHP is *very* low which gives it its momentum.