Breaking Technologies
•Download as KEY, PDF•
0 likes•2,329 views
This is a @JSConfEU talk about how we interact with technology and how we should maybe rethink our god-like approach to software languages. It also showcases an experiment that allows developers to interact with PHP directly from Node.js.
Recommended
More Related Content
Viewers also liked
Viewers also liked (19)
Similar to Breaking Technologies
Similar to Breaking Technologies (8)
More from David Coallier
More from David Coallier (15)
Recently uploaded
Recently uploaded (20)
Breaking Technologies
- 3. Story @davidcoallier — @JSConfEU 2011
- 4. Perpetual Learner @davidcoallier — @JSConfEU 2011
- 5. Constraints Suck @davidcoallier — @JSConfEU 2011
- 6. Think Outside The Box @davidcoallier — @JSConfEU 2011
- 7. Consider The Following @davidcoallier — @JSConfEU 2011
- 8. 1889 @davidcoallier — @JSConfEU 2011
- 9. Naples, Italy @davidcoallier — @JSConfEU 2011
- 10. Queen Margherita @davidcoallier — @JSConfEU 2011
- 11. Raffaele Esposito @davidcoallier — @JSConfEU 2011
- 15. Think Outside The Box. @davidcoallier — @JSConfEU 2011
- 16. Trolley + Suitcase @davidcoallier — @JSConfEU 2011
- 18. Foosball + Arduino + Cloud + HTML5 + CouchDB @davidcoallier — @JSConfEU 2011
- 19. @davidcoallier — @JSConfEU 2011
- 20. Perl + C @davidcoallier — @JSConfEU 2011
- 21. cpp + v8 + awesumsauce @davidcoallier — @JSConfEU 2011
- 22. It’s intrinsic. @davidcoallier — @JSConfEU 2011
- 24. God Complex @davidcoallier — @JSConfEU 2011
- 25. Users are worth more than technology @davidcoallier — @JSConfEU 2011
- 26. “All War is Deception” —Sun Tzu @davidcoallier — @JSConfEU 2011
- 27. For Instance. @davidcoallier — @JSConfEU 2011
- 29. Taxi... @davidcoallier — @JSConfEU 2011
- 30. Schadenfreude @davidcoallier — @JSConfEU 2011
- 31. “Pleasure Derived from the misfortune of others” @davidcoallier — @JSConfEU 2011
- 32. “We are not robots” @davidcoallier — @JSConfEU 2011
- 33. “Use what makes sense” @davidcoallier — @JSConfEU 2011
- 34. Rapid Rant @davidcoallier — @JSConfEU 2011
- 35. Node.js @davidcoallier — @JSConfEU 2011
- 36. PHP And the innovator’s dilemma @davidcoallier — @JSConfEU 2011
- 38. The Experiment @davidcoallier — @JSConfEU 2011
- 39. Engineer. @davidcoallier — @JSConfEU 2011
- 40. Open Source is my life. @davidcoallier — @JSConfEU 2011
- 41. I <3 HTML5 Kinda. @davidcoallier — @JSConfEU 2011
- 42. I <3 PHP @davidcoallier — @JSConfEU 2011
- 43. I <3 JavaScript @davidcoallier — @JSConfEU 2011
- 44. I <3 WebSockets @davidcoallier — @JSConfEU 2011
- 45. I <3 Python @davidcoallier — @JSConfEU 2011
- 46. I <3 Erlang @davidcoallier — @JSConfEU 2011
- 47. I <3 Technology. @davidcoallier — @JSConfEU 2011
- 48. I had code, But no time. @davidcoallier — @JSConfEU 2011
- 49. “What if I could run PHP from Node.js” - Me on a friday night after many drinks @davidcoallier — @JSConfEU 2011
- 50. Let’s show off. @davidcoallier — @JSConfEU 2011
Editor's Notes
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- We are merely owners of our own realms/reich\n
- We are merely owners of our own realms/reich\n
- We are merely owners of our own realms/reich\n
- We are merely owners of our own realms/reich\n
- We are merely owners of our own realms/reich\n
- We are merely owners of our own realms/reich\n
- We are merely owners of our own realms/reich\n
- We are merely owners of our own realms/reich\n
- - Incumbents do not generally react to disruptive technology until it&#x2019;s too late.\n- Up to a few years ago that was PHP.\n
- - Incumbents do not generally react to disruptive technology until it&#x2019;s too late.\n- Up to a few years ago that was PHP.\n
- - Disruptive, disagree with the status-quo\n
- - Disruptive, disagree with the status-quo\n
- - Incumbents do not generally react to disruptive technology until it&#x2019;s too late.\n- Up to a few years ago that was PHP.\n
- - Incumbents do not generally react to disruptive technology until it&#x2019;s too late.\n- Up to a few years ago that was PHP.\n
- - Incumbents do not generally react to disruptive technology until it&#x2019;s too late.\n- Up to a few years ago that was PHP.\n
- - Incumbents do not generally react to disruptive technology until it&#x2019;s too late.\n- Up to a few years ago that was PHP.\n
- - Incumbents do not generally react to disruptive technology until it&#x2019;s too late.\n- Up to a few years ago that was PHP.\n
- - Semantics changes\n- Moving target\n- Predefined class names ... error class only on certain elements, not on div or em&#x2019;s for instance.\n
- - Incumbents do not generally react to disruptive technology until it&#x2019;s too late.\n- Up to a few years ago that was PHP.\n
- - Incumbents do not generally react to disruptive technology until it&#x2019;s too late.\n- Up to a few years ago that was PHP.\n
- - Incumbents do not generally react to disruptive technology until it&#x2019;s too late.\n- Up to a few years ago that was PHP.\n
- - Incumbents do not generally react to disruptive technology until it&#x2019;s too late.\n- Up to a few years ago that was PHP.\n
- - Incumbents do not generally react to disruptive technology until it&#x2019;s too late.\n- Up to a few years ago that was PHP.\n
- - Incumbents do not generally react to disruptive technology until it&#x2019;s too late.\n- Up to a few years ago that was PHP.\n
- - Incumbents do not generally react to disruptive technology until it&#x2019;s too late.\n- Up to a few years ago that was PHP.\n
- - Incumbents do not generally react to disruptive technology until it&#x2019;s too late.\n- Up to a few years ago that was PHP.\n
- - Incumbents do not generally react to disruptive technology until it&#x2019;s too late.\n- Up to a few years ago that was PHP.\n
- - If you were expecting an in-depth tech-talk I&#x2019;m sorry but I sure hope that you take something back from this with regards to your language, your community and how thinking outside the box can create pretty cool things.\n