SlideShare ist ein Scribd-Unternehmen logo
1 von 72
Downloaden Sie, um offline zu lesen
CRÉATEURS DU WEB
CRÉATEURS DU WEB
      #webnotwar
Make Web Not War 2010 Keynote - Français
LE WEB EST ENCORE
    UN ENFANT
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
Perl
C/C++
TCL/Tk
Make Web Not War 2010 Keynote - Français
<blink></blink>
Make Web Not War 2010 Keynote - Français
Page
Semantique   Page   Contenue
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
NOUS CONSTRUISONS
POUR LA
CONSOMMATION
  D’AUTRES
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
Vos utilisateurs ne se soucient pas du stack technologique de
                      votre application.
Ils veulent seulement que ça fonctionne.
       Et que ça fonctionne bien.
PRAGMATISME
Or, le fait que vos utilisateurs s’en fichent.
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
La technologie bouge vite. Sur le web, encore plus vite.
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
LAYERS

Système d’exploitation
   Base de données
     Serveur web
      Fureteur
LAYERS
OS             OS             OS

DB1            DB2            DB3


      S. web         S. web
          Fureteur
LAYERS
OS                          OS                         OS

DB                          DB                        DB


 OS           OS            OS           OS           OS

Web           Web           Web          Web          Web

       OS            OS           OS           OS
      Proxy         Proxy        Proxy        Proxy

     Fureteurs web                Fureteurs mobiles
LAYERS
OS                          OS                         OS

DB                          DB                        DB


 OS           OS            OS           OS           OS

Web           Web           Web          Web          Web

       OS            OS           OS           OS
      Proxy         Proxy        Proxy        Proxy

     Fureteurs web                Fureteurs mobiles
STANDARDS OUVERTS
STANDARDS OUVERTS

       HTML
STANDARDS OUVERTS

       HTML
        CSS
STANDARDS OUVERTS

       HTML
        CSS
       JSON
STANDARDS OUVERTS

       HTML
        CSS
       JSON
        Atom
STANDARDS OUVERTS

       HTML
        CSS
       JSON
        Atom
        RSS
STANDARDS OUVERTS

       HTML
        CSS
       JSON
        Atom
        RSS
       WSDL
Make Web Not War 2010 Keynote - Français
Make Web Not War 2010 Keynote - Français
L’intéropérabilité n’est pas un option.C’est une obligation.
@JPERRAS


 http://nerderati.com
PHOTOS

Arduino LCD chipset: http://www.flickr.com/photos/spikenzie/

Compact Muon Solenoid, LHC: http://www.flickr.com/photos/muriel_vd

Leatherman Fuse: http://www.flickr.com/photos/origomi

Evil Java: http://www.coderjournal.com/2007/05/java-for-evil-masterminds/

Printing Press: http://www.flickr.com/photos/kokjebalder

Checkmark: http://en.wikipedia.org/wiki/File:Checkmark.png

All language/browser/framework logos are copyright of their respective owners.

All photographs used in this presentation are licensed under the Creative Commons or in the public domain.

Weitere ähnliche Inhalte

Ähnlich wie Make Web Not War 2010 Keynote - Français

Pourquoi choisir les technologies Microsoft
Pourquoi choisir les technologies MicrosoftPourquoi choisir les technologies Microsoft
Pourquoi choisir les technologies MicrosoftSofteam agency
 
JavaScript aussi sur le serveur et jusque dans le cloud?
JavaScript aussi sur le serveur et jusque dans le cloud?JavaScript aussi sur le serveur et jusque dans le cloud?
JavaScript aussi sur le serveur et jusque dans le cloud?benjguin
 
Server Side Javascript in the cloud
Server Side Javascript in the cloudServer Side Javascript in the cloud
Server Side Javascript in the cloudstefounet
 
JavaScript Devoxx France 2013
JavaScript Devoxx France 2013JavaScript Devoxx France 2013
JavaScript Devoxx France 2013Romain Linsolas
 
Alphorm.com Formation le langage SQL
Alphorm.com  Formation le langage SQLAlphorm.com  Formation le langage SQL
Alphorm.com Formation le langage SQLAlphorm
 
Performances Web Mobile
Performances Web MobilePerformances Web Mobile
Performances Web MobileWilly Leloutre
 
La plateforme Web Microsoft
La plateforme Web MicrosoftLa plateforme Web Microsoft
La plateforme Web MicrosoftChristophe Lauer
 
Faire des applications web avec Delphi
Faire des applications web avec DelphiFaire des applications web avec Delphi
Faire des applications web avec Delphipprem
 
