Talk comments

Good talk, but a bit too short...

Miro,

I realize there are talks and people out there who say things like "REST is not about strict rules" or that you can make up your own style and that an API is great and RESTful as long as it solves your problems.

Roy Fielding says (here: http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven) the following about the matter:

"[...] if the engine of application state (and hence the API) is not being driven by hypertext, then it cannot be RESTful and cannot be a REST API. Period."

And he should know, since he coined the term REST :)

"Secure by design", this is the pragmatic precept that summarizes your great talk about how we should develop our software architectures.

I loved the enthusiasm you injected into your talk, I'm the guy who asked you some advice after your talk: thank you for that, you were lovely and all of you guys at Etsy are really smart!

@Lukas: You are mostly right, you won't typically speed up an application by applying all the best practices I've shown during the presentation. But I still often had improved the general performance (in terms of reqs/second delivered) by chasing the usage of array_merge()/array_unique()/in_array()... Especially when those are used in autoloaders or in frameworks without some cares.

Some well known applications can really be faster by applying those techniques, e.g.: PHP_CodeSniffer which heavily use array()/in_array to implement a "set" to match tokens. You might be surprised by seeing how in_array() is truly the bottleneck into it, however changing that implies a hard BC!