Évaluation De La Valeur À L'ère Du Web: Proposition De Modèle De Valorisation Des Projets Non Marchands

Total Page:16

File Type:pdf, Size:1020Kb

Évaluation De La Valeur À L'ère Du Web: Proposition De Modèle De Valorisation Des Projets Non Marchands Évaluation de la valeur à l’ère du web : Proposition de modèle de valorisation des projets non marchands François Druel To cite this version: François Druel. Évaluation de la valeur à l’ère du web : Proposition de modèle de valorisation des projets non marchands. Sciences de l’ingénieur [physics]. Université d’Angers, 2007. Français. tel- 00346337 HAL Id: tel-00346337 https://tel.archives-ouvertes.fr/tel-00346337 Submitted on 11 Dec 2008 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. UNIVERSITÉ D’ANGERS ANNÉE : 2007 NUMÉRO D’ORDRE : 845 Évaluation de la valeur à l’ère du web : Proposition de modèle de valorisation des projets non marchands ÉCOLE DOCTORALE D’ANGERS THÈSE DE DOCTORAT Spécialité : SCIENCES POUR L’INGÉNIEUR Présentée et soutenue publiquement le 14 novembre 2007 à l’INSTITUT DES SCIENCES ET TECHNIQUES DE L’INGÉNIEUR D’ANGERS 62, avenue Notre-Dame du Lac, Angers par FRANÇOIS DRUEL Devant le jury d’examen composé de : Messieurs : Vincent BOLY : professeur des Universités – ENSGSI – rapporteur Fabrice PAPY : maître de conférence (HDR)– UNIVERSITÉ PARIS VIII – rapporteur Simon RICHIR : professeur des Universités – ENSAM – directeur de thèse Henri SAMIER : maître de conférences – ISTIA INNOVATION – encadrant de recherche Pascal CRUBLEAU : maître de conférences – ISTIA INNOVATION – examinateur Norbert PAQUEL : professeur associé – UNIVERSITÉ PARIS VIII – examinateur LABORATOIRE PRÉSENCE-INNOVATION —ENSAM CENTRE D’ANGERS — 4, rue de l’Ermitage 53000 LAVAL 2 Je dédie ce travail de recherche à la mémoire de JEAN-PAUL NEAU, mon premier mentor. Celui qui m’a ouvert les yeux sur la valeur, le non conformisme et la réflexion. Celui qui a osé me donner le goût de la connaissance et du partage. ii Ce travail n’aurait pas été possible sans le soutien et l’aide de celles et ceux qui m’ont épaulé durant toutes ces années de recherches et que je souhaite remercier ici. Simon RICHIR : directeur du laboratoire PRÉSENCE -INNOVATION pour son accueil au sein de son équipe recherche. Vincent BOLY et Fabrice PAPY : qui ont accepté d’être rapporteurs de cette thèse et dont l’ac- cueil enthousiaste et chaleureux a été pour moi un encouragement. Henri SAMIER : sans qui ce travail n’aurait pas été possible et qui a osé m’ouvrir les portes de la recherche. Qui m’a guidé, aidé, encouragé et qui a dirigé mes travaux pendant toute la durée de mes recherches. Qui, depuis toutes ces années, me montre amicalement la voie. Pascal CRUBLEAU : qui accepté d’évaluer mon travail et de participer au jury de thèse. Norbert PAQUEL : qui m’a fait confiance au début de ma vie professionnelle et dont le soutien amical fut éclairant tout au long de ma démarche de recherches. Laurent BORDET : bibliothécaire de l’ISTIA-INNOVATION, qui m’a prouvé qu’un centre de docu- ment était une source riche de ressources, de réflexions et d’échanges. Philippe DRUEL : pour son aide scientifique ainsi que son regard critique et éclairé tout au long de ma recherche. Élise FURGÉ : pour la relecture critique et la correction de mon manuscrit. André-Yves PORTNOFF : qui par ses travaux m’a permis de construire le présent travail. M. BAUWENS, P. BROWN, J. DRÉO, D. GLAZMAN, J. MICHEL, R. STALLMAN : qui ont accepté de répondre à mes questions lors d’interviews qui ont éclairé mon travail. Bertrand et Sabine SIMON : qui un jour ont accepté que j’ouvre un forum pour les lecteurs de leur site web. Ma famille pour son soutien matériel, logistique et amical durant toutes ces années L’équipe de l’ISTIA -INNOVATION qui m’accompagne depuis si longtemps. iv Table des matières I Introduction 1 1 Motivations, buts de cette recherche et présentation du documment 3 1.1 Motivations . 5 1.2 Buts de cette recherche . 5 1.3 Présentation document . 7 II Contexte de recherche et notions fondamentales 9 2 Contexte de recherche et champ d’investigation 11 2.1 Introduction . 13 2.2 Les technologies de l’information et de la communication . 13 2.2.1 Une réalité technique . 13 2.2.2 Un monde de produits et de services . 14 2.2.3 Des usages à dimension humaine . 15 2.3 La dynamique des produits et des marchés . 16 2.3.1 Les cycles de vie évoluent . 16 2.3.2 Le temps s’accélère . 17 2.4 Une dialectique de changement . 18 2.4.1 Technique, marché et co-conception . 19 2.4.2 L’émergence de l’ouverture . 20 2.5 Une approche par la valeur . 21 2.5.1 Introduction . 21 2.5.2 La création de valeur sur le web marchand . 21 2.5.3 Le changement de paradigme . 24 v 2.6 Champ d’investigation . 26 3 La valeur 29 3.1 Introduction . 31 3.2 La valeur en économie . 31 3.2.1 Libéralisme et valeur . 31 3.2.2 Valeur et subjectivité . 36 3.3 Valeur en analyse de la valeur . 37 3.3.1 L’analyse de la valeur . 37 3.3.2 Définition de la valeur . 37 3.4 La valeur, le client et la vente . 38 3.4.1 Le marketing et la création de valeur . 38 3.4.2 Entreprise et valeur . 38 3.5 Conclusion sur la valeur . 39 4 Réalité du phénomène technologique 41 4.1 Introduction . 43 4.2 Réalité du phénomène technologique . 43 4.2.1 L’équipement en micro-ordinateurs . 43 4.2.2 Les connexions à internet . 44 4.3 L’ humain et la machine . 47 4.3.1 Le rapport à la machine, à l’information, aux médias . 48 4.3.2 L’ humain en groupe : l’ organisation . 54 4.3.3 L’ homo consomatorus . 55 4.4 Conclusion . 55 5 Les outils du partage 57 5.1 Introduction . 59 5.2 Les outils antérieurs au web . 59 5.2.1 Les outils techniques .............................. 59 5.2.2 Les outils courants ............................... 60 5.3 Le web et les outils permis par le web . 61 5.3.1 Le web : un système client-serveur facilitant les usages . 62 5.3.2 Les outils de partage . 65 vi 5.4 Les sous-jacents du partage . 67 5.4.1 Les règles du partage . 68 5.4.2 Les services du partage . 71 5.5 Conclusion sur les outils du partage . 73 6 La collecte de données 75 6.1 Introduction . 77 6.2 Présentation synthétique . 77 6.2.1 Types de données recueillies . 77 6.2.2 Fiabilité et validité . 78 6.3 Les questionnaires . 82 6.3.1 La construction du questionnaire . 82 6.3.2 L’échantillonnage . 83 6.3.3 Les biodata, des données particulières . 84 6.3.4 Administration et dépouillement . 85 6.4 Les interviews . 85 6.5 Conclusion . 86 7 Les méthodes d’interprétation des données 87 7.1 Introduction . 89 7.2 Les méthodes de traitement . 89 7.2.1 Le traitement des données quantitatives . 90 7.2.2 Le traitement des données qualitatives . 91 7.3 L’évaluation multi-critères . 95 7.3.1 L’aide à la décision . 95 7.3.2 L’objet de la décision . 96 7.3.3 L’élaboration des critères . 97 7.3.4 Modélisation des préférences globales . 98 7.4 Conclusion . 98 8 L’évaluation de la valeur de l’immatériel 99 8.1 Introduction . 101 8.2 Caractériser l’immatériel . 101 8.2.1 L’économie de l’immatériel . 101 vii 8.2.2 Le capital immatériel . 102 8.3 Les quatre voies de de l’évaluation . 103 8.4 Panorama des méthodes existantes . 104 8.4.1 Analyse des méthodes d’évaluation de l’immatériel . 104 8.4.2 Ce que nous retenons de nos observations . 105 8.5 La méthode V.I.P : Valorisation Instantanée et prospective . 105 8.5.1 Introduction . 105 8.5.2 Les méthodes d’évaluation des entreprises . 106 8.5.3 le capital réel des organisations . 107 8.5.4 Proposition de la méthode . 107 8.5.5 Les axes et les critères . 108 8.5.6 Ce que nous retenons de l’étude de la méthode VIP . 112 8.6 Conclusion sur les méthodes d’évaluation de l’immatériel . ..
Recommended publications
  • Using Emergent Team Structure to Focus Collaboration
    Using Emergent Team Structure to Focus Collaboration by Shawn Minto B.Sc, The University of British Columbia, 2005 A THESIS SUBMITTED IN PARTIAL FULFILMENT OF THE REQUIREMENTS FOR THE DEGREE OF Master of Science The Faculty of Graduate Studies (Computer Science) The University Of British Columbia January 30, 2007 © Shawn Minto 2007 ii Abstract To build successful complex software systems, developers must collaborate with each other to solve issues. To facilitate this collaboration specialized tools are being integrated into development environments. Although these tools facilitate collaboration, they do not foster it. The problem is that the tools require the developers to maintain a list of other developers with whom they may wish to communicate. In any given situation, it is the developer who must determine who within this list has expertise for the specific situation. Unless the team is small and static, maintaining the knowledge about who is expert in particular parts of the system is difficult. As many organizations are beginning to use agile development and distributed software practices, which result in teams with dynamic membership, maintaining this knowledge is impossible. This thesis investigates whether emergent team structure can be used to support collaboration amongst software developers. The membership of an emergent team is determined from analysis of software artifacts. We first show that emergent teams exist within a particular open-source software project, the Eclipse integrated development environment. We then present a tool called Emergent Expertise Locator (EEL) that uses emergent team information to propose experts to a developer within their development environment as the developer works. We validated this approach to support collaboration by applying our ap• proach to historical data gathered from the Eclipse project, Firefox and Bugzilla and comparing the results to an existing heuristic for recommending experts that produces a list of experts based on the revision history of individual files.
    [Show full text]
  • Oral History of Winifred Mitchell Baker
    ........ Computer • History Museum Oral History of Winifred Mitchell Baker Interviewed by: Marc Weber Recorded: December 10, 2014 Mountain View, California CHM Reference number: X7311.2015 © 2015 Computer History Museum Oral History of Winifred Mitchell Baker Marc Weber: I'm Marc Weber of the Computer History Museum. And I'm here with Mitchell Baker, Chairwoman of Mozilla. Thank you so much for doing this interview. Winifred Mitchell Baker: Thanks, Marc. I'm happy to be here. The museum has been a bright spot for a long time, so I'm honored as well. Weber: Thank you. As am I. So start with a bit of your background. What is your full name? And when and where were you born? Baker: My full name is Winifred Mitchell Baker. My mom was a little eccentric though, and she never wanted me to use Winifred. So it's my first name. But in her mind, I was always Mitchell. So that's what I go by. And I was born in Berkeley in California in 1959. Weber: And tell me a little bit about your family and where you grew up. Baker: I grew up in Oakland, so the East Bay across from San Francisco. It borders Berkeley. My parents were born and raised on the East Coast and moved west, as people did in the '50s, where it seemed [like] starting a new life. They were each eccentric. And each had their own view of their world and really clear opinions. And I think some of that has rubbed off actually. Weber: So eccentric in what way? What did they do? Baker: Well, my dad was a classic entrepreneur.
    [Show full text]
  • Maelstrom Web Browser Free Download
    maelstrom web browser free download 11 Interesting Web Browsers (That Aren’t Chrome) Whether it’s to peruse GitHub, send the odd tweetstorm or catch-up on the latest Netflix hit — Chrome’s the one . But when was the last time you actually considered any alternative? It’s close to three decades since the first browser arrived; chances are it’s been several years since you even looked beyond Chrome. There’s never been more choice and variety in what you use to build sites and surf the web (the 90s are back, right?) . So, here’s a run-down of 11 browsers that may be worth a look, for a variety of reasons . Brave: Stopping the trackers. Brave is an open-source browser, co-founded by Brendan Eich of Mozilla and JavaScript fame. It’s hoping it can ‘save the web’ . Available for a variety of desktop and mobile operating systems, Brave touts itself as a ‘faster and safer’ web browser. It achieves this, somewhat controversially, by automatically blocking ads and trackers. “Brave is the only approach to the Web that puts users first in ownership and control of their browsing data by blocking trackers by default, with no exceptions.” — Brendan Eich. Brave’s goal is to provide an alternative to the current system publishers employ of providing free content to users supported by advertising revenue. Developers are encouraged to contribute to the project on GitHub, and publishers are invited to become a partner in order to work towards an alternative way to earn from their content. Ghost: Multi-session browsing.
    [Show full text]
  • CSS 2.1) Specification
    Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification W3C Editors Draft 26 February 2014 This version: http://www.w3.org/TR/2014/ED-CSS2-20140226 Latest version: http://www.w3.org/TR/CSS2 Previous versions: http://www.w3.org/TR/2011/REC-CSS2-20110607 http://www.w3.org/TR/2008/REC-CSS2-20080411/ Editors: Bert Bos <bert @w3.org> Tantek Çelik <tantek @cs.stanford.edu> Ian Hickson <ian @hixie.ch> Håkon Wium Lie <howcome @opera.com> Please refer to the errata for this document. This document is also available in these non-normative formats: plain text, gzip'ed tar file, zip file, gzip'ed PostScript, PDF. See also translations. Copyright © 2011 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply. Abstract This specification defines Cascading Style Sheets, level 2 revision 1 (CSS 2.1). CSS 2.1 is a style sheet language that allows authors and users to attach style (e.g., fonts and spacing) to structured documents (e.g., HTML documents and XML applications). By separating the presentation style of documents from the content of documents, CSS 2.1 simplifies Web authoring and site maintenance. CSS 2.1 builds on CSS2 [CSS2] which builds on CSS1 [CSS1]. It supports media- specific style sheets so that authors may tailor the presentation of their documents to visual browsers, aural devices, printers, braille devices, handheld devices, etc. It also supports content positioning, table layout, features for internationalization and some properties related to user interface. CSS 2.1 corrects a few errors in CSS2 (the most important being a new definition of the height/width of absolutely positioned elements, more influence for HTML's "style" attribute and a new calculation of the 'clip' property), and adds a few highly requested features which have already been widely implemented.
    [Show full text]
  • A Rustic Javascript Interpreter CIS Department Senior Design 2015-2016 1
    js.rs { A Rustic JavaScript Interpreter CIS Department Senior Design 2015-2016 1 Terry Sun Sam Rossi [email protected] [email protected] April 25, 2016 Abstract trol flow modifying statements. We aimed for correctness in any language feature that JavaScript is an incredibly widespread lan- we implemented. guage, running on virtually every modern computer and browser, and interpreters such This project aimed for breadth of coverage: as NodeJS allow JavaScript to be used as a Js.rs supports more common language fea- server-side language. Unfortunately, modern tures at the cost of excluding certain edge implementations of JavaScript engines are cases. Additionally, Js.rs does not focus on typically written in C/C++, languages re- achieving optimal performance nor memory liant on manual memory management. This usage, as it is a proof-of-concept project. results in countless memory leaks, bugs, and security vulnerabilities related to memory mis-management. 2 Background Js.rs is a prototype server-side JavaScript in- 2.1 Rust terpreter in Rust, a new systems program- ming language for building programs with Rust is a programming language spear- strong memory safety guarantees and speeds headed by Mozilla. It is a general-purpose comparable to C++. Our interpreter runs programming language emphasizing memory code either from source files or an interac- safety and speed concerns. Rust's initial sta- tive REPL (read-evaluate-print-loop), sim- ble release (version 1.0) was released in May ilar to the functionality of existing server- 2015. side JavaScript interpreters. We intend to demonstrate the viability of using Rust to Rust guarantees memory safety in a unique implement JavaScript by implementing a way compared to other commonly used pro- core subset of language features.
    [Show full text]
  • HTML 4.01 Specification
    HTML 4.01 Specification HTML 4.01 Specification W3C Proposed Recommendation This version: http://www.w3.org/TR/1999/PR-html40-19990824 (plain text [786Kb], gzip’ed tar archive of HTML files [367Kb], a .zip archive of HTML files [400Kb], gzip’ed Postscript file [740Kb, 387 pages], a PDF file [3Mb]) Latest version: http://www.w3.org/TR/html40 Previous version: http://www.w3.org/TR/1998/REC-html40-19980424 Editors: Dave Raggett <[email protected]> Arnaud Le Hors <[email protected]> Ian Jacobs <[email protected]> Copyright © 1997-1999 W3C® (MIT, INRIA, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Abstract This specification defines the HyperText Markup Language (HTML), version 4.0 (subversion 4.01), the publishing language of the World Wide Web. In addition to the text, multimedia, and hyperlink features of the previous versions of HTML, HTML 4.01 supports more multimedia options, scripting languages, style sheets, better printing facilities, and documents that are more accessible to users with disabilities. HTML 4.01 also takes great strides towards the internationalization of documents, with the goal of making the Web truly World Wide. HTML 4.01 is an SGML application conforming to International Standard ISO 8879 -- Standard Generalized Markup Language [ISO8879] [p.351] . Status of this document This section describes the status of this document at the time of its publication. Other documents may supersede this document. The latest status of this document series is maintained at the W3C. 1 24 Aug 1999 14:47 HTML 4.01 Specification This document is a revised version of the 4.0 Recommendation first released on 18 December 1997 and then revised 24 April 1998 Changes since the 24 April version [p.312] are not just editorial in nature.
    [Show full text]
  • Brackets Third Party Page (
    Brackets Third Party Page (http://www.adobe.com/go/thirdparty) "Cowboy" Ben Alman Copyright © 2010-2012 "Cowboy" Ben Alman Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. The Android Open Source Project Copyright (C) 2008 The Android Open Source Project All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
    [Show full text]
  • Liste Des Propriétés CSS
    A Liste des propriétés CSS Voici la liste des propriétés CSS telles que décrites dans les documents de la norme CSS 2 (http://www.w3.org/TR/1998/REC-CSS2-19980512/propidx.html). Ceci incorpore donc notamment les propriétés déjà présentes en CSS 1. Tableau A–1 Index des propriétés CSS Nom de la propriété Valeurs Explications azimuth angle, left-side, far-left, Détermine la direction d'origine du son en left, center-left, center, média aural. Les navigateurs actuels ne center-right, right, far-right, gérant pas encore les restitutions vocales, on right-side, behind, leftwards, utilise pour cela des logiciels spécialisés. La rightwards, inherit plupart ne prennent pas encore en charge CSS. background Raccourci pour background-color, background-image, background-repeat, background-attachment, background-position. background- scroll, fixed, inherit Fige une image d'arrière-plan insérée avec attachment background-image. Celle-ci ne défile plus avec le contenu de l'élément auquel elle est appliquée. background-color couleur, transparent, inherit Définit la couleur de fond d'un élément. © Groupe Eyrolles, 2005 Sites et ressources 254 ANNEXES Tableau A–1 Index des propriétés CSS (suite) Nom de la propriété Valeurs Explications background-image URL, none, inherit Affiche une image d'arrière-plan pour l'élé- ment (ou la page dans le cas de la balise body). Par défaut, l'image sera répétée en damier (ou papier peint) à partir du coin supé- rieur gauche de l'élément. background- pourcentage, longueur, top, center, Positionne une image d'arrière-plan définie position bottom, left, right, inherit avec background-image. Propriété géné- ralement utilisée en l'absence de répétition (background-repeat).
    [Show full text]
  • 1. with Examples of Different Programming Languages Show How Programming Languages Are Organized Along the Given Rubrics: I
    AGBOOLA ABIOLA CSC302 17/SCI01/007 COMPUTER SCIENCE ASSIGNMENT ​ 1. With examples of different programming languages show how programming languages are organized along the given rubrics: i. Unstructured, structured, modular, object oriented, aspect oriented, activity oriented and event oriented programming requirement. ii. Based on domain requirements. iii. Based on requirements i and ii above. 2. Give brief preview of the evolution of programming languages in a chronological order. 3. Vividly distinguish between modular programming paradigm and object oriented programming paradigm. Answer 1i). UNSTRUCTURED LANGUAGE DEVELOPER DATE Assembly Language 1949 FORTRAN John Backus 1957 COBOL CODASYL, ANSI, ISO 1959 JOSS Cliff Shaw, RAND 1963 BASIC John G. Kemeny, Thomas E. Kurtz 1964 TELCOMP BBN 1965 MUMPS Neil Pappalardo 1966 FOCAL Richard Merrill, DEC 1968 STRUCTURED LANGUAGE DEVELOPER DATE ALGOL 58 Friedrich L. Bauer, and co. 1958 ALGOL 60 Backus, Bauer and co. 1960 ABC CWI 1980 Ada United States Department of Defence 1980 Accent R NIS 1980 Action! Optimized Systems Software 1983 Alef Phil Winterbottom 1992 DASL Sun Micro-systems Laboratories 1999-2003 MODULAR LANGUAGE DEVELOPER DATE ALGOL W Niklaus Wirth, Tony Hoare 1966 APL Larry Breed, Dick Lathwell and co. 1966 ALGOL 68 A. Van Wijngaarden and co. 1968 AMOS BASIC FranÇois Lionet anConstantin Stiropoulos 1990 Alice ML Saarland University 2000 Agda Ulf Norell;Catarina coquand(1.0) 2007 Arc Paul Graham, Robert Morris and co. 2008 Bosque Mark Marron 2019 OBJECT-ORIENTED LANGUAGE DEVELOPER DATE C* Thinking Machine 1987 Actor Charles Duff 1988 Aldor Thomas J. Watson Research Center 1990 Amiga E Wouter van Oortmerssen 1993 Action Script Macromedia 1998 BeanShell JCP 1999 AngelScript Andreas Jönsson 2003 Boo Rodrigo B.
    [Show full text]
  • Virtual Machines for Dynamic Languages Ausgewählte Kapitel Der Systemsoftwaretechnik, WS2021
    Virtual Machines for Dynamic Languages Ausgewählte Kapitel der Systemsoftwaretechnik, WS2021 Mark Deutel Friedrich-Alexander-University Erlangen-Nürnberg (FAU) Erlangen, Germany [email protected] ABSTRACT threading model. It is common that once a dynamic language has A common approach to execute dynamic languages is inside a vir- grown popular enough the interpreter is extended by a just-in-time tual machine (VM), usually implemented in a low level system (JIT) compiler to more efficiently execute interpreted code. language like C. Such VMs have to support the often complex However this approach does not come without problems. The syntax and semantics of the dynamic languages they are hosting. effort required to write a complete virtual machine from scratch Additionally, some properties of dynamic language code can only is huge. It also forces the language implementer to deal with plat- be inferred at runtime making the optimization of code execution form or target architecture specific details. This makes implement- another challenging task. Therefore, it is hardly possible to provide ing a VM time consuming, error prone, and complicated to port general purpose implementations that support a large range of to other systems. Additionally, modern dynamic languages like different dynamic languages. Furthermore, many commonly used Python, Ruby or JavaScript evolve rapidly and have complex syn- dynamic languages such as Python or Javascript are still evolving tax and semantics. This not only makes it hard to represent the which means that their VMs have to adapt constantly. This implies language properly in low level code, but makes maintenance of that it is necessary to write and maintain a sufficiently elaborated existing VM implementations a complicated task as well.
    [Show full text]
  • Web Evolution and Webassembly
    Web Evolution and WebAssembly COMP 520 - Special Topics Lecture I David Herrera March 29, 2019 Contents ● Limitations of JavaScript ● Evolution of Web performance via asm.js ● WebAssembly ○ Design ○ Pipeline ■ Decoding ■ Validation ■ Execution ○ Examples JavaScript - What is JavaScript? ● Dynamic, high-level language ● 10 days!, Famously designed and prototyped in ten days by Brendan Eich ● Little Performance Design: Language was not designed with performance in mind. ● Web Language: Has been the main programming language for the web since 1999 Limitations of JavaScript ● Tough Target: Dynamically typed nature makes it a “tough target” of static languages such as C and C++, as well as a relatively slow language. ● Lacks Parallelism: No real parallelism supported natively. (At least not widely supported by all browsers, or general with full control) ● Number type: Numbers are restricted to doubles, float64. This means that for instance, an i64 number cannot be represented natively in JavaScript. Let’s look at speed JavaScript as a target language for C/C++? ● Is it Doable? Yes, since JavaScript is turing complete, it should be able to represent any sort of weird semantics. JavaScript as a target language for C/C++? ● Is it Doable? Yes, since JavaScript is turing complete, it should be able to represent any sort of weird semantics. ● Is it efficient? Let’s look at Emscripten ● Emscripten is a static compiler from LLVM to JavaScript created in 2011 ● Asm.js is a“typed” subset of JavaScript which serves as a target for Emscripten ● Initial goal was to support a large enough subset of C and C++ constructs that could be run on the web.
    [Show full text]
  • Le Web Social Table Des Matières
    Le Web Social Table des matières 1 Web social 1 1.1 Historique ............................................... 1 1.2 L'évolution du web social ....................................... 1 1.2.1 Blogs et wiki ......................................... 1 1.2.2 L'art social .......................................... 2 1.2.3 Le crowdsourcing ...................................... 2 1.2.4 Le développement d'applications mobiles .......................... 2 1.2.5 Des projets de logiciels communautaires ........................... 2 1.3 Du web social à la vie réelle ..................................... 2 1.4 Bibliographie ............................................. 3 1.5 Notes et références .......................................... 3 1.6 Voir aussi ............................................... 3 2 Réseautage social 4 2.1 Histoire ................................................ 4 2.2 Applications .............................................. 4 2.3 Modèle économique ......................................... 5 2.3.1 Commerce des données ................................... 5 2.3.2 Vente d'espaces publicitaires ................................. 5 2.3.3 Cession des actifs ....................................... 5 2.4 Domaines d'application ........................................ 5 2.4.1 Réseaux internes versus réseaux externes ........................... 6 2.4.2 Services en ligne de réseautage professionnels ........................ 6 2.4.3 Réseaux sociaux d'amis de la vie réelle ............................ 6 2.4.4 Services en ligne d'ancien
    [Show full text]