# data[].attributes.headline
1991, Web 1.0. Páginas estáticas, extensiones HTML

# data[].attributes.subject
1991, Web 1.0. Páginas estáticas, extensiones HTML

# data[].attributes.body
El contenido en internet es de texto, estático y difícil de actualizar, no hay dinamismo

# data[].attributes.headline
1995, Java applets. Uso de java para hacer scripts en la web.

# data[].attributes.subject
1995, Java applets. Uso de java para hacer scripts en la web.

# data[].attributes.body
Se basaba en inyectar pequeñas apps (applets) dentro de una página web, lo cual le permitia actuar como un programar con interactividad básica

# data[].attributes.headline
1996, estandarización de los tipos MIME para subir contenidos a la red

# data[].attributes.subject
1996, estandarización de los tipos MIME para subir contenidos a la red

# data[].attributes.headline
1995, Javascript. Lenguaje de scripting para brindar dinamismo e interactividad a la web.

# data[].attributes.subject
1995, Javascript. Lenguaje de scripting para brindar dinamismo e interactividad a la web.

# data[].attributes.headline
2004, Web 2.0. Basada en la aportación activa de los usuarios y la colaboración.

# data[].attributes.subject
2004, Web 2.0. Basada en la aportación activa de los usuarios y la colaboración.

# data[].attributes.body
Los usuarios pasan de ser un actor pasivo a poder colaborar con comentarios, servicios de rede sociales, blogs y wikis

# data[].attributes.headline
2004, A. Ronacher crea Flask, una popular plataforma de desarrollo de webapps en python

# data[].attributes.subject
2004, A. Ronacher crea Flask, una popular plataforma de desarrollo de webapps en python

# data[].attributes.headline
2006, Web 3.0. Crecimiento acelerado de la web. Nacimiento de tecnologías como web geoespacial, web 3d, inteligencia artificial aplicada a la web, etc.

# data[].attributes.subject
2006, Web 3.0. Crecimiento acelerado de la web. Nacimiento de tecnologías como web geoespacial, web 3d, inteligencia artificial aplicada a la web, etc.

# data[].attributes.headline
2010, introducción de los websockets, tecnología para comunicación cliente - servidor de forma bidireccional para visualización de información en tiempo real

# data[].attributes.subject
2010, introducción de los websockets, tecnología para comunicación cliente - servidor de forma bidireccional para visualización de información en tiempo real

# data[].attributes.headline
2011, Web 4.0. Aplicaciones en la nube, red intelignente. Se busca unir las tecnologías

# data[].attributes.subject
2011, Web 4.0. Aplicaciones en la nube, red intelignente. Se busca unir las tecnologías

# data[].attributes.body
-https://www.vice.com/en/article/8q8n3k/a-brief-history-of-the-java-applet
-https://medium.com/@_benaston/lesson-1a-the-history-of-javascript-8c1ce3bffb17
-https://sites.google.com/site/programacionwebhegm/unidad-1-arquitectura/1-1-evolucion-de-las-aplicaciones-web

# data[].attributes.attachment_link.readable_text
The success of Java itself would be in slow, deliberate entrenchment in the oatmeal world of enterprise software.

In 1995, this was pretty exciting stuff. The newborn Java language, the creation of Sun Microsystems, was immediately tasked with taking on the web. 1997 saw the release of the HotJava browser, the first to accommodate Java Applets. It was to be Sun's big demonstration of the technology and, with it, the potential of an interactive web.

"HotJava Browser 1.0 is a powerful tool that allows developers to quickly create their own style in the user interface, or create network applications that use URLs and HTTP to transport and locate information," a Sun press release announced. "For example, HotJava Browser can be used to develop customized information kiosks that businesses could use to provide information to their customers. The kiosks would display HTML-based pages and customers would use HotJava Browser to browse the information. The kiosks' graphical user interface would be completely tailored to reflect the branding of the business. HotJava Browser is completely customizable and lets any business create a browser-based user environment that is in its own image."