Comment intégrer une application ASP.NET dans Windows Azure
Comment intégrer une application ASP.NET dans Windows AzureComment intégrer une application ASP.NET dans Windows Azure
Comment intégrer une application ASP.NET dans Windows AzureMicrosoft Technet France
 
Développement mobile cross-plateform
Développement mobile cross-plateformDéveloppement mobile cross-plateform
Développement mobile cross-plateformStefan Cosquer
 
Du JavaScript propre ? Challenge accepted ! @Devoxx France 2013
Du JavaScript propre ? Challenge accepted ! @Devoxx France 2013Du JavaScript propre ? Challenge accepted ! @Devoxx France 2013
Du JavaScript propre ? Challenge accepted ! @Devoxx France 2013Julien Jakubowski
 
Introduction aux Technologies Web élaborée par Marouan OMEZZINE
Introduction aux Technologies Web élaborée par Marouan OMEZZINEIntroduction aux Technologies Web élaborée par Marouan OMEZZINE
Introduction aux Technologies Web élaborée par Marouan OMEZZINEMarouan OMEZZINE
 
Developper une application mobile
Developper une application mobileDevelopper une application mobile
Developper une application mobileEutech SSII
 
Pourquoi rails est génial? (version longue)
Pourquoi rails est génial? (version longue)Pourquoi rails est génial? (version longue)
Pourquoi rails est génial? (version longue)Camille Roux
 
Construire Des Applications Cloud Natives - SymfonyLive Paris 2016
Construire Des Applications Cloud Natives - SymfonyLive Paris 2016Construire Des Applications Cloud Natives - SymfonyLive Paris 2016
Construire Des Applications Cloud Natives - SymfonyLive Paris 2016Ori Pekelman
 
Demarrer ionic en 5 etape
Demarrer ionic en 5 etapeDemarrer ionic en 5 etape
Demarrer ionic en 5 etapeZaïd BOUDAMOUZ
 
Gab17 lyon-Docker pour quoi faire - Cédric Leblond et Derue
Gab17 lyon-Docker pour quoi faire - Cédric Leblond et DerueGab17 lyon-Docker pour quoi faire - Cédric Leblond et Derue
Gab17 lyon-Docker pour quoi faire - Cédric Leblond et DerueAZUG FR
 

Ähnlich wie Make Web Not War 2010 Keynote - Français (20)

Pourquoi choisir les technologies Microsoft
Pourquoi choisir les technologies MicrosoftPourquoi choisir les technologies Microsoft
Pourquoi choisir les technologies Microsoft
 
Do you speak technique ?
Do you speak technique ?Do you speak technique ?
Do you speak technique ?
 
JavaScript aussi sur le serveur et jusque dans le cloud?
JavaScript aussi sur le serveur et jusque dans le cloud?JavaScript aussi sur le serveur et jusque dans le cloud?
JavaScript aussi sur le serveur et jusque dans le cloud?
 
Server Side Javascript in the cloud
Server Side Javascript in the cloudServer Side Javascript in the cloud
Server Side Javascript in the cloud
 
Web services SOAP et REST
Web services  SOAP et RESTWeb services  SOAP et REST
Web services SOAP et REST
 
JavaScript Devoxx France 2013
JavaScript Devoxx France 2013JavaScript Devoxx France 2013
JavaScript Devoxx France 2013
 
jQuery mobile vs Twitter bootstrap
jQuery mobile vs Twitter bootstrapjQuery mobile vs Twitter bootstrap
jQuery mobile vs Twitter bootstrap
 
Alphorm.com Formation le langage SQL
Alphorm.com  Formation le langage SQLAlphorm.com  Formation le langage SQL
Alphorm.com Formation le langage SQL
 
Performances Web Mobile
Performances Web MobilePerformances Web Mobile
Performances Web Mobile
 
La plateforme Web Microsoft
La plateforme Web MicrosoftLa plateforme Web Microsoft
La plateforme Web Microsoft
 
Faire des applications web avec Delphi
Faire des applications web avec DelphiFaire des applications web avec Delphi
Faire des applications web avec Delphi
 
Comment intégrer une application ASP.NET dans Windows Azure
Comment intégrer une application ASP.NET dans Windows AzureComment intégrer une application ASP.NET dans Windows Azure
Comment intégrer une application ASP.NET dans Windows Azure
 
Développement mobile cross-plateform
Développement mobile cross-plateformDéveloppement mobile cross-plateform
Développement mobile cross-plateform
 
Du JavaScript propre ? Challenge accepted ! @Devoxx France 2013
Du JavaScript propre ? Challenge accepted ! @Devoxx France 2013Du JavaScript propre ? Challenge accepted ! @Devoxx France 2013
Du JavaScript propre ? Challenge accepted ! @Devoxx France 2013
 
