La Muerte De Mozilla Firefox

Total Page:16

File Type:pdf, Size:1020Kb

La Muerte De Mozilla Firefox Image not found or type unknown www.juventudrebelde.cu Image not found or type unknown Firefox Autor: Internet Publicado: 21/09/2017 | 06:59 pm La muerte de Mozilla Firefox El navegador que un día plantara cara a Internet Explorer agoniza ante un nuevo todopoderoso señor de la web: Google Chrome Publicado: Miércoles 28 junio 2017 | 09:48:23 pm. Publicado por: Yurisander Guevara A Mozilla Firefox lo «conocí» a inicios de 2003, cuando en mi condición de estudiante ya colaboraba en este diario. Desde los primeros momentos en que usé ese navegador web sentí que estaba ante un producto diferente, mejor que el habitual Internet Explorer, pues requería de menos recursos y permitía al ordenador trabajar con más fluidez. Tales prestaciones permitieron a Mozilla un rápido crecimiento y su consolidación como el navegador preferido de muchos. Pero en los 14 años transcurridos desde entonces, la realidad es bien diferente: Firefox ha visto disminuida su base de usuarios de forma drástica, una herida grave para sus aspiraciones, como si estuviera al borde de la muerte. Y, paradójicamente, todavía goza de buena salud en Cuba. Una fuerte alternativa libre Mozilla Firefox es el resultado de la sempiterna «guerra de navegadores», iniciada en la década de los 90 con la adopción de la web como una tecnología estándar. Por esa época Netscape Navigator dominaba el mercado y había puesto en jaque a Internet Explorer (IE), de Microsoft. Esta última compañía, para quitarse de encima a la «molesta» competencia, decidió incluir a IE de serie en el sistema operativo Windows. Como respuesta a esa estrategia Netscape lanzó el código fuente de su navegador y lo hizo libre. Buscaba atraer un mejor desarrollo para sus productos. Así las cosas, en 1999 la compañía AOL compró Netscape y, con ello, el producto se volvió más comercial. Al liberarse el código de Netscape, surgió un proyecto más amplio: crear la Mozilla Application Suite, un software de desarrollo multiplataforma sobre el que se podrían construir otras aplicaciones. Dicho producto incluía, además del navegador, un cliente de chat y otro de correo electrónico, un editor de páginas web y un módulo de calendario. Pero los desarrolladores estadounidenses Dave Hyatt, Joe Hewitt y Blake Ross, trabajadores del proyecto, consideraron que Mozilla Application Suite era un software «inflado». Por eso se unieron para crear un navegador potente y ligero. El 23 de septiembre de 2002 los ingenieros lograron su cometido y se presentó el Mozilla Firefox 1.0, que primero tuvo como nombre Phoenix y luego se llamó Firebird. En ambos casos las designaciones tuvieron que ser desechadas, pues pertenecían a otras compañías tecnológicas. Lo cierto fue que, desde antes de su lanzamiento, el proyecto Mozilla Firefox había llamado la atención de los medios de comunicación estadounidenses, tanto que la versión 1.0 tuvo 25 millones de descargas en los primeros cien días. En 2006 la cifra rebasaría los 200 millones. Netscape, entretanto, desapareció un tiempo después (2008), y Firefox se instaló como una fuerte alternativa a Internet Explorer. Si bien nunca superó a IE —sustituido por Edge en Windows 10—, con los años Firefox ganó cada vez más seguidores y todo apuntaba a que algún día lo sobrepasaría. En 2009, por ejemplo, Mozilla había logrado escalar hasta el 30 por ciento de la cuota de mercado global (IE acumulaba entonces 60 por ciento), según datos de la consultora Stat Counter. Más allá de cifras, uno de los mayores logros de Firefox había sido instaurar la cultura del código abierto y libre para los navegadores web, algo que no tenía precedente en un entorno a base de Windows, por ejemplo. También Firefox aglutinó a una comunidad de entusiastas colaboradores, los cuales aportaron (y aportan) ingeniosas soluciones al navegador, a partir de las conocidas extensiones, los temas y otras funcionalidades muy populares. En Cuba ello tiene expresión en comunidades como la muy activa Firefoxmanía, de la Universidad de las Ciencias Informáticas. Pero retornemos a 2009. Mientras Firefox se apuntaba como el navegador destinado por la providencia para desbancar a IE, por ese entonces comenzaron a desarrollarse de forma acelerada unos «monstruos silenciosos» que serían su condena: los móviles inteligentes. Un Chrome para dominarlos a todos Google se introdujo en el negocio de los navegadores web en 2008, el mismo año en que se presentó el sistema operativo Android. El proyecto Chromium, de software libre, da vida a este navegador, que se distribuye gratis bajo condiciones específicas de software privativo. Ello significa que los aportes hechos por el proyecto libre Chromium sustentan el código fuente del navegador base sobre el que está construido Chrome y, por tanto, tendrá sus mismas características, a las cuales Google adiciona otras que no se consideran software libre. Al igual que Firefox, Chrome está disponible para Windows, OS X, Linux, Android e iOS. Comenzó de forma discreta a ganar mercado, hasta que el rápido desenvolvimiento de los teléfonos celulares inteligentes y las tabletas le permitió instalarse como navegador base de la mayoría de esos terminales. Firefox, una vez más, tuvo que enfrentar lo que podríamos llamar una competencia desleal. Si primero Windows hizo presencia directa con Internet Explorer en cada ordenador, luego Google instaló Chrome de forma predeterminada en cada equipo con Android. Como informamos hace apenas una semana, en el mundo existen más de 7 300 millones de celulares y, de estos, 3 285 millones son smartphones. De entre los móviles inteligentes, cerca del 80 por ciento opera a base de Android, lo que se traduce en la presencia de Chrome. La cifra no toma en cuenta las tabletas. Acaso por eso entre 2008 y 2012 Chrome ganó cada vez más usuarios globales, a despecho de Internet Explorer y Firefox. Ya en 2012, indican cifras de Stat Counter, Chrome se posicionaba como el navegador más usado del mundo, con el 30 por ciento del mercado. Ese fue el año que marcó la caída en picado de Internet Explorer, ignorado por el público ante su pésima factura. Firefox, entretanto, se mantuvo como la otra opción fuerte, con el 21 por ciento de uso mundial. Pero Chrome ganó en calidad y multiplicó su presencia para, desde 2012, incrementar su base de usuarios de forma sostenida y brutal, hasta situarla el pasado mayo en el 53,06 por ciento de los usuarios globales. En ese período, y de forma silenciosa, las excelentes ventas experimentadas por los dispositivos de Apple impulsaron a que Safari, su navegador insignia, creciera hasta ser hoy el segundo más usado, con el 14,45 por ciento. Firefox, por su parte, solo registra el 6,47 por ciento de uso en el mundo conectado a la web. Esas cifras son diferentes en Cuba. Las mismas buenas características que se apoderaron de mis gustos por Firefox en 2003 parece que calaron hondo entre nosotros. Tal es así que Stat Counter indica que hoy Firefox es usado por el 67,66 por ciento de los usuarios cubanos de internet. Ello representa, no obstante, el nueve por ciento menos con respecto a 2016, porcentaje que se agenció —sí, ya sé que adivinó—, Google Chrome. ¿Un zorro de fuego con futuro? Andreas Gal, quien fuera un alto ejecutivo de la Fundación Mozilla, publicó en su blog el pasado 25 de mayo un post titulado Chrome ganó, en el que proyectó la desaparición de Firefox en un período de dos a tres años. De seguir así, la Fundación muestra números rojos y carga con el fracaso rotundo de su aplicación para teléfonos móviles (que se anunció sería retirada de las tiendas de aplicaciones para enfocarse en equipos de escritorio), pero en escritorio tampoco ha funcionado en los últimos años, afirma Gal. «Firefox no va a ningún lado», atiza el exdirectivo, y agrega, demoledor: «La visión fundacional de Mozilla era construir internet con la creación de un navegador. La tecnología móvil rompió con esa idea, pues en estos equipos los navegadores son menos importantes y forman parte de aplicaciones mayores, como Facebook o Twitter». La reflexión de Gal está motivada por el fracaso del proyecto Firefox OS, un sistema operativo destinado a móviles y equipos de escritorio en el que Mozilla puso todo su empeño entre los años 2011 y 2014. Por entonces su cuota de mercado cayó cerca del 14 por ciento, lo que motivó a la organización a poner de nuevo el foco sobre el navegador de escritorio. Empero, el tiempo transcurrido le hizo perder calidad y, con ello, usuarios. A casi 15 años del lanzamiento del navegador que hizo cotidiana la navegación por pestañas, los números, como ya vimos, languidecen. ¿Podrá Mozilla recuperarse de este escenario desfavorable con el lento crecimiento que hoy experimentan las ventas de ordenadores, o estamos asistiendo a su muerte? Por el momento, al menos en Cuba, su funeral parece lejano. http://www.juventudrebelde.cu/suplementos/informatica/2017-06-28/la-muerte-de-mozilla-firefox Juventud Rebelde | Diario de la juventud cubana Copyright © 2017 Juventud Rebelde.
Recommended publications
  • D 4.3 Additional Applications
    Grant Agreement No. ICT-2009-270082 Project Acronym PATHS Project full title Personalised Access To Cultural Heritage Spaces D 4.3 Additional Applications Authors: George Chrysochoidis, i-sieve Contributors: Paul D. Clough and Mark Stevenson, USFD Eneko Agirre and Arantxa Otegi, UPV/EHU Kate Fernie, MDR Project funded under FP7-ICT-2009-6 Challenge 4 – “Digital Libraries and Content” Status Final Distribution level Public Date of delivery 24/01/2014 Type Report Project website http://www.paths-project.eu Project Coordinator Dr. Mark Stevenson University of Sheffield PATHS Collaborative Project EU-ICT-270082 Change Log Version Date Amended by Changes 0.1 12/12/2014 Paul Clough (USFD) Outline + recommender system 0.2 13/12/2014 Eneko Agirre, Arantxa Otegi Additional recommender system (UPV/EHU) 0.3 23/12/2014 George Chrysochoidis, i-sieve Mobile application 0.4 16/01/2014 George Chrysochoidis, i-sieve Additional text 0.5 20/01/2014 Kate Fernie, MDR Edited text 1.0 24/01/2013 Mark Stevenson, USFD, Kate Final Fernie, MDR D4.3 Additional Applications Page 2 PATHS Collaborative Project EU-ICT-270082 Contents 1. Executive Summary .............................................................................................. 4 2. Introduction ........................................................................................................... 5 2.1. Culture on the go ............................................................................................ 5 2.2. Native and Web Mobile Applications – A Brief History ..................................
    [Show full text]
  • M&A @ Facebook: Strategy, Themes and Drivers
    A Work Project, presented as part of the requirements for the Award of a Master Degree in Finance from NOVA – School of Business and Economics M&A @ FACEBOOK: STRATEGY, THEMES AND DRIVERS TOMÁS BRANCO GONÇALVES STUDENT NUMBER 3200 A Project carried out on the Masters in Finance Program, under the supervision of: Professor Pedro Carvalho January 2018 Abstract Most deals are motivated by the recognition of a strategic threat or opportunity in the firm’s competitive arena. These deals seek to improve the firm’s competitive position or even obtain resources and new capabilities that are vital to future prosperity, and improve the firm’s agility. The purpose of this work project is to make an analysis on Facebook’s acquisitions’ strategy going through the key acquisitions in the company’s history. More than understanding the economics of its most relevant acquisitions, the main research is aimed at understanding the strategic view and key drivers behind them, and trying to set a pattern through hypotheses testing, always bearing in mind the following question: Why does Facebook acquire emerging companies instead of replicating their key success factors? Keywords Facebook; Acquisitions; Strategy; M&A Drivers “The biggest risk is not taking any risk... In a world that is changing really quickly, the only strategy that is guaranteed to fail is not taking risks.” Mark Zuckerberg, founder and CEO of Facebook 2 Literature Review M&A activity has had peaks throughout the course of history and different key industry-related drivers triggered that same activity (Sudarsanam, 2003). Historically, the appearance of the first mergers and acquisitions coincides with the existence of the first companies and, since then, in the US market, there have been five major waves of M&A activity (as summarized by T.J.A.
    [Show full text]
  • Accelerometers & Location
    Please post comments or corrections to the Author Online forum at http://www.manning-sandbox.com/forum.jspa?forumID=453 MEAP Edition Manning Early Access Program Copyright 2008 Manning Publications For more information on this and other Manning titles go to www.manning.com Please post comments or corrections to the Author Online forum at http://www.manning-sandbox.com/forum.jspa?forumID=453 Licensed to Rodney Pearson <[email protected]> Contents Preface Part 1 An Introduction to iPhone programming Chapter 1 Introducing the iPhone Chapter 2 Web development or the SDK? Part 2 Designing web pages for the iPhone Chapter 3 Redeveloping web pages for the iPhone Chapter 4 Using advanced Webkit for web apps Chapter 5 Using iUI for web apps Chapter 6 Using Canvas for web apps Chapter 7 Building web pages with Dashcode Chapter 8 Debugging iPhone web pages Chapter 9 SDK programming for web developers Part 3 Learning SDK Fundamentals Chapter 10 Learning Objective-C and the iPhone OS Chapter 11 Using Xcode Chapter 12 Using Interface Builder Chapter 13 Creating basic View Controllers Chapter 14 Monitoring events and actions Chapter 15 Creating advanced View Controllers Part 4 Programming with the SDK Toolkit Chapter 16 Data: Actions, Preferences, Files, SQLite, and Addresses Chapter 17 Positioning: Accelerometers and Location Chapter 18 Media: Images and sounds Chapter 19 Graphics: Quartz, Core Animation, and OpenGL Chapter 20 The Web: Web views and Internet protocols Appendices Appendix A iPhone OS class reference Appendix B External sources and references Appendix C Publishing your SDK program Please post comments or corrections to the Author Online forum at http://www.manning-sandbox.com/forum.jspa?forumID=453 Licensed to Rodney Pearson <[email protected]> 1 Introducing the iPhone This chapter covers: Understanding Apple’s iPhone technology Examining the iPhone’s specifications Highlighting what makes the iPhone unique In the 1980s Apple Computer was the leading innovator in the computer business.
    [Show full text]
  • A SYSTEMS ANALYSIS and DESIGN READER By
    A SYSTEMS ANALYSIS AND DESIGN READER by RUTH ANN SERRANO BASNILLO This work is licensed under a Creative Commons Attribution-Noncommercial- Share Alike 3.0 Philippines License. TABLE OF CONTENTS Dedication......................................................................................................... 5 Preface………………………………………………………………………………...6 Book Reviews Book Review 1 • Information Systems………………………………………………….9 Book Review 2 • Roles of Systems Analysts…………………………………………..10 Book Review 3 • Systems Development Life Cycle…………………………………..12 Book Review 4 • Roles of Systems Analysts…………………………………………..17 Book Review 5 • Organization as Systems……………………....…………………….19 Book Review 6 • Organizational Cultures…………..…………………………………..21 Book Review 7 • Using Data Flow Diagrams…………….…………………………….23 Book Review 8 • Prototyping………….………………………………………………….25 Book Review 9 • Kinds of Prototyping………………………………………….............27 Book Review 10 • Developing a Prototype……………………………………………….29 Book Review 11 • Advantages and Disadvantages of Prototyping…..………………..31 Book Review 12 • User’s Role in Prototyping...………………………………………….33 Book Review 13 • Rapid Application Development….…………………………………..34 Book Review 14 • Comparing RAD to the SDLC..……………………………………….36 Case Studies Case Study 1 • Paypal (Max Levchin)…………………………………...…………….39 Case Study 2 • Hotmail (Sabeer Bhatia)………………………………………………41 Case Study 3 • Apple Computer (Steve Wozniak)……………………………………43 Case Study 4 • Excite (Joe Kraus)…….……………………………………………….45 Case Study 5 • Software Arts (Dan Bricklin).………………………………………….47
    [Show full text]
  • Open Source Used in Cisco Tidal Enterprise Scheduler 6.2
    Open Source Used In Cisco Tidal Enterprise Scheduler 6.2 Cisco Systems, Inc. www.cisco.com Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices. Text Part Number: 78EE117C99-37892935 OL-32211-01 Open Source Used In Cisco Tidal Enterprise Scheduler 6.2 1 This document contains licenses and notices for open source software used in this product. With respect to the free/open source software listed in this document, if you have any questions or wish to receive a copy of any source code to which you may be entitled under the applicable free/open source license(s) (such as the GNU Lesser/General Public License), please contact us at [email protected]. In your requests please include the following reference number 78EE117C99-37892935 Contents 1.1 #ziplib? (SharpZipLib) 0.83 1.1.1 Available under license 1.2 ACE 5.3 1.2.1 Available under license 1.3 ActiveMQ 5.3.1 1.3.1 Available under license 1.4 AmazonS3 2011-01-22 1.4.1 Available under license 1.5 ant 1.7.1 1.5.1 Available under license 1.6 Apache ANT Contrib 1.0b3 1.6.1 Available under license 1.7 Apache AXIS 1.3. 1.7.1 Available under license 1.8 Apache Axis 1.1 1.8.1 Notifications 1.8.2 Available under license 1.9 Apache Batik 1.7 1.9.1 Available under license 1.10 Apache Commons Codec 1.3.
    [Show full text]
  • Oracle Endeca Commerce: Third-Party Software Usage And
    Oracle Endeca Commerce Third-Party Software Usage and Licenses January 2013 Contents About this guide.............................................................................................................7 Who should use this guide............................................................................................................................7 Conventions used in this guide.....................................................................................................................7 Contacting Oracle Support...........................................................................................................................7 Chapter 1: Third-Party Software Usage and Licenses............................9 Commercial Packages and Terms................................................................................................................9 Open Source Packages and Terms............................................................................................................11 Libraries......................................................................................................................................................26 Other Third-party Dependencies.................................................................................................................29 Public domain works ..................................................................................................................................29 Chapter 2: Other Third-Party Licenses...................................................31
    [Show full text]
  • High Performance Web Sites
    High Performance Web Sites Table of Contents Praise for High Performance Web Sites Foreword Preface How This Book Is Organized Conventions Used in This Book Code Examples Comments and Questions Safari® Books Online Acknowledgments 1. The Importance of Frontend Performance Tracking Web Page Performance Where Does the Time Go? The Performance Golden Rule 2. HTTP Overview Compression Conditional GET Requests Expires Keep-Alive There's More 3. Rule 1: Make Fewer HTTP Requests Image Maps CSS Sprites Inline Images Combined Scripts and Stylesheets Conclusion 4. Rule 2: Use a Content Delivery Network Content Delivery Networks The Savings 5. Rule 3: Add an Expires Header Expires Header Max-Age and mod_expires Empty Cache vs. Primed Cache More Than Just Images Revving Filenames Examples 6. Rule 4: Gzip Components How Compression Works What to Compress The Savings Configuration Apache 1.3: mod_gzip Apache 2.x: mod_deflate Proxy Caching Edge Cases Gzip in Action 7. Rule 5: Put Stylesheets at the Top Progressive Rendering sleep.cgi Blank White Screen CSS at the Bottom CSS at the Top Flash of Unstyled Content What's a Frontend Engineer to Do? 8. Rule 6: Put Scripts at the Bottom Problems with Scripts Parallel Downloads Scripts Block Downloads Worst Case: Scripts at the Top Best Case: Scripts at the Bottom Putting It in Perspective 9. Rule 7: Avoid CSS Expressions Updating Expressions Working Around the Problem One-Time Expressions Event Handlers Conclusion 10. Rule 8: Make JavaScript and CSS External Inline vs. External In Raw Terms, Inline Is Faster Page Views Empty Cache vs. Primed Cache Component Reuse Typical Results in the Field Home Pages The Best of Both Worlds Post-Onload Download Dynamic Inlining 11.
    [Show full text]
  • The Case of Internet Explorer and Mozilla Firefox
    Volume: 2, Issue: 1 Page: 53 -57 2020 Journal of Scientific Reports Battle of Desktop Web Browsers: The Case of Internet Explorer and Mozilla Firefox Özgür Önday Abstract Day by day correspondence is encouraged by computerized advancements through Web locales and web based life, and got to by means of PCs and cell phones (Meeker, Devitt, and Wu, 2009). The PC has changed the manner in which we live, work and play" (Lunenfeld, 2011, p. 143). Specialized gadgets are driving the advancement of innovation guidelines that are ground-breaking for purchasers, yet much progressively incredible and productive for the organizations that control them. A fight proceeds for authority over the manner in which we get to data online by means of Web programs on PCs and cell phones. Internet browsers have been assuming a key job in electronic business and electronic trade. They have extraordinary usefulness that connect a huge number of web clients to the universe of wide the internet. In the event that there were no internet browsers today; there would not be web based business and all the more for the most JSR part there would not be e-business in the good judgment. Along these lines, it isn't too Accepted 03 March 2020 Published 28 March 2020 amazing that the challenge among different internet browsers has been anxious in the DOI: 10.5281/zenodo.3731964 course of the most recent ten years. Web innovation is one the very pinnacle of developments of our time and has contributed essentially in dispersing and gathering information and data.
    [Show full text]
  • Stevens Owen
    BOOKS FOR PROFESSIONALS BY PROFESSIONALS® Stevens Owen RELATED The Truth About HTML5 The Truth About HTML5 is for web designers, web developers, and front-end coders who want to get up to speed with HTML5. The book isn’t afraid to point out what everyone gets wrong about HTML5’s new markup, so you don’t make the same mistakes. It will show you what rocks in HTML5 today and what the future holds. Marking up a basic web page shouldn’t be a quasi-religious exercise where the high priests of HTML5 must be consulted for their interpretation of the holy texts (the HTML5 spec). Don’t waste hours trawling through confusing, poorly researched, and often flat-out wrong information on the Internet. Get the truth on HTML5’s markup here. You’ll also find out about HTML5’s new microdata standard that’s being used on major websites, such as eBay and IMDB, right now, and get the low-down on the Canvas object and what it can and can’t do for you. The book also covers how HTML5 affects CMSs and web apps, what HTML5 means for mobile, and what the future holds. HTML5 isn’t one big blob of technology that will be “finished” at some point in the future. It’s a grab bag of cool stuff, much of which has been around for years. Learn what’s well supported and ready to go today. Now that the initial wave of hype is over, it’s time to learn the truth about HTML5. What You’ll Learn: • How to write elegant and up-to-date HTML5 markup • How to use microdata - the future of the semantic web • What the Canvas object can and can’t do, and how to use it correctly • How to use new features such as enhanced forms and video and audio • Which HTML5 features are production ready, and what the future holds ISBN 978-1-4302-6415-6 52999 Shelve in Web Development/General User level: Beginning–Intermediate 9 781430 264156 www.apress.com For your convenience Apress has placed some of the front matter material after the index.
    [Show full text]
  • High Performance Web Sites (O'reilly
    Praise for High Performance Web Sites “If everyone would implement just 20% of Steve’s guidelines, the Web would be a dramatically better place.Between this book and Steve’s YSlow extension, there’s really no excuse for having a sluggish web site anymore.” — Joe Hewitt, Developer of Firebug debugger and Mozilla’s DOM Inspector “Steve Souders has done a fantastic job of distilling a massive, semi-arcane art down to a set of concise, actionable, pragmatic engineering steps that will change the world of web performance.” — Eric Lawrence, Developer of the Fiddler Web Debugger, Microsoft Corporation “As the stress and performance test lead for Zillow.com, I have been talking to all of the developers and operations folks to get them on board with the rules Steve outlined in this book, and they all ask how they can get a hold of this book.I think this should be a mandatory read for all new UE developers and performance engineers here.” — Nate Moch, www.zillow.com “High Performance Web Sites is an essential guide for every web developer.Steve offers straightforward, useful advice for making virtually any site noticeably faster.” — Tony Chor, Group Program Manager, Internet Explorer team, Microsoft Corporation High Performance Web Sites Other resources from O’Reilly Related titles Adding Ajax HTTP: The Definitive Guide Ajax Design Patterns HTTP Pocket Reference CSS Pocket Reference JavaScript & Dynamic HTML ™ Dynamic HTML: The Cookbook Definitive Reference JavaScript: The Definitive Head First HTML with CSS Guide & XHTML Programming PHP oreilly.com oreilly.com is more than a complete catalog of O’Reilly books.
    [Show full text]
  • Asa Dotzler. and I've
    Asa Doltzler Interview 03-29-2 Page 1 Tom Scheinfeldt: Okay, if you’d just say your name. Asa Dotzler: Asa Dotzler. And I’ve been with—or should I wait? Okay. And I’ve been with the project since 1999. I actually attempted to get involved, right, in early ’98 when the source code was released. But I wasn’t a developer. And so I failed miserably. And I spent the next six months trying to find my way into sort of the core of the project. So, that meant going through the news groups and trying to keep up with what was going on, trying to find actual binary so I could download and test. In the early days of the project, there wasn’t anything. If you weren’t a developer, and didn’t have the ability to pull a source code and compile it into a build, you didn’t get to play in the game. And so I spent about six months trying to get at that. And a few friendly developers would make some of these executables and put them up on FTP servers. And then it was the hunt to find those. And did Mike Weinhold [ph] who had one two months ago, has he put up another one yet? And is it going to annoy him if I send him an e-mail wanting to see, you know, what was going on with this development project? And there was actually a website that was born and sort of catered to that around me and four or five other people who were interested in getting at those.
    [Show full text]
  • Hewitt Page 1 Ken Albers: It's June 27
    Hewitt Page 1 Ken Albers: It's June 27, [2006], and if you could state your name. Joe Hewitt: I'm Joe Hewitt. Blake Ross: Okay. Joe, when did you first begin using computers? Joe Hewitt: When I was seven years old. My dad bought an IBM PC Jr. for our house, and that was my first computer. Ken Albers: And was that sort of where your interest started generating, or did you have any other influences as far as technology and computers? Joe Hewitt: Yeah, that was pretty much it. My dad was interested in changing careers to become a programmer, and he bought the computer to sort of teach himself to program. And so I'd watch him writing programs and typing programs out of PC Magazine that, you know, they'd give you the code on paper and you'd type it in. And that was really where my interest started, following him as he learned. Later when I got older I sort of took off on my own. Ken Albers: And did you ever have—what's your sort of educational background? Did you then pursue formal computer training at any point or—? Joe Hewitt: Yeah. I'm not a very academic guy, so I sort of halfheartedly went through school. I started out as a computer science major. Didn't really like formal computer science, so I switched to graphic design. Realized I wasn't an artist so I went back to computer science. Then I got a ton of job offers in the field, so I just dropped out of college and I've been professional ever since.
    [Show full text]