Transcripción
Extracto de la transcripción automática del vídeo realizada por YouTube.
hi my name is Cameron I'm the tract chair for coding and development drupalcon Prague and it's my absolute honor to introduce one of the featured speakers in my track Alec spot those of you who attended Teresa's keynote this morning would have
had a bit of an intro to Alex winter is thanked him but for those who weren't alex is one of only five Drupal 8 core committees in the most recently appointed i think in april so core committer is someone in a very privileged position being one of the
few people can accept changes to the core of Drupal itself so for Drupal 8 we've only got Angie Byron Nathaniel Catchpole Jennifer hodgdon and the docs team dress of course in Alex who can commit code so since April he's already done more than 1,200
commits which is a blistering pace I think three said 50 a week this morning and to put them in perspective I think until then there was only about 2,000 commits on the drip wet trunk so came to call development through its work on the configuration management
initiative which some of you may know about which he became interested in when he was working as lead developer on the Royal Mail project talked a Greek Dunlop became part of that initiative and then was invited by juries to be a cool committed he's now
working full-time in London on drip away and he's an absolutely lovely guy it's really my honor to to introduce him so the theme of the conference is one too many alex is going to talk about how Triple A has incorporated and ideas technologies and
indeed librarians from the wider PHP community and what it means for Drupal now and in the future so Alex take it away Thank You Cameron afternoon everyone so as comments just said I'm here to talk about the Drupal 8 story how we've gone from not invented
here to proudly found elsewhere and we're looking for ideas from outside of the Drupal community outside of PHP on how to make Drupal better so that's who I am he's introduced me so that slide is rather redundant I'm so we'll move on to
who are you I'm hoping that most of you are drupal developers who are new to Drupal 8 and that I'm going to talk to you about why we're making the changes that we've made a Drupal 8 how to talk in Drupal 8 so that when you come to issues and
you look at the way that the codes written you understand what it's what it's trying to do I'm going to talk about some of the advantages about the changes that we've made from a developer perspective so in order to talk about why we've
made the changes to Drupal 8 we had to go back in time so I don't know how many of you know how Drupal started but dribble started in a doormat at university by user one sitting there going hey I want to make a slashdot for my dorm and so that's what
he set out to do he made made the drop org and him and his friends posted messages and started to share the software this has impact on the way that Drupal is written and the the way that the internet was in 1999 also has impacts you know Google was in beta
everyone was using Internet Explorer five there were some advanced things going on on the internet like SETI at home but it was all like bespoke software and the internet was full of tables and it just was a different world and people were using these to access
the internet and these to make phone calls we're not in that world anymore so looking at what we have today we have a Drupal that sitting at the heart of the Internet getting requests from iPhones from kiosk applications from desktops of course from all
sorts of other frameworks and systems yet at the moment drupal 7 assumes the moment it's making a response to requests that is this desktop that's what it does and in Drupal 7 order to get around this the services module does all sorts of evil things
like just exiting straight from co2 any anything you've got that it's going to fire at the end of a response on termination there that won't fire but yep that's Drupal 7 for HTML so at the beginning of the cycle for Drupal 8 Larry Garfield
said the Drupal basically needs to evolve and quickly from the first class web CMS into a first-class rest server that includes the first class web CMS and this has a fundamental impact on the way in which we have to architect Drupal to work and so I'm
going to talk about what that is at the same time the tools on which we built Drupal have been changing so PHP is no longer pH before that it was back in nineteen ninety nine it's embraced concepts and techniques such as oo namespaces and anonymous functions
that we need to embrace because that's that's PHP that's the fundamental language that we're using so Drupal 8 is object orientated because PHP is object oriented so if you if you don't get classes objects and interfaces then now's
the time to start to learn so i'm going to show you why that's important in quite simple numbers drupal 7 has 380 classes basically it's all the DB layer Drupal 8 at the moment has 2816 classes and it's only going to grow so if you want to
develop on Drupal 8 getting comfortable with oo code is going to be mandatory so one of the key things that was introduced in PHP 53 which Drupal 8 assume is the lowest version that the Drupal 8 is going to work on is namespaces and what namespaces allow us
to do is to use classes with the same name like database but take them from different places so with PHP 53 and its new object orientation and namespaces people were sitting around saying well actually this now allows us to share code between our projects
and so in 2009 some people came together under the framework into interoperability group so called PHP fig and proposed PSR 0 which is a way in which projects can share their classes and share their share objects and share functionality so that we don't
[ ... ]
Nota: se han omitido las otras 2.837 palabras de la transcripción completa para cumplir con las normas de «uso razonable» de YouTube.