Podcasts about Document Object Model

React is an immensely popular JavaScript library that is used to build website user interfaces. A key feature of React is that it uses a virtual Document Object Model, or DOM, to selectively update the desired regions of the web page, which provides major performance advantages. Million.js is an open source project that provides an The post Making React 70% faster with Aiden Bai of Million.js appeared first on Software Engineering Daily.

React is an immensely popular JavaScript library that is used to build website user interfaces. A key feature of React is that it uses a virtual Document Object Model, or DOM, to selectively update the desired regions of the web page, which provides major performance advantages. Million.js is an open source project that provides an The post Making React 70% faster with Aiden Bai of Million.js appeared first on Software Engineering Daily.

React is an immensely popular JavaScript library that is used to build website user interfaces. A key feature of React is that it uses a virtual Document Object Model, or DOM, to selectively update the desired regions of the web page, which provides major performance advantages. Million.js is an open source project that provides an The post Making React 70% faster with Aiden Bai of Million.js appeared first on Software Engineering Daily.

First released in 2016, the Svelte Web framework has steadily gained popularity as an alternative approach to building Web applications, one that prides itself on being more intuitive (and less verbose) than the current framework du jour, Facebook's React. You can say that it reaches back to the era before the web app — when desktop and server applications were compiled — to make the web app easier to develop and more enjoyable to user. In this latest episode of The New Stack Makers podcast, we interview the creator of Svelte himself, Rich Harris. Harris started out not as a web developer, but as a journalist who created the framework to do immersive web journalism. So we were interested in that. In addition to delving into history, we also discussed the current landscape of Web frameworks, the Web's Document Object Model, the way React.js updates variables, the value of TypeScript, and the importance SvelteKit. We also chatted about why Vercel, where Harris now works maintaining Svelte, wants to make a home for Svelte. TNS Editor Joab Jackson hosted this conversation. Below are a few excerpts from our conversation, edited for brevity and clarity. So set the stage for us. What was the point that inspired you to create Svelte? To fully tell the story, we need to go way back into the mists of time, back to when I started programming. My background is in journalism. And about a decade ago, I was working in a newsroom at a financial publication in London. I was very inspired by some of the interactive journalism that was being produced at places like the New York Times, but also the BBC and the Guardian and lots of other news organizations, where they were using Flash and increasingly JavaScript, to tell these data rich interactive stories that couldn't really be done any other way. And to me, this felt like the future of journalism, it's something that was using the full power of the web platform as a storytelling medium in a way that just hadn't been done before. And I was very excited about all that, and I wanted a piece of it. So I started learning JavaScript with the help of the help of some some friends, and discovered that it's really difficult. Particularly if you're doing things that have a lot of interactivity. If you're managing lots of state that can be updated in lots of different ways, you end up writing what is often referred to as spaghetti code. And so I started building a toolkit, really, for myself. And this was a project called Reactive, short for interactive, something out of a out of a Neal Stephenson book, in fact, and it actually got a little bit of traction, not it was never huge, but you know, it was my first foray into open source, and it got used in a few different places. And I maintained that for some years, and eventually, I left that company and joined the Guardian in the U.K. And we used Reactive to build interactive pieces of journalism there, I transferred to the U.S. to continue at the guardian in New York. And we use directive quite heavily there as well. After a while, though, it became apparent that, you know, as with many frameworks of that era, it had certain flaws. A lot of these frameworks were built for an era in which desktop computing was prevalent. And we were now in firmly in this age of mobile, first, web development. And these frameworks weren't really up to the task, primarily because they were just too big, they were too big, and they were too bulky and they were too slow. And so in 2016, I started working on what was essentially a successor to that project. And we chose the name Svelte because it has all the right connotations. It's elegant, it's sophisticated. And the idea was to basically provide the same kind of development experience that people were used to, but change the was that translated into the experience end users have when they run it in the browser. It did this by adopting techniques from the compiler world. The code that you write doesn't need to be the code that actually runs in the browser. Svelte was really one of the first frameworks to lean into the compiler paradigm. And as a result, we were able to do things with much less JavaScript, and in a way that was much more performant, which is very important if you're producing these kinds of interactive stories that typically involve like a lot of data, a lot of animation Can you talk a bit about more about the compiler aspect? How does that work with a web application or web page? So, you know, browsers run JavaScript. And like nowadays, they can run WASM, too. But JavaScript is the language that you need to write stuff in if you want to have interactivity on a web page. But that doesn't mean that you need to write JavaScript, if you can design a language that allows you to describe user interfaces in a more natural way, then the compiler could turn that intention into the code that actually runs. And so you get all the benefits of declarative programming but without the drawbacks that historically have accompanied that. There is this trade off that historically existed: the developer wants to write this nice, state driven declarative code and the user doesn't want to have to wait for this bulky JavaScript framework to load over the wire. And then to do all of this extra work to translate your declarative intentions into what actually happens within the browser. And the compiler approach basically allows you to, to square that circle, it means that you get the best of both worlds you're maximizing the developer experience without compromising on developer experience. Stupid question: As a developer, if I'm writing JavaScript code, at least initially, how do I compile it? So pretty much every web app has a build step. It is possible to write web applications that do not involve a build step, you can just write JavaScript, and you can write HTML, and you can import the JavaScript into the HTML and you've got a web app. But that approach, it really doesn't scale, much as some people will try and convince you otherwise. At some point, you're going to have to have a build step so that you can use libraries that you've installed from NPM, so that you can use things like TypeScript to optimize your JavaScript. And so Svelte fits into your existing build step. And so if you have your components that are written in Svelte files, it's literally a .SVELTE extension. Then during the build step, those components will get transformed into JavaScript files. Svelte seemed to take off right around the time we heard complaints about Angular.js. Did the frustrations around Angular help the adoption of Svelte? Svelte hasn't been a replacement for Angular because Angular is a full featured framework. It wants to own the entirety of your web application, whereas Svelte is really just a component framework. So on the spectrum, you have things that are very focused on individual components like React and Vue.js and Svelte. And then at the other end of the spectrum, you have frameworks like Angular, and Ember. And historically, you had to do the work of taking your component framework and figuring out how to build the rest of the application unless you were using one of these full-featured frameworks. Nowadays, that's less true because we have things like Next.js, and remix-vue, And on the Svelte team are currently working on SvelteKit, which is the answer to that question of how do I actually build an app with this? I would attribute the growth in popularity is felt to different forces. Essentially, what happened is it trundled along with a small but dedicated user base for a few years. And then in 2019, we released version three of the framework, which really rethought the authoring experience, the syntax that you use to write components and, and the APIs that are available. Around that time, I gave a couple of conference talks around it. And that's when it really started to pick up steam. Now, of course, we're growing very rapidly. And we're consistently at the top of developer-happiness surveys. And so now, like a lot of people are aware of is, but we're still like a very tiny framework, compared to the big dogs like React and Vue. You have said that part of the Svelte mission has been to make web development fun. What are some of Svelte's attributes that make it less aggravating for the developer? The first thing is that you can write a lot less code. If you're using Svelte, then you can express the same concepts with typically about 40% less code. There's just a lot less ceremony, a lot less boilerplate. We're not constrained by JavaScript. For example, the way that you use state inside a component with React, you have to use hooks. And there's this slightly idiosyncratic way of declaring a local piece of state inside the component. With Svelte, you just declare a variable. And if you assign a new value to that variable, or if it's an object, and you mutate that object, then the compiler interprets that as a sign that it needs to update the component.  

