It's all about the jumps

Comments

Comments are closed.

Rated 5

James Titcumb at 17:36 on 1 Oct 2016

Well explained, great technical content, and in-depth (as promised!)

Rated 5

Ashley Pinner at 17:44 on 1 Oct 2016

As always, Derick gives a detailed talk about internal PHP things. As always, it's accessible enough to be understandable, but enough to make your head spin with complexity.

Rated 5

Sunil Duggal at 18:12 on 1 Oct 2016

My favourite talk of the entire day loved the examples what php does behind the scenes

Rated 5

Dave Redfern at 22:42 on 1 Oct 2016

A fascinating insight into the steps that the PHP interpreter goes through and what it is actually producing opcode wise. Derek had some useful reminders to be more careful with branching code and that code coverage lies!

Rated 5

Tom de Bruin at 08:45 on 2 Oct 2016

A fascinating insight into what's happening behind the scenes of PHP. Really well presented and very enjoyable.

Rated 5

Chris Emerson at 15:54 on 2 Oct 2016

I really enjoyed this. I like the technical talks more anyway, but have never really looked into how PHP parses and executes code in depth, and Derick provided a great insight into this while still keeping it easy enough to follow along.

Rated 5

Derek Kaye at 16:01 on 2 Oct 2016

Really good talk about the internals of PHP and how your source code gets converted to bytecode.
It was mentioned that things like opcache could optimise some of the resulting bytecode, but what I would like to know in a future talk is as a PHP developer, is how can I take this new knowledge and use it to make my code more efficient. I think this final step was missing.

Excellent talk, good to see the guts of PHP, (took me right back to my lex and yacc classes at uni :) )

Rated 5

Lewis Hides at 11:15 on 3 Oct 2016

A fascinating look at the internal workings of PHP.

Rated 5

Andy Roberts at 11:21 on 3 Oct 2016

The talk was crazy and intriguing - i loved it. Learning about how PHP works internally was inspiring, along with tokeniser, parsing and AST. As expected the talk was delivered confidently and precisely with excellent examples, Derick passion for this subject really shone through.

Interesting to hear how debuggers hook into the abstract syntax tree, and the problems associated with branch code coverage.

The immersion within the PHP internals and the jumps were really interesting, now I feel to understand PHP better thanks to Derick.
One tip would be to make some small pauses or more relaxed moments, since it's highly technical requires total attention, I know its hard to do that due the amount of content, but would be good to have some breaks, other than that everything was really good!

Rated 5

Ben Plummer at 13:56 on 3 Oct 2016

These complex technical talks always attract me but in some cases they are hard to follow. That wasn't the case with Derick's talk. It was really well presented with well laid out slides to make the complex content of the talk accessible. Great to see more of the internal workings of PHP.

I thought that I will be lost in first 5 minutes, but no. The content was well prepared and explained very nicely. I learned a lot from it, about tokenizer and how the php is translated into opcode.

Rated 5

Nigel Greenway at 08:39 on 4 Oct 2016

Watching Derick is always enjoyable. Although this was very low level, it gave me enough to walk away from to look at books to learn from this talk further. Slides were clear and highlighted to give ease of following around.

If you want to get an understanding of PHP under the hood, then I suggest you watch out for this talk...

Rated 5

David Roff at 13:52 on 5 Oct 2016

Dereks a great speaker, every talk I've been to by him has been well presented and interesting, this one didn't fall short of expectations, the topic was quite heavy and you had to think constantly during the talk on what was happening on screen, but this is good as it shows genuine engagement.

Topic gave a good insight to the internal workings, found it strange at first the way some loops are processed (jumping to the end then to the start if condition not met) but now makes sense

Thanks for the insight!