Hype ensued. With that hype came JavaScript, a language whipped up by Netscape engineer Brendan Eich in 10 days in 1995 to be featured in the forthcoming Navigator 2.0. The JavaScript name usually taken to be a quick cash-in on the Java buzz of the time. JavaScript would eventually crush the Java Applet, but you probably wouldn't know it at the time. JavaScript promised much of the same web functionality as Java, but Netscape (and Microsoft) were busily implementing their own JVMs, thus enabling Java Applets to run on non-Sun mainstream browsers.

Flashiness would wind up being JavaScript's thing. The success of Java itself would be in slow, deliberate entrenchment in the oatmeal world of enterprise software, e.g. the long-lasting collections of programs that together serve the needs of whole organizations. The Java language promised "write once, run anywhere" functionality-that is, code written for the JVM would run the same regardless of the underlying machine or operating system. Programs written for the JVM, which include several other non-Java languages that run within the same virtual environment, are said to be platform-independent.

A 1999 white-paper in the industry journal HP Professional extolled the virtues of the new Java way: "Software companies spend a fortune building separate code for Windows NT, Windows 3.1, Linux, MacOS, Solaris, AIX, etc. This is a major headache for every IT shop. Java has achieved the greatest success in letting developers write Java code once for all platforms. When applications are written in Java, the resulting bytecode will run identically on any JVM."

"Java is being widely used from developing browser applets to serious enterprise applications," the paper continued. "It is being used to reengineer global reservation systems, to speed ERP implementation and to improve call centers. What started as an improved programming language is now an architecture that is reshaping our enterprises and the World Wide Web."

The resulting effect to the ecosystem is that Java applets are still present in the platform, and are a major contributor to security problems.

So, there is server-side scripting, which is what PHP does, and there is client-side scripting, which is what JavaScript does. The prior means that a script is running on server somewhere, and is likely meant to interact with a database in some way, while the latter means the script is running on your computer via a browser. When we usually think of "cool stuff" happening on a web page, we're usually thinking of stuff happening on the client side in terms of some real-time interaction.

JavaScript is able to do its thing because modern browsers are built with JavaScript engines. These engines behave in a way similar to the JVM described above, but, rather than mimic a full-on computer architecture, the engine's job is to use the instructions provided in a script to change some HTML in interesting and useful ways.

JavaScript didn't immediately sink the Java Applet, despite web browsers now being able to do cool stuff without having to farm it out to the JVM. This is because for many years the JVM still offered performance advantages. It makes sense: the Applet has access to the full resources of a simulated computer, while, until recently, JavaScript code was left to dork around with HTML via the relatively limited capabilities of a browser. One is essentially a program, while the other fakes being a program.

Applets are a technology that are very much of their time, and they have not aged well. The technology proved to be very difficult to evolve, and so applets have not been considered to be a modern development platform for many years now. However, they doggedly persist due to some large early adopters being very resistant to change. The resulting effect to the ecosystem is that Java applets are still present in the platform, and are a major contributor to security problems.

Java's rapid rise to fame 20 years ago began with a tumbling duke applet running in the HotJava browser, long before Microsoft Internet Explorer, Mozilla Firefox or Google Chrome were released. Applets allowed richer development functionality through a browser plugin at a time when browser capabilities were very limited, and provided centralized distribution of applications without requiring users to install or update applications locally. The Netscape Navigator browser went on to popularize a standards based plug-in model with the Netscape Plugin API (NPAPI), which was in turn adopted by many other browsers, allowing plugins to extend the capabilities of browsers to provide cross-platform and cross-browser functionality.

As Java evolved to become one of the leading mainstream development platforms, so did the applet's hosts - the web browsers. The rise of web usage on mobile device browsers, typically without support for plugins, increasingly led browser makers to want to restrict and remove standards based plugin support from their products, as they tried to unify the set of features available across desktop and mobile versions.

# data[].attributes.attachment_link.title
The Rise and Fall of the Java Applet: Creative Coding's Awkward Little Square

# data[].attributes.attachment_link.description
The success of Java itself would be in slow, deliberate entrenchment in the oatmeal world of enterprise software. In 1995, this was pretty exciting stuff. The newborn Java language, the creation of Sun Microsystems, was immediately tasked with taking on the web. 1997 saw the release of the HotJava browser, the first to accommodate Java Applets.