Geoff talks a bit about his parents' annual visit and some rules his dad used to have about travelling and social media, Georgie is going to lose her silver frequent flyer status, and we touch on some advice for freelancing as a web dev. Document Object Model: https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model 

In this episode we are exploring an important part of web programming that is hidden in plain sight to most of us - it is called the DOM. This stands for the Document Object Model, and it is created to represent the html document in the web browser every time code is sent from a web server. The DOM also has a programming interface called an API, which can be manipulated with languages such as JavaScript. I will be going over these concepts, as well as showing what it all really looks like using php and js in the wpPluginCollege.com hands-on learning lab. At the end, I will give you some coaching about dealing with the complexity of learning how to code. You can see the slides I created for this episode on the wpPluginCollege.com website, along with the YouTube version. We also have a free mini-course on 7 ways you can use the WordPress plugin programming framework to create unique products and online businesses. Hope you can join us for some learning and conversation.

¿Se pueden usar diferentes versiones de una misma librería en un proyecto? (resumen: ¡No vayas por ahí!). MultiVersion Concurrent Control https://podcast.jcea.es/python/19 Participantes: Jesús Cea, email: jcea@jcea.es, twitter: @jcea, https://blog.jcea.es/, https://www.jcea.es/. Conectando desde Madrid. Víctor Ramírez, twitter: @virako, programador python y amante de vim, conectando desde Huelva. Javier, conectando desde Madrid. Miguel Sánchez, email: msanchez@uninet.edu, conectando desde Canarias. Audio editado por Pablo Gómez, twitter: @julebek. La música de la entrada y la salida es "Lightning Bugs", de Jason Shaw. Publicada en https://audionautix.com/ con licencia - Creative Commons Attribution 4.0 International License. [00:52] Prólogo: FOSDEM https://fosdem.org/. Escuchar audios previos para ver errores y comentar "erratas". [03:07] ¡Tenemos un voluntario para editar el podcast! Detalles de cómo grabamos las tertulias. Todo se graba en una sola pista :-(. RNNoise: https://people.xiph.org/~jm/demo/rnnoise/. Ideas para automatizar el proceso. [09:17] Aviso legal de que se está grabando el sonido y que se va a publicar online. El audio publicado tendrá un índice en texto, para poder hacer búsquedas y poder moverse con facilidad entre temas. [11:22] Errata de la tertulia anterior: No, pipenv https://pypi.org/project/pipenv/ no puede instalar dos versiones diferentes de la misma librería. [13:07] Tormenta de ideas https://es.wikipedia.org/wiki/Lluvia_de_ideas sobre cómo usar diferentes versiones de la misma librería en el mismo proyecto. Conclusión: ¡No vayas por ahí! Las bibliotecas solo se cargan una vez en el programa, aunque se hagan muchos import en el código. sys.modules https://docs.python.org/3/library/sys.html#sys.modules. Dependencias transitivas. Subintérpretes Python. PEP 554: https://www.python.org/dev/peps/pep-0554/. Módulos en C: PEP 489 -- Multi-phase extension module initialization https://www.python.org/dev/peps/pep-0489/. [22:17] Python 3.10a5. PEP 636 -- Structural Pattern Matching: Tutorial https://www.python.org/dev/peps/pep-0636/. ¡Más sintaxis nueva! PEP 617 -- New PEG parser for CPython https://www.python.org/dev/peps/pep-0617/. [23:57] Nuitka https://nuitka.net/. Puede generar un binario que no depende de tener nada instalado. [26:02] Volvemos a "Structural Pattern Matching" https://www.python.org/dev/peps/pep-0636/. "Switch" con esteroides. [27:32] Lo importante que fue la modernización de los tutoriales y ejemplos para ayudar a la migración de Python 2 a Python 3. PEP 414 -- Explicit Unicode Literal for Python 3.3 https://www.python.org/dev/peps/pep-0414/. Jesús Cea opina que la migración de Python 2 a Python 3 se hizo mal y ha sido muy traumática. [30:22] PEP 8 https://www.python.org/dev/peps/pep-0008/. ¿Ajustarse estrictamente a 80 columnas? Flake8: https://pypi.org/project/flake8/. [33:22] Mucho cuidado con "python-ideas" https://mail.python.org/mailman3/lists/python-ideas.python.org/. Tabulación de código. La anotación de tipos puede gustar o no, pero de momento es opcional. Tema recurrente: ¿Qué es ser pythonico? [35:12] Ventajas de anotar tipos. Origen de MYPY: http://mypy-lang.org/. Aportar información al IDE https://en.wikipedia.org/wiki/Integrated_development_environment. Valor a la hora de documentar los tipos en los API https://en.wikipedia.org/wiki/API. [39:52] Cryptography https://cryptography.io/en/latest/ y polémica al integrar módulos en Rust https://en.wikipedia.org/wiki/Rust_(programming_language) Comunidad tóxica. [41:27] Digresión sobre systemd https://en.wikipedia.org/wiki/Systemd y otras cosas de sistemas. ¿El cambio por el cambio? [45:07] El peso de la web está moviéndose otra vez al backend. ¿Qué opciones tiene Python en este area? El cliente web solo envía eventos al servidor y recibe cambios al DOM https://es.wikipedia.org/wiki/Document_Object_Model enviadas por el servidor. Abre la posibilidad olvidarnos de JavaScript: https://es.wikipedia.org/wiki/JavaScript. ItsNat: https://en.wikipedia.org/wiki/ItsNat. [51:02] splash https://pypi.org/project/splash/. Servicio de dibujado de javascript en Python. AJAX: https://es.wikipedia.org/wiki/AJAX. [56:07] Integrar Python en otros programas y demonios. LUA: https://es.wikipedia.org/wiki/Lua. [57:07] PyOxidizer https://pyoxidizer.readthedocs.io/en/stable/ y PyO3 https://pyo3.rs/. Interactuar con otros lenguajes. Python en Java, interactuando sin dolor: Jython https://www.jython.org/. [59:52] ¿Cómo empezamos en Python? Valor de Python como lenguaje fácil de entender y pseudocódigo. SpamBayes: http://spambayes.sourceforge.net/. Tutorial de Python: https://docs.python.org/es/3/tutorial/index.html. bc -l https://linux.die.net/man/1/bc. [01:05:07] Modificación atómica de ficheros. En Unix se suele hacer: write + flush + rename. rename: https://www.man7.org/linux/man-pages/man2/rename.2.html. MS Windows eso no funciona. Python 3.3 añadió os.replace() https://docs.python.org/3.8/library/os.html#os.replace. En MS Windows es atómico... casi siempre: Issue8828: Atomic function to rename a file https://bugs.python.org/issue8828. [01:10:02] Combinar fork e hilos en Python es una receta para el desastre. fork: https://www.man7.org/linux/man-pages/man2/fork.2.html. multiprocessing: https://docs.python.org/3/library/multiprocessing.html. [01:11:37] Decorador @overload https://docs.python.org/3/library/typing.html#typing.overload. @functools.singledispatch https://docs.python.org/3/library/functools.html. ¿Qué se ve cuando salta una excepción? Especializaciones. Cython https://cython.org/. [01:17:00] AnyIO https://anyio.readthedocs.io/en/stable/basics.html. Unificación de reactores asíncronos. [01:18:12] "lxml soporta xpath". Hilo en la lista de correo: "[Python-es] Biblioteca XPATH" https://mail.python.org/pipermail/python-es/2021-February/037931.html. lxml: https://lxml.de/. beautifulsoup4: https://pypi.org/project/beautifulsoup4/. XPath: https://es.wikipedia.org/wiki/XPath. Scrapy: https://scrapy.org/. El buscador de PyPI https://pypi.org/ funciona fatal a la hora de ordenar por relevancia. [01:20:02] El valor de estudiar el código fuente ajeno no solo para aprender de él sino también para descubrir qué bibliotecas útiles utilizan para añadirlas a tu cajón de herramientas. Es la documentación última. Los tests son muy útiles para saber cómo se usa el producto. [01:22:02] ¿Cómo gestionáis la paginación cuando los datos del backend cambian? ¿Cómo evitáis repetir resultados o saltaros datos? Brainstorming de diversas estrategias. Berkeley DB: https://pypi.org/project/berkeleydb/. lmdb: https://pypi.org/project/lmdb/. Multiversion concurrency control: https://es.wikipedia.org/wiki/Multiversion_concurrency_control. Copy on Write: https://es.wikipedia.org/wiki/Copy_on_write. Snapshot: https://es.wikipedia.org/wiki/Copia_instant%C3%A1nea_de_volumen. BTree: https://es.wikipedia.org/wiki/%C3%81rbol-B. PostgreSQL: https://www.postgresql.org/. ZFS: https://es.wikipedia.org/wiki/ZFS_(sistema_de_archivos). Normalización y formas normales: https://es.wikipedia.org/wiki/Forma_normal_(base_de_datos). [01:48:42] FOSDEM https://fosdem.org/: Virako recomienda las siguientes: Some SQL Tricks of an Application DBA - Non-trivial tips for database development https://fosdem.org/2021/schedule/event/postgresql_some_sql_tricks_of_an_application_dba/. Database Disasters and How to Find Them https://fosdem.org/2021/schedule/event/postgresql_database_disasters_and_how_to_find_them/. Practical advice for using Mypy - Hidden gems in the typing system! https://fosdem.org/2021/schedule/event/python_mypy/. Escaping the Cargo Cult - How to structure your project without losing your mind. https://fosdem.org/2021/schedule/event/python_escaping_cargo_cult/. [01:52:02] Charla Python Madrid https://www.python-madrid.es/. TDD - ¿panacea del desarrollo o pérdida de tiempo? https://www.python-madrid.es/meetings/reunion-febrero-2021-python-madrid/. [01:54:27] Comentado en la tertulia de la semana pasada: Bugs sobre "pickle" https://docs.python.org/3/library/pickle.html en el módulo __main__. Se trata de un problema conocido. Ejemplo de código: https://pastebin.com/vGM1sh8r. Issue24676: Error in pickle using cProfile https://bugs.python.org/issue24676. Issue9914: trace/profile conflict with the use of sys.modules[__name__] https://bugs.python.org/issue9914. Issue9325: Add an option to pdb/trace/profile to run library module as a script https://bugs.python.org/issue9325. [02:00:42] Que te cuenten lo que no funciona es mucho más interesante. Postmortem. [02:02:52] Whoosh: https://whoosh.readthedocs.io/en/latest/intro.html. ¿Cómo normalizar las palabras para español? La palabra "real" Whoosh: https://www.wordreference.com/es/translation.asp?tranword=whoosh. Dificultades para buscar el proyecto Python Whoosh https://whoosh.readthedocs.io/en/latest/intro.html en internet. [02:05:48] Final.

