DOCSLIB.ORG

State of Python

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

1 The State of Python Francisco Santos, Nuno Cerqueira, Ricardo Barreira, Rui Martins FEUP - Faculdade de Engenharia da Universidade do Porto Rua Dr. Roberto Frias, s/n, 4200-465 Porto, Portugal [email protected], [email protected], [email protected], [email protected] Abstract. In this article we describe the current state of the relatively recent Python programming language, which is an interpreted language with a simple syntax. Although often referred as a scripting language, it has a degree of functionality similar to the mainstream languages. Python’s philosophy is based on adaptability, flexibility and dynamism, supporting multiple programming paradigms. Some of the most useful and well known languages’ libraries and frame- works are then described. Among others, we present: SciPy, a library that offers useful scientific functions (e.g. Fast Fourier Transform); Tur- boGears, a framework that allows rapid front-to-back Web Development, including automatic mapping of databases; and wxPython, a framework to implement applications that use multi-platform native GUI widgets. In the end, we present a set of conclusions regarding the benefits of using Python as a general-purpose programming language. 1 Introduction Computer Science is a very recent subject. Despite that, it has suffered an ex- ceptional growth, since in just half a century1 it became the centre of the In- formation Society, having an immense number of daily-use applications. With a growth rate of this magnitude, it is normal that several branches appear in its development, as a reaction to the different types of people involved, as well as their different needs. Nowadays there are millions of developers all around the world, with a multi- tude of cultures, education and needs. This variety is mirrored in the existing pro- gramming languages. There are some mainstream programming languages (like Java, C++ and C#), used widely due to their enterprise nature or capabili- ties in certain key domains. However, in other tasks these languages are quite inefficient2 and are outperformed by languages of another kind. Python [16] is not a very well known language and it is not a mainstream one, although its features allow the same degree of functionality of these lan- guages, but frequently in an easier way (for programmers with the same degree of familiarity). 1 The first high-level programming languages were invented in the 1950s: COBOL, FORTRAN and Lisp. 2 In this case, the performance of a programming language is not given only by its computational efficiency, but also by its capabilities, programmer productivity. F. Santos, N. Cerqueira, R. Barreira, R. Martins 2 F. Santos, N. Cerqueira, R. Barreira, R. Martins With this article we intend to “spread the word” about Python, describing its current state. In this section (Sect. 1) we present the context on which Python is inserted, the goals and structure of this document. In The Python Programming Language (Sect. 2) we describe the language features, its philosophy, history and future. In Libraries (Sect. 3) we describe some important libraries that extend the language, adding usefulness and power to it. In Frameworks (Sect. 4), we describe some Python frameworks that allow to easily create domain specific applications. Finally, in Conclusions (Sect. 5) we present a small summary of Python’s current state and issue some comments on its usage and evolution. 2 The Python Programming Language 2.1 History Python is a relatively recent language. It was created in 1990 by Guido van Rossum at the CWI 3 in the Netherlands. Guido van Rossum was an experienced programmer and had been previously involved in the creation of the ABC programming language [5], also at the CWI. The lack of flexibility of ABC, along with his general dissatisfaction with other programming languages made him create Python. In its development he took advice and suggestions from several programmers, and a small Internet based community started to grow. After some problems with the licensing of the language, finally Python be- came completely Open Source. This event took place even before of the global establishment of the word Open Source. During this process, and due to the language’s features, the Python community had had an astounding growth as lots of people were contributing with very useful modules. The Python Software Foundation [14] was then created to satisfy the need for guidance that this evolution had created. This foundation is “(. ) a non-profit membership organization devoted to advancing open source technology related to the Python programming language”. One of its main purposes is to organize the PyCon – an annual conference where the state and evolution of Python is discussed, as well as the applications using it. Nowadays, pythoneers4 are very involved and actively developing applica- tions, frameworks and modules which contribute to the language’s growth. As a final remark, the name Python is often associated with snakes, which is wrong. As the author asserts frequently Python is really all about “spam, ham and eggs”, in a reference to Monty Python, the famous british comedian group. It is very common to see references to the series in Python’s code, tutorials and reference materials. 3 CWI stands for Centrum voor Wiskunde en Informatica, or National Research In- stitute for Mathematics and Computer Science. 4 A common name used for the members of the Python community. The State of Python 3 2.2 Philosophy Python is a high level dynamic programming language designed to ease the pro- grammer’s work, allowing him to spend most of the time with application prob- lems rather than dealing with the artifacts of the language. It also has some syntax constraints that force a more readable code, like rigid whitespace based indentation. It also aims to be an unambiguous language, meaning its code should be explicit about what it is doing, and also that there should be one, and only one, obvious way to do something. Python is a multi-paradigm language which means that the programmer has a wide range of paradigms to choose from when solving a problem, he could use object orientation, functional programming as well as aspect orientation or even design by contract. Another important goal of the language is its extensibility, integrating na- tively new C or C++ modules (as will be described in Sect. 2.5). 2.3 Language Features The Python programming language combines the most common features of mod- ern programming languages, like modules, classes, exceptions, high-level dynamic data types and dynamic typing. Modules permit a better code organization for large projects and also open the road for continuous expansion of the language by adding new libraries with new functionalities. Classes add the power of Object Oriented Programming (OOP), like in C++ or Java, giving more flexibility and easing changes to programs. OOP is consid- ered to be easier to learn by newcomers and it leads to a better direct analysis, coding, understanding of complex situations and procedures than other program- ming methods. Exceptions are a programming construct designed to handle runtime errors or other problems which occur during the execution of a computer program. They help the programmer to deal with unexpected situations that could be harder to spot otherwise. Also, because exceptions should be exceptional, the language doesn’t force the programmer to catch every single thrown exception as Java does. Should an exception occur, the language assumes that the application is better off by immediately exiting and printing the exception stack trace. Python supports the common high-level programming language data types: basic types like integers, decimals, characters and strings; collection types like lists, tuples and dictionaries; and object types that can be dynamically created as complex structures of other data types. Dynamic typing is a feature that permits a variable to change type during the execution of the program. It’s possible to start using a variable as an integer number and later use it as a string. Dynamic typing is a key language feature and one of the greatest causes for the reduction of code length in the application comparing to other static typed languages such as C++ or Java. 4 F. Santos, N. Cerqueira, R. Barreira, R. Martins 2.4 Python Versus Other Programming Languages It is not always easy to make a clear classification on how good a language is, when compared to others. Most of the comparisons available on the web are strongly biased because they’re written by “zealots”. Python has its own fair share of this. Like “VI versus Emacs”, “KDE versus Gnome” or “BSD versus Linux”, also Python has its own neverending debates titled “Python versus Perl”. Python, Perl and Ruby are similar when it comes to language power compar- ison. Some people might argue that language A has this feature which language B doesn’t, but in the end, they just have different ways of getting things done. Perl language emphasizes strings and regular expression manipulation, so it is expected that if you’re looking for these features, you’ll get you’re goals done easier by using Perl. This however doesn’t mean that it can’t be done in Python or Ruby. It simply is done in a different way. A common acceptance point is that Python code is easier to read than other languages. Because indentation is part of the language syntax, Python code generated in different projects always tends to look the same. This is undoubtedly a major maintainability asset for large projects and you can’t get this feature for free in other languages unless you impose well defined rules regarding the project’s code layout. It is also very usual to see Python compared to Java or C/C++ as far as performance is concerned.
Recommended publications
  • GNU/Linux AI & Alife HOWTO

    GNU/Linux AI & Alife HOWTO

    GNU/Linux AI & Alife HOWTO GNU/Linux AI & Alife HOWTO Table of Contents GNU/Linux AI & Alife HOWTO......................................................................................................................1 by John Eikenberry..................................................................................................................................1 1. Introduction..........................................................................................................................................1 2. Symbolic Systems (GOFAI)................................................................................................................1 3. Connectionism.....................................................................................................................................1 4. Evolutionary Computing......................................................................................................................1 5. Alife & Complex Systems...................................................................................................................1 6. Agents & Robotics...............................................................................................................................1 7. Statistical & Machine Learning...........................................................................................................2 8. Missing & Dead...................................................................................................................................2 1. Introduction.........................................................................................................................................2
  • Ironpython in Action

    Ironpython in Action

    IronPytho IN ACTION Michael J. Foord Christian Muirhead FOREWORD BY JIM HUGUNIN MANNING IronPython in Action Download at Boykma.Com Licensed to Deborah Christiansen <[email protected]> Download at Boykma.Com Licensed to Deborah Christiansen <[email protected]> IronPython in Action MICHAEL J. FOORD CHRISTIAN MUIRHEAD MANNING Greenwich (74° w. long.) Download at Boykma.Com Licensed to Deborah Christiansen <[email protected]> For online information and ordering of this and other Manning books, please visit www.manning.com. The publisher offers discounts on this book when ordered in quantity. For more information, please contact Special Sales Department Manning Publications Co. Sound View Court 3B fax: (609) 877-8256 Greenwich, CT 06830 email: [email protected] ©2009 by Manning Publications Co. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by means electronic, mechanical, photocopying, or otherwise, without prior written permission of the publisher. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in the book, and Manning Publications was aware of a trademark claim, the designations have been printed in initial caps or all caps. Recognizing the importance of preserving what has been written, it is Manning’s policy to have the books we publish printed on acid-free paper, and we exert our best efforts to that end. Recognizing also our responsibility to conserve the resources of our planet, Manning books are printed on paper that is at least 15% recycled and processed without the use of elemental chlorine.
  • Python Programming

    Python Programming

    Python Programming Wikibooks.org June 22, 2012 On the 28th of April 2012 the contents of the English as well as German Wikibooks and Wikipedia projects were licensed under Creative Commons Attribution-ShareAlike 3.0 Unported license. An URI to this license is given in the list of figures on page 149. If this document is a derived work from the contents of one of these projects and the content was still licensed by the project under this license at the time of derivation this document has to be licensed under the same, a similar or a compatible license, as stated in section 4b of the license. The list of contributors is included in chapter Contributors on page 143. The licenses GPL, LGPL and GFDL are included in chapter Licenses on page 153, since this book and/or parts of it may or may not be licensed under one or more of these licenses, and thus require inclusion of these licenses. The licenses of the figures are given in the list of figures on page 149. This PDF was generated by the LATEX typesetting software. The LATEX source code is included as an attachment (source.7z.txt) in this PDF file. To extract the source from the PDF file, we recommend the use of http://www.pdflabs.com/tools/pdftk-the-pdf-toolkit/ utility or clicking the paper clip attachment symbol on the lower left of your PDF Viewer, selecting Save Attachment. After extracting it from the PDF file you have to rename it to source.7z. To uncompress the resulting archive we recommend the use of http://www.7-zip.org/.
  • IT Acronyms.Docx

    IT Acronyms.Docx

    List of computing and IT abbreviations /.—Slashdot 1GL—First-Generation Programming Language 1NF—First Normal Form 10B2—10BASE-2 10B5—10BASE-5 10B-F—10BASE-F 10B-FB—10BASE-FB 10B-FL—10BASE-FL 10B-FP—10BASE-FP 10B-T—10BASE-T 100B-FX—100BASE-FX 100B-T—100BASE-T 100B-TX—100BASE-TX 100BVG—100BASE-VG 286—Intel 80286 processor 2B1Q—2 Binary 1 Quaternary 2GL—Second-Generation Programming Language 2NF—Second Normal Form 3GL—Third-Generation Programming Language 3NF—Third Normal Form 386—Intel 80386 processor 1 486—Intel 80486 processor 4B5BLF—4 Byte 5 Byte Local Fiber 4GL—Fourth-Generation Programming Language 4NF—Fourth Normal Form 5GL—Fifth-Generation Programming Language 5NF—Fifth Normal Form 6NF—Sixth Normal Form 8B10BLF—8 Byte 10 Byte Local Fiber A AAT—Average Access Time AA—Anti-Aliasing AAA—Authentication Authorization, Accounting AABB—Axis Aligned Bounding Box AAC—Advanced Audio Coding AAL—ATM Adaptation Layer AALC—ATM Adaptation Layer Connection AARP—AppleTalk Address Resolution Protocol ABCL—Actor-Based Concurrent Language ABI—Application Binary Interface ABM—Asynchronous Balanced Mode ABR—Area Border Router ABR—Auto Baud-Rate detection ABR—Available Bitrate 2 ABR—Average Bitrate AC—Acoustic Coupler AC—Alternating Current ACD—Automatic Call Distributor ACE—Advanced Computing Environment ACF NCP—Advanced Communications Function—Network Control Program ACID—Atomicity Consistency Isolation Durability ACK—ACKnowledgement ACK—Amsterdam Compiler Kit ACL—Access Control List ACL—Active Current
  • The Turbogears Toolbox and Other Tools

    The Turbogears Toolbox and Other Tools

    19 The TurboGears Toolbox and Other Tools In This Chapter ■ 19.1 Toolbox Overview 372 ■ 19.2 ModelDesigner 373 ■ 19.3 CatWalk 375 ■ 19.4 WebConsole 377 ■ 19.5 Widget Browser 378 ■ 19.6 Admi18n and System Info 379 ■ 19.7 The tg-admin Command 380 ■ 19.8 Other TurboGears Tools 380 ■ 19.9 Summary 381 371 226Ramm_ch19i_indd.indd6Ramm_ch19i_indd.indd 337171 110/17/060/17/06 111:50:421:50:42 AAMM urboGears includes a number of nice features to make your life as a de- Tveloper just a little bit easier. The TurboGears Toolbox provides tools for creating and charting your database model, adding data to your database with a web based GUI while you are still in development, debugging system problems, browsing all of the installed widgets, and internationalizing your application. 19.1 Toolbox Overview The TurboGears Toolbox is started with the tg-admin toolbox command. Your browser should automatically pop up when you start the Toolbox, but if it doesn’t you should still be able to browse to http://localhost:7654, where you’ll see a web page with links for each of the tools in the toolbox (as seen in Figure 19.1). FIGURE 19.1 The TurboGears Toolbox home page Each of the components in the Toolbox is also a TurboGears application, so you can also look at them as examples of how TurboGears applications are built. 372 226Ramm_ch19i_indd.indd6Ramm_ch19i_indd.indd 337272 110/17/060/17/06 111:50:431:50:43 AAMM 19.2 ModelDesigner 373 Because there isn’t anything in TurboGears that can’t be done in code or from the command line, the use of the Toolbox is entirely optional.
  • Industrialization of a Multi-Server Software Solution DEGREE FINAL WORK

    Industrialization of a Multi-Server Software Solution DEGREE FINAL WORK

    Escola Tècnica Superior d’Enginyeria Informàtica Universitat Politècnica de València Industrialization of a multi-server software solution DEGREE FINAL WORK Degree in Computer Engineering Author: Víctor Martínez Bevià Tutor: Andrés Terrasa Barrena Jaume Jordán Prunera Course 2016-2017 Acknowledgements To my tutors, Andrés and Jaume, for their care, attention and continued help through the execution of this Degree Final Work. To Encarna Maria, whose support knows no end. iii iv Resum L’objectiu del Treball de Fi de Grau és reescriure el procés de desplegament per a una solució de programari multiservidor per ser conforme amb el programari d’orquestració i automatització i redissenyar un flux de treball seguint pràctiques d’integració contínua i proves automàtiques. El projecte també inclou la implementació dels instal·ladors de ca- da component per a les arquitectures Windows i Linux emprant la infraestructura pròpia de l’empresa. Paraules clau: Industrialització, integració contínua, instal·ladors, testing, vmware orc- hestrator, jenkins, robot, gitlab Resumen El objetivo del Trabajo de Fin de Grado es reescribir el proceso de despliegue para una solución software multiservidor para estar en conformidad con el software de orquesta- ción y automatización y rediseñar un flujo de trabajo siguiendo prácticas de integración continua y pruebas automáticas. El proyecto también incluye la implementación de los instaladores de cada componente para las arquitecturas Windows y Linux usando la in- fraestructura propia de la empresa. Palabras clave: Industrialización, integración continua, instaladores, testing, vmware or- chestrator, jenkins, robot, gitlab Abstract The goal of the Final Degree Work is to rewrite the deployment process for a multi- server software solution in order to be compliant with the company’s orchestration and automation software while redesigning a development workflow following continuous integration and continuous automated testing principles.
  • Copyrighted Material

    Copyrighted Material

    Index abld build 36 AVRecorder 270 with C 40 abld freeze 226 IDE 32 abort() 74, 400, 402 MFC 214 abstract base class 46 Base Class Library (BCL) Mutex 388–391 active objects 31, 94–99, 237 C classes 53, 79, 85, 87 381 battery 10, 14, 43 C Wrappers 339–340 Active Template Library Bazaar 392–393 CActive 95, 97 (ATL) 134 BCL. See Base Class Library CActiveScheduler Adapter pattern 384 Binary Runtime Environment Add() 95–96 Alerts API 166 for Wireless Start() 141 AllFiles 130, 349, 355 (BREW) 253–254 CAknAppUi 155 Alloc() 64 Blackberry 11, 17–18 calendar 186, 251 ALLOC panic 45–46, 399 bld.inf 35, 36, 38, callbacks 147, 324, 381 AllocL() 64 115–116, 186, camera 165, 185, 253 All-Tcb 117 211, 292, 293, 316 Cancel() 98 Android 11, 12, 17–18, bldmake 36, 211 capabilities 228, 348–355 244–253, Bluetooth 127, 138 Android 369–371 369–371 Boost 107, 197 trusted applications ANSI C++ standardCOPYRIGHTED 386 BREW. See Binary MATERIAL Runtime 362–363 APIs 68–71, 103–131 Environment for untrusted applications applications, portable Wireless 363–364 375–396 CAPABILITY 37, 355 ARM RealView Compilation capitalization guidelines Tools (RVCT) 34, C 21, 28, 40, 103–131, 50–51 112 214 Carbide.c++ 32, 38, 72, ATL See Active Template C++ 21, 28, 31, 50, 59, 147, 211, 214, Library 61–66, 103–131, 368–369 auto_ptr 85, 143, 144 CArray 58 391–392 abstract base class 46 CArrayFixFlat 58 412 INDEX CArrayFixSeg 58 Common Language Runtime DLL. See dynamic link CArrayVarSeg 58 (CLR) 236 library CArrayXSeg 58 compilers 34, 39–40, Document Object Model catch 72 318–322 (DOM) 184 CBase 53, 54, 82, Component Object Model DOM.
  • Multimedia Systems

    Multimedia Systems

    MVC Design Pattern Introduction to MVC and compare it with others Gholamhossein Tavasoli @ ZNU Separation of Concerns o All these methods do only one thing “Separation of Concerns” or “Layered Architecture” but in their own way. o All these concepts are pretty old, like idea of MVC was tossed in 1970s. o All these patterns forces a separation of concerns, it means domain model and controller logic are decoupled from user interface (view). As a result maintenance and testing of the application become simpler and easier. MVC Pattern Architecture o MVC stands for Model-View-Controller Explanation of Modules: Model o The Model represents a set of classes that describe the business logic i.e. business model as well as data access operations i.e. data model. o It also defines business rules for data means how the data can be created, sotored, changed and manipulated. Explanation of Modules: View o The View represents the UI components like CSS, jQuery, HTML etc. o It is only responsible for displaying the data that is received from the controller as the result. o This also transforms the model(s) into UI. o Views can be nested Explanation of Modules: Controller o The Controller is responsible to process incoming requests. o It receives input from users via the View, then process the user's data with the help of Model and passing the results back to the View. o Typically, it acts as the coordinator between the View and the Model. o There is One-to-Many relationship between Controller and View, means one controller can handle many views.
  • Foreign Library Interface by Daniel Adler Dia Applications That Can Run on a Multitude of Plat- Forms

    Foreign Library Interface by Daniel Adler Dia Applications That Can Run on a Multitude of Plat- Forms

    30 CONTRIBUTED RESEARCH ARTICLES Foreign Library Interface by Daniel Adler dia applications that can run on a multitude of plat- forms. Abstract We present an improved Foreign Function Interface (FFI) for R to call arbitary na- tive functions without the need for C wrapper Foreign function interfaces code. Further we discuss a dynamic linkage framework for binding standard C libraries to FFIs provide the backbone of a language to inter- R across platforms using a universal type infor- face with foreign code. Depending on the design of mation format. The package rdyncall comprises this service, it can largely unburden developers from the framework and an initial repository of cross- writing additional wrapper code. In this section, we platform bindings for standard libraries such as compare the built-in R FFI with that provided by (legacy and modern) OpenGL, the family of SDL rdyncall. We use a simple example that sketches the libraries and Expat. The package enables system- different work flow paths for making an R binding to level programming using the R language; sam- a function from a foreign C library. ple applications are given in the article. We out- line the underlying automation tool-chain that extracts cross-platform bindings from C headers, FFI of base R making the repository extendable and open for Suppose that we wish to invoke the C function sqrt library developers. of the Standard C Math library. The function is de- clared as follows in C: Introduction double sqrt(double x); We present an improved Foreign Function Interface The .C function from the base R FFI offers a call (FFI) for R that significantly reduces the amount of gate to C code with very strict conversion rules, and C wrapper code needed to interface with C.
  • HOWTO Use Python in the Web Release 2.7.9

    HOWTO Use Python in the Web Release 2.7.9

    HOWTO Use Python in the web Release 2.7.9 Guido van Rossum and the Python development team December 10, 2014 Python Software Foundation Email: [email protected] Contents 1 The Low-Level View 2 1.1 Common Gateway Interface.....................................2 Simple script for testing CGI.....................................2 Setting up CGI on your own server..................................3 Common problems with CGI scripts.................................3 1.2 mod_python..............................................4 1.3 FastCGI and SCGI..........................................4 Setting up FastCGI..........................................5 1.4 mod_wsgi...............................................5 2 Step back: WSGI 5 2.1 WSGI Servers.............................................6 2.2 Case study: MoinMoin........................................6 3 Model-View-Controller 6 4 Ingredients for Websites 7 4.1 Templates...............................................7 4.2 Data persistence............................................8 5 Frameworks 8 5.1 Some notable frameworks......................................9 Django.................................................9 TurboGears..............................................9 Zope.................................................. 10 Other notable frameworks...................................... 10 Index 11 Author Marek Kubica Abstract This document shows how Python fits into the web. It presents some ways to integrate Python with a web server, and general practices useful for developing web
  • The Linux Gamers' HOWTO

    The Linux Gamers' HOWTO

    The Linux Gamers’ HOWTO Peter Jay Salzman Frédéric Delanoy Copyright © 2001, 2002 Peter Jay Salzman Copyright © 2003, 2004 Peter Jay SalzmanFrédéric Delanoy 2004-11-13 v.1.0.6 Abstract The same questions get asked repeatedly on Linux related mailing lists and news groups. Many of them arise because people don’t know as much as they should about how things "work" on Linux, at least, as far as games go. Gaming can be a tough pursuit; it requires knowledge from an incredibly vast range of topics from compilers to libraries to system administration to networking to XFree86 administration ... you get the picture. Every aspect of your computer plays a role in gaming. It’s a demanding topic, but this fact is shadowed by the primary goal of gaming: to have fun and blow off some steam. This document is a stepping stone to get the most common problems resolved and to give people the knowledge to begin thinking intelligently about what is going on with their games. Just as with anything else on Linux, you need to know a little more about what’s going on behind the scenes with your system to be able to keep your games healthy or to diagnose and fix them when they’re not. 1. Administra If you have ideas, corrections or questions relating to this HOWTO, please email me. By receiving feedback on this howto (even if I don’t have the time to answer), you make me feel like I’m doing something useful. In turn, it motivates me to write more and add to this document.
  • Xildoom Final Report

    Xildoom Final Report

    XilDoom Final Report 18545 Fall 2010 Robert Waaser Shupeng Sun Soo Hwan Kim Summary For our project, we ported the classic 1993 first-person shooter Doom to a Xilinx LX110T Field Programmable Gate Array (FPGA). We chose to use a source port known as Chocolate Doom which uses the Simple DirectMedia Layer (SDL) library to achieve cross-plaorm compability. AXer building a custom computer system on the FPGA that was capable of running the game, we wrote custom drivers for SDL that allowed Chocolate Doom to run on our hardware. The final result was a SystemAce file that could be used to configure an FPGA to run Doom on boot, complete with keyboard input and audio and video output. Networking was also implemented, but not tested before the public demo. Our Project Idea For our capstone we were required to implement a game, a game console, or one of a number of research projects. For the game route, the game had to be complete with audio and video output, some sort of user input, mulWple players, and a way to keep score. Furthermore the game could not be of our own creaon, as the course was not meant to be a course in game programming but rather a course in systems-level design. We took a look at capstone projects from the past three years and noWced that projects that ported soXware games such as Quake and Descent seemed to have a relavely high rate of success. Typically these projects focused less on designing hardware and code from scratch and more on combining and modifying exisWng code and libraries to funcWon in an embedded environment.