Introduction aux Technologies Web élaborée par Marouan OMEZZINE
Introduction aux Technologies Web élaborée par Marouan OMEZZINEIntroduction aux Technologies Web élaborée par Marouan OMEZZINE
Introduction aux Technologies Web élaborée par Marouan OMEZZINE
 
Developper une application mobile
Developper une application mobileDevelopper une application mobile
Developper une application mobile
 
Pourquoi rails est génial? (version longue)
Pourquoi rails est génial? (version longue)Pourquoi rails est génial? (version longue)
Pourquoi rails est génial? (version longue)
 
Construire Des Applications Cloud Natives - SymfonyLive Paris 2016
Construire Des Applications Cloud Natives - SymfonyLive Paris 2016Construire Des Applications Cloud Natives - SymfonyLive Paris 2016
Construire Des Applications Cloud Natives - SymfonyLive Paris 2016
 
Demarrer ionic en 5 etape
Demarrer ionic en 5 etapeDemarrer ionic en 5 etape
Demarrer ionic en 5 etape
 
Gab17 lyon-Docker pour quoi faire - Cédric Leblond et Derue
Gab17 lyon-Docker pour quoi faire - Cédric Leblond et DerueGab17 lyon-Docker pour quoi faire - Cédric Leblond et Derue
Gab17 lyon-Docker pour quoi faire - Cédric Leblond et Derue
 

Make Web Not War 2010 Keynote - Français