Follow us on Twitter: https://www.twitter.com/juanlizarazog •• https://www.twitter.com/jaredpotter What is the DOM? Why is it so essential to learn DOM Manipulation with Pure JavaScript? How does React, Vue, and Angular use the native DOM APIs along with their own Virtual DOMs? In today's Dev Bootcamp Life episode, Jared Potter and Juan Lizrazo discuss these crucial questions and explore their answers. Understanding the DOM and its native pure javascript APIs will make you a better web software engineer to level up and or help you land your tech first job! Learn the practical skills behind today's episode by taking Juan's NEW course - https://learndom.dev --- Support this podcast: https://anchor.fm/devbootcamplife/support

En este episodio expandimos continuamos con el tema del Document Object Model. Esta vez hablamos del virtual DOM y como éste no es lo mismo que el Shadow DOM. Si desean mayores detalles sobre el tema, aquí les dejamos algunos enlaces relacionados: The difference between Virtual DOM and DOM https://reactkungfu.com/2015/10/the-difference-between-virtual-dom-and-dom/ Shadow DOM != Virtual DOM https://develoger.com/shadow-dom-virtual-dom-889bf78ce701 What’s The Deal With Vue’s Virtual DOM? https://vuejsdevelopers.com/2017/02/21/vue-js-virtual-dom/ React: The Virtual DOM | Codecademy https://www.codecademy.com/articles/react-virtual-dom What is Virtual Dom - Tony Freed - Medium https://medium.com/@tony_freed/what-is-virtual-dom-c0ec6d6a925c What is the difference between DOM and Virtual DOM? https://www.devwrites.com/what-is-the-difference-between-dom-and-virtual-dom/ No olviden subscribirse a nuestro canal de YouTube y seguirnos en Instagram y Twitter: YouTube: https://www.youtube.com/channel/UCM7c4hwn-BZT67chRgpkCNg Instagram: @SeHablaCodigo Twitter: @SeHablaCodigo David Kontorovsky en Twitter: @dkvsky --- Send in a voice message: https://anchor.fm/sehablacodigo/message

Recorded at Øredev 2018, Fredrik talks to Steve Klabnik about Rust and Webassembly. We talk a lot about error messages, based on Steve’s talk on how Rust handles and displays error messages. We discuss Rust’s error messages thinking an handling, but also error messages more in general, such how to think in order to produce error messages both developers and end users have a chance of understanding. Steve explains how and why the Rust compiler is switching from a pass-based compilation approach to a query-based approach to better facilitate partial recompilation upon smaller code changes. We also talk about Rust 2018, how Rust puts out new releases and what major features are on their way. We then switch to talking about Webassembly. We discuss how Webassembly is moving along, among other things how it is getting better at playing well with others, enabling people to rely on Webassembly code without necessarily even needing to know about it. Thank you Cloudnet for sponsoring our VPS! Comments, questions or tips? We are @kodsnack, @tobiashieta, @oferlund and @bjoreman on Twitter, have a page on Facebook and can be emailed at info@kodsnack.se if you want to write longer. We read everything we receive. If you enjoy Kodsnack we would love a review in iTunes! You can also support the podcast by buying us a coffee (or two!) through Ko-fi. Links Steve Klabnik Steve was also in episode 245, talking about Rust, why the lucky stiff and a lot more Mozilla Rust Steve’s presentation about error messages in Rust Steve’s second presentation, about Webassembly Rust’s Github label for diagnostics/confusing error messages ICE - internal compiler error AST - abstract syntax tree IR - intermediate representation Linkchecker The Rust book Rust by example Async/await for Rust Webassembly Emscripten Wasmpack - bundles Webassembly code as a npm package - and puts it on npm Spectre and Meltdown The host bindings proposal The DOM Wasm-bindgen Polyfill Ethereum’s work with Webassembly SIMD - Single instruction multiple data SIMD-support in Webassembly webassembly.org The Webassembly spec C and C++ through Emscripten Blazor - C# to Webassembly Yes, there was a talk about Blazor by Steve Sanderson Spidermonkey - Mozilla’s Javascript engine Titles Something that should not be an afterthought Hard actual work What messages to give or how to give them Any error message that’s confusing is a bug Git blame always returns your own name The internal deadline is tomorrow The harder problem The real test of being usable More useful to more people Broader than just the DOM A host can do these things The design is sort of not there We need more teachers and explainers