Hinweis der Redaktion

  1. Joke about being homeless hippy, aka open source developer. As developers, we possess the ability to shape and make the web of tomorrow. While the role of &apos;web developer&apos; is relatively new in the grand scheme of things, the infancy of our profession has not hindered the rapid pace of development. In a short amount of time we have created languages, tools and methodologies that have allowed us to develop ever increasingly complex applications used by hundreds of millions of people around the world. These tools, however, are only building blocks towards a goal that all developers share: to make the web a more informative, interactive and useful place. Now more than ever, the interoperability between various application and data layers is of utmost importance, and increasingly more effort is being put forth in this endeavour by individuals and corporations alike, including Microsoft.
  2. The web is still a child. No matter how much ajax, html5 or other buzzwords you throw around, we&apos;re still not very sure about what it is we&apos;re doing, and what goals we&apos;re trying to attain. In the late nineties we were poking around in the dark, getting a feel for what this new &apos;web&apos; could do. Now, we&apos;ve got a little flashlight that helps us navigate, but we still don&apos;t see the big picture. But we&apos;re getting there.
  3. The tools of our trade have evolved. (ask about first programming language people learned)
  4. We&apos;ve come a long way from tiny Perl and C/C++ CGI scripts for counting page views and providing an in-page guestbook, and times where the only &apos;dynamic&apos; part of a web site (because the term &apos;web application&apos; didn&apos;t really apply) was the [CHANGE SLIDE] overzealous use of the &lt;blink&gt; tag
  5. We&apos;ve come a long way from tiny Perl and C/C++ CGI scripts for counting page views and providing an in-page guestbook, and times where the only &apos;dynamic&apos; part of a web site (because the term &apos;web application&apos; didn&apos;t really apply) was the [CHANGE SLIDE] overzealous use of the &lt;blink&gt; tag
  6. We&apos;ve come a long way from tiny Perl and C/C++ CGI scripts for counting page views and providing an in-page guestbook, and times where the only &apos;dynamic&apos; part of a web site (because the term &apos;web application&apos; didn&apos;t really apply) was the [CHANGE SLIDE] overzealous use of the &lt;blink&gt; tag
  7. We learned that it was best to separate design and layout from markup and content
  8. We learned that it was best to separate design and layout from markup and content
  9. We learned that Java Applets were a neat trick. And then we learned that we needed some new and colourful curse words for sites that had these applets.
  10. But, no matter how advanced (or simplistic) our tools become, we need to remember one vital fact: The web that we build is one that is made [CHANGE SLIDE] to be consumed by others. We might be the _makers_ of the web, but we are not it&apos;s target audience.
  11. We didn&apos;t build Flickr,
  12. or Facebook,
  13. or LinkedIn, for people like you and I - we built them for people who don&apos;t know the difference between HTML and CSS. And that&apos;s not a bad thing.
  14. Think of all the non-web-based media that you and I consume on a daily basis: should we know _how_ a liquid crystal display works in order to enjoy our favourite TV show?
  15. Should I need to know the fundamentals of offset lithography in order to read the newspaper? The answers to these questions are, of course, categorically no.
  16. As a direct corollary to this, we can conclude that the end users of the web don&apos;t care at all about the tools that were used to build the applications they love. And why should they? The end-user (our target audience), experiences the end product of our labours - the rendered content and the interactive features that our Javascript and/or Flash chops are able to produce.
  17. They don&apos;t care how it&apos;s done; hand-coded Javascript, MooTools, HAML, PHP, Ruby, C#, it&apos;s all the same (and it&apos;s all gibberish) to them. The &apos;average&apos; web user is, in fact, the most pragmatic person you will ever meet: they don&apos;t care _how_ it works, they only care that it _works_ and that it _works _well_.
  18. And because of that, we web developers have a hard job. A really hard job. A job that requires us to dedicate hours of time each week just to discover and learn about the technologies and techniques that were developed the week prior. With this ever-changing landscape of tools and tech, we as a profession have grown to not only expect, but to _require_ interoperability between the various layers that make up today&apos;s web applications. This allows us to select the best tool for the job at hand, regardless of our choice of platform or operating system. [GO INTO LANGUAGES]
  19. Some examples of how users shouldn&amp;#x2019;t care: browsers. Gone are the days where we would use tags like &amp;#x2018;Best viewed in Netscape 4.1&amp;#x2019;
  20. End users have plethora of browsers at our disposal - Firefox,
  21. Safari,
  22. Internet Explorer
  23. Chrome - many of which run on several operating systems.
  24. We also have runtimes like Silverlight
  25. and Adobe Air, which allow us to develop desktop applications using the web technologies we are familiar with.
  26. If we go down a layer, we have the various Javascript frameworks that abstract away the common functionality needed for highly interactive, rich applications - jQuery, MooTools, YUI, Dojo make our lives as developers easier by providing a consistent and fluid API for interoperating with the various browsers&apos; idiosyncrasies. [GO INTO THE PAIN OF THE DOCUMENT OBJECT MODEL]
  27. If we go down a layer, we have the various Javascript frameworks that abstract away the common functionality needed for highly interactive, rich applications - jQuery, MooTools, YUI, Dojo make our lives as developers easier by providing a consistent and fluid API for interoperating with the various browsers&apos; idiosyncrasies. [GO INTO THE PAIN OF THE DOCUMENT OBJECT MODEL]
  28. If we go down a layer, we have the various Javascript frameworks that abstract away the common functionality needed for highly interactive, rich applications - jQuery, MooTools, YUI, Dojo make our lives as developers easier by providing a consistent and fluid API for interoperating with the various browsers&apos; idiosyncrasies. [GO INTO THE PAIN OF THE DOCUMENT OBJECT MODEL]
  29. If we go down a layer, we have the various Javascript frameworks that abstract away the common functionality needed for highly interactive, rich applications - jQuery, MooTools, YUI, Dojo make our lives as developers easier by providing a consistent and fluid API for interoperating with the various browsers&apos; idiosyncrasies. [GO INTO THE PAIN OF THE DOCUMENT OBJECT MODEL]
  30. The web pages that get served to the browsers are generated by a webserver - Apache, IIS, nginx, lighty, mongrel, etc., all of which attempt to adhere to a common standard for processing HTTP requests. Going further, we then have our choice of languages for the application middle-tier: PHP, Ruby, Python, C#, Java, SmallTalk, Erlang, Clojure... a virtual cornucopia of choice. And the meat of most web applications, the persistent storage, is no different - there are more relational databases, cloud-based storage solutions, map/reduce clusters, document stores, column stores and XML (sadly) persistent storage engines out there than any one person could ever hope to understand them all.
  31. And the real crazy part of all this: I can use them all. Actually, not only can I use all of the above technologies for my application, but for the most part I can mix and match to my heart&apos;s desire. PHP over IIS with jQuery for some snazzy visual effects on the front-end and CouchDB as my persistent document store? Check. Ruby with Apache as the webserver, Cassandra as my column store and Dojo for my online store? Check. Gone are the days where software was written to work on one specific hardware specification. Platform and technology agnosticism is the new black, and I think it&apos;s here to stay.
  32. And a lot of that is due to open, public specifications and standards.
  33. And a lot of that is due to open, public specifications and standards.
  34. And a lot of that is due to open, public specifications and standards.
  35. And a lot of that is due to open, public specifications and standards.
  36. And a lot of that is due to open, public specifications and standards.
  37. And a lot of that is due to open, public specifications and standards.
  38. Interoperability is no longer a &apos;feature&apos; - it&apos;s a necessity. It&apos;s a real wonder any of us got into this profession at all - long hours, difficult clients, apathetic end-users, not to mention the endless shift and movement of the underlying technologies that we make our living using and developing.