En este segundo episodio estaremos hablando de un importante componente web. Conoceremos al "Shadow DOM". Antes de entrar en materia repasaremos lo que es el DOM o "Document Object Model", y la estructura de árbol que podemos ver en las páginas web. Tendremos nuevo episodio los días Martes. ¡Suscríbete y corre la voz! Y recuerda que estamos en: Twitter: @SeHablaCodigo y @programatiko Instagram: @programatiko YouTube: https://www.youtube.com/channel/UCM7c4hwn-BZT67chRgpkCNg --- Send in a voice message: https://anchor.fm/sehablacodigo/message

Interested in starting your coding career? I'm now accepting students into an immersive programming Bootcamp where I guarantee you a job offer upon graduation. It is a 6 month, part-time, online Bootcamp that teaches you everything you need to know to get a job as a Java developer in the real-world. You can learn more via https://www.coderscampus.com/bootcamp   Show notes for this episode are available via http://coderscampus.com/40    

Show notes for this episode are available via http://coderscampus.com/40 Don't forget to check out our current "deal" for coders campus available via http://coderscampus.com/deal

Document Object Model (DOM) Taken from w3schools.com – The W3C Document Object Model (DOM) is a platform and language-neutral interface that allows programs and scripts to dynamically access and update the content, structure, and style of a document.” The W3C DOM standard is separated into 3 different parts: Core DOM – standard model for all […] The post Eps 36: Document Object Model (DOM) appeared first on Schaffen Creative - Make. Manage. Achieve..

Document Object Model (DOM) Taken from w3schools.com – The W3C Document Object Model (DOM) is a platform and language-neutral interface that allows programs and scripts to dynamically access and update the content, structure, and style of a document.” The W3C DOM standard is separated into 3 different parts: Core DOM – standard model for all […] The post Eps 36: Document Object Model (DOM) appeared first on Schaffen Creative - Make. Manage. Achieve..

In this episode, we're going to take a deep dive into the DOM. Nicole explains what the Document Object Model is, what it looks like, and what we can do with it. And because we can't touch on everything, at the end of the episode, I'll provide some more resources for you to go forth and dominate the DOM. Show notes, key moments, and links are available on the La Vie en Code website: http://www.lavieencode.net/podcast/009-intro-to-js-dom

For 6 weeks now, three gaming novices have met up to discuss video games and farts. This week, there is a fourth member. AND HE IS A GAMING GENIUS! Non-wanky video games journalist, Nintendo Beta Tester and Windows Phone owner Matteo Muscas (https://matteomuscas.com / https://twitter.com/matteomuscas) joins us in game fart towers... game fart studios?... game fart asylum? We haven't made up a name for our gathering place just yet. But Matteo joins us there as our guest. We discuss some actual video game news, AND mostly correct trivia this week, thanks to Matteo's superior knowledge. We also take a trip down memory lane to discuss the legendary Dreamcast Moose Boot discs we never actually owned (honest mate, just saw my friends) and discuss Apples lack of Rainbow Cum at their recent events. Probably our best and most least offensive episode yet. # NEWS - The New Playstation Flying Chicken Dog Game (again) - The new Final Fantasy / U-KISS cross over game, Final Fantasy XV - Xbox Scorpio games WILL MAKE XBOX ONE LOOK LIKE CRAP OLD LAPTOP GAMES! - The recent PSX event with many trailers for confusing Japanese games - Crash bandicoot remakes # BAD - Too many remakes for millennials # GOOD - Full Throttle Remake # UGLY - Rose tinted glasses: Old games were shit! # GETS A MENTION - Postal & Bully (a.k.a. The game with the weird name in UK you can't remember) - UP - Metal Gear Solid V (again) - The Final Fantasy Movie - Various Consoles Bits (64bit / 128bit / etc) - Ultra HLE - BLEEM! - x86 / x64 Processors - JSON and the Document Object Model's badly titled XMLHttpRequest API call - Heavy Rain a.k.a. Dad Simulator - The game where the baby has to try and kill itself (http://store.steampowered.com/app/427730/) - The Sega Saturn - PS3 BBQ Heat - 4K Blu-Rays & Copyright adverts - Aaron's flash background TV Lights - Various LucasArts games (Monkey Island, Day of the Tentacle, Fate of Atlantis) - Copy protection wheels and instruction manual lookups - DOOM was Free - Meaty £5 Notes - The Legendary Dreamast Moose Boot (image attached http://imgur.com/R3Q3EL4) - Apples $300 Picture Book - Apples become wanky / No more Apple Rainbow Cum Sex - A brief history of Windows Mobile Devices Follow us at... gamefart.fasnastic.com twitter.com/fasnasticgf facebook.com/fasnasticgf reddit.com/r/FASNASTIC This podcast is brought to you by FASNASTIC LTD. in the UK and intended to be listened to on the train to work, or in bed for some falling asleep background noise.

02:54 - Everyone Gets It But Me Martin Fowler 04:06 - Tools You “Need” to Know 06:29 - Clojures 07:39 - JavaScript as “Object-Oriented” vs “Event-Oriented” Object-Oriented Programming 09:30 - Code That Can’t Be Serialized or Deserialized 10:49 - Clojures (Cont’d) 14:32 - The DOM (Document Object Model) [YouTube] Angular + React = Speed by Dave Smith @ ng-conf 2015 19:52 - Math Is Hard IEEE754 (Floating-Point Arithmetic) 22:39 - Prototypes Sebastian Porto: A Plain English Guide to JavaScript Prototypes 25:43 - Asynchronous Programming Debugging Gregor Hohpe: Your Coffee Shop Doesn’t Use Two-Phase Commit How Do You Learn It? 32:23 - Browser Environments 34:48 - Keeping Up with JavaScript 35:46 - Node Nesting Context Switching 42:48 - UTF-8 Conversion 44:56 - Jamison’s Stack React Koa     RethinkDB io.js Webpack Check out and sign up to get new on React Rally: A community React conference on August 24th and 25th in Salt Lake City, Utah! Picks Jason Orendorff: ES6 In Depth (Aimee) Cat Strollers (Aimee) Stephano Legacy of the Void (Joe) A Gentleman's Guide to Love and Murder (Joe) Gregor Hohpe: Your Coffee Shop Doesn’t Use Two-Phase Commit  (AJ) Firefox OS (AJ) Flame (AJ) OpenWest 2015 (AJ) 801 Labs Hackerspace (AJ) Stack Overflow Careers (AJ) Dota 2 (Jamison) Beats, Rye & Types Podcast (Jamison) JS Remote Conf Talks (Chuck) Workflowy (Chuck)

02:54 - Everyone Gets It But Me Martin Fowler 04:06 - Tools You “Need” to Know 06:29 - Clojures 07:39 - JavaScript as “Object-Oriented” vs “Event-Oriented” Object-Oriented Programming 09:30 - Code That Can’t Be Serialized or Deserialized 10:49 - Clojures (Cont’d) 14:32 - The DOM (Document Object Model) [YouTube] Angular + React = Speed by Dave Smith @ ng-conf 2015 19:52 - Math Is Hard IEEE754 (Floating-Point Arithmetic) 22:39 - Prototypes Sebastian Porto: A Plain English Guide to JavaScript Prototypes 25:43 - Asynchronous Programming Debugging Gregor Hohpe: Your Coffee Shop Doesn’t Use Two-Phase Commit How Do You Learn It? 32:23 - Browser Environments 34:48 - Keeping Up with JavaScript 35:46 - Node Nesting Context Switching 42:48 - UTF-8 Conversion 44:56 - Jamison’s Stack React Koa     RethinkDB io.js Webpack Check out and sign up to get new on React Rally: A community React conference on August 24th and 25th in Salt Lake City, Utah! Picks Jason Orendorff: ES6 In Depth (Aimee) Cat Strollers (Aimee) Stephano Legacy of the Void (Joe) A Gentleman's Guide to Love and Murder (Joe) Gregor Hohpe: Your Coffee Shop Doesn’t Use Two-Phase Commit  (AJ) Firefox OS (AJ) Flame (AJ) OpenWest 2015 (AJ) 801 Labs Hackerspace (AJ) Stack Overflow Careers (AJ) Dota 2 (Jamison) Beats, Rye & Types Podcast (Jamison) JS Remote Conf Talks (Chuck) Workflowy (Chuck)

02:54 - Everyone Gets It But Me Martin Fowler 04:06 - Tools You “Need” to Know 06:29 - Clojures 07:39 - JavaScript as “Object-Oriented” vs “Event-Oriented” Object-Oriented Programming 09:30 - Code That Can’t Be Serialized or Deserialized 10:49 - Clojures (Cont’d) 14:32 - The DOM (Document Object Model) [YouTube] Angular + React = Speed by Dave Smith @ ng-conf 2015 19:52 - Math Is Hard IEEE754 (Floating-Point Arithmetic) 22:39 - Prototypes Sebastian Porto: A Plain English Guide to JavaScript Prototypes 25:43 - Asynchronous Programming Debugging Gregor Hohpe: Your Coffee Shop Doesn’t Use Two-Phase Commit How Do You Learn It? 32:23 - Browser Environments 34:48 - Keeping Up with JavaScript 35:46 - Node Nesting Context Switching 42:48 - UTF-8 Conversion 44:56 - Jamison’s Stack React Koa     RethinkDB io.js Webpack Check out and sign up to get new on React Rally: A community React conference on August 24th and 25th in Salt Lake City, Utah! Picks Jason Orendorff: ES6 In Depth (Aimee) Cat Strollers (Aimee) Stephano Legacy of the Void (Joe) A Gentleman's Guide to Love and Murder (Joe) Gregor Hohpe: Your Coffee Shop Doesn’t Use Two-Phase Commit  (AJ) Firefox OS (AJ) Flame (AJ) OpenWest 2015 (AJ) 801 Labs Hackerspace (AJ) Stack Overflow Careers (AJ) Dota 2 (Jamison) Beats, Rye & Types Podcast (Jamison) JS Remote Conf Talks (Chuck) Workflowy (Chuck)

This keynote will focus on the unique potential offered to web developers - the ability to use the web platform to build compelling applications that reach across different devices, scenarios and environments. In discussing the approaches necessary to deliver great experiences across all these spaces, we will also uncover unique opportunities in a platform that reaches from mobile phones to the biggest display screen in your house. Chris Wilson is a Developer Advocate at Google Inc. He began working on web browsers in 1993 when he co-​​authored the original Windows version of NCSA Mosaic, the first mass-​​market WWW browser. After leaving NCSA in 1994 and spending a year working on the AIRMosaic web browser for SPRY, Inc., he joined Microsoft’s Internet Explorer team as a developer in 1995. Over the course of 15 years, Chris represented Microsoft in many standards working groups, in particular helping develop standards for Cascading Style Sheets, HTML, the Document Object Model and XSL through the W3C working groups. He also developed the first implementation of Cascading Style Sheets in Internet Explorer – the first, in fact, in any mass-​​market web browser. Beginning in 2001, he spent a few years working on the WPF project, but rejoined the IE team in 2004 to lead the IE Platform and Security team, then moved to work on the Javascript engine team in 2009. In 2010, Chris left Microsoft and joined Google’s Developer Relations team, and is currently working on the Google TV project. In his free time, he enjoys photography and hiking with his wife and daughter, and scuba diving in the cool waters of Puget Sound. Occasionally he remembers to share his thoughts on his blog. Follow Chris on Twitter: @cwilso Licensed as Creative Commons Attribution-Share Alike 3.0 (http://creativecommons.org/licenses/by-sa/3.0/).

Document Object Model (DOM), parsing a document and changing its contents with DOM attributes and functions

Es wird ein Überblick über die Möglichkeiten gegeben, Webseiten interaktiv abhängig von benutzereingaben und anderen externen Faktoren zu gestalten. Die Sprache JavaScript wird eingeführt und verschiedene Beispiele zur HTML-Integration werden besprochen. Als Zugriffsmöglichkeit auf Benutzereingaben werden HTML-Forms und das Document Object Model eingeführt. Abschließend wird eine knappe einführende Diskussion von serverseitigen Lösungen für dynamische Web-Seiten gegeben, mit kurzen Beispielen in der Sprache PHP.

Es wird ein Überblick über die Möglichkeiten gegeben, Webseiten interaktiv abhängig von benutzereingaben und anderen externen Faktoren zu gestalten. Die Sprache JavaScript wird eingeführt und verschiedene Beispiele zur HTML-Integration werden besprochen. Als Zugriffsmöglichkeit auf Benutzereingaben werden HTML-Forms und das Document Object Model eingeführt. Abschließend wird eine knappe einführende Diskussion von serverseitigen Lösungen für dynamische Web-Seiten gegeben, mit kurzen Beispielen in der Sprache PHP.