Podcasts about v8 javascript

Node is back in the news with some noteworthy updates as v24 drops. It gets an upgrade to 13.6 for its V8 JavaScript engine, runs with npm version 11, and has more efficient implementation of the local storage API and test runner updates.Google has released its newest version of its Gemini AI model: Gemini 2.5 Pro Preview (I/O Edition), which claims to be the best model for front-end and UI development. To prove it, Google links to a site called the WebDev Arena (where Gemini 2.5 Pro Preview ranks #1), that lets users put in a prompt and then pits different AI models head to head to build a site based on the prompt. Figma just had their 2025 Config conference and unveiled a host of new offerings, including Figma Sites that lets folks design, prototype and publish with Figma, and Figma Make the AI prompting tool that can add functionality to a Figma mockup via natural language directions.News:Paige - Node 24 updatesJack - Figma Make and Figma Sites and conference demo videoTJ - Gemini 2.5 updates and WebDev ArenaBonus News:Take the first annual State of Devs surveyOpenAI agrees to buy Windsurf for $3BFire Starters:CSS reading-flow and reading-orderWhat Makes Us Happy this Week:Paige - Old Town Trolley ToursJack -  The Residence TV showTJ - ChatGPT helping with camera & video setupThanks as always to our sponsor, the Blue Collar Coder channel on YouTube. You can join us in our Discord channel, explore our website and reach us via email, or talk to us on X, Bluesky, or YouTube.Front-end Fire websiteBlue Collar Coder on YouTubeBlue Collar Coder on DiscordReach out via emailTweet at us on X @front_end_fireFollow us on Bluesky @front-end-fire.comSubscribe to our YouTube channel @Front-EndFirePodcast

In today's episode, we explore the alarming rise of NGate Android malware, which employs NFC technology to facilitate unauthorized ATM withdrawals from victims' bank accounts. We also discuss Google's urgent patch for the ninth Chrome zero-day vulnerability of 2024, addressing serious security flaws that could allow attackers to exploit devices. Plus, we cover the sentencing of Jesse Kipf, who faked his death through cyber intrusions to evade child support obligations. Video Episode: https://youtu.be/Mem_XEAQymI 00:00 - Intro 00:56 - Android NFC Malware 02:53 - Google Zero Day 04:14 - Kentucky Man Fakes Death Sources: https://www.helpnetsecurity.com/2024/08/22/android-malware-nfc-data-atm-withdrawals/ https://www.bleepingcomputer.com/news/security/google-fixes-ninth-actively-exploited-chrome-zero-day-in-2024/ https://www.justice.gov/usao-edky/pr/pulaski-county-man-sentenced-cyber-intrusion-and-aggravated-identity-theft Sign up for digestible cyber news delivered to your inbox: https://news.thedailydecrypt.com Thanks to Jered Jones for providing the music for this episode. https://www.jeredjones.com/ Logo Design by https://www.zackgraber.com/ Tags: NGate, Android, NFC, malware, cybersecurity, Google, Chrome, zero-day, cyber heist, identity theft, hacking, ESET, V8 JavaScript, payment security, mobile crime, Jesse Kipf Search phrases: What are today's top cybersecurity news stories, NGate Android malware news, how to protect from malware attacks, zero-day vulnerabilities in Chrome, identity theft prevention measures, steps to update Chrome browser, impacts of NFC technology on security, cyber heist case studies, ESET cybersecurity research, mobile payment security tips

This week we speak to Justin Cormack the CTO of Docker. We talked about WASM (or WebAssembly Modules), Docker support for running WASM apps and the future of the technology.   Do you have something cool to share? Some questions? Let us know: - web: kubernetespodcast.com - mail: kubernetespodcast@google.com - twitter: @kubernetespod   News of the week WASMCon 2023: CFP Event Kyverno Project 1.10 Intro to Cilium course Microsoft Azure Linux is GA CNCF Glossary German edition is live Google C3 Machine family is available for GKE ChainGuard move from Github Registry to self-hosted Amazon Pull through cache on AWS container registry   Links from the interview Justin Cormack: Twitter LinkedIn Docker WebAssembly Docker+WASM asm.js asmjs.org V8 Javascript engine Google Sandboxing WebGPU ByteCode Alliance Containerd Mesos WASM Edge  

話したネタ denoの話 Bun first impressions Node.js、Deno、Bunとは何か？ JavaScriptランタイムとは何か？ サーバーサイドJavaScript expressを利用してWebサーバーを立てるコードは、Node.js以外でも動くのか？ ECMAScript と ランタイム との関係は？ TC39 Node.js はどんな経緯で生まれてきた？ Rubyを書くタイミングと、JavaScriptを書くタイミングでのコンテキストスイッチ netv8 イベントループモデルとは何か？ ブロッキング処理、for文やJSON.parse() なぜ、Node.jsはここまで人気が出たのか？ V8(JavaScriptエンジン)とは何か？ JavaScriptCore Edge Workerとの相性の良さ JITコンパイラ Denoはどういう背景で生まれてきているのか？ モジュールを取り巻く課題 JSConf JP 訂正 冒頭で第81回と話しておりますが、82回の誤りです。 番組のスポンサーD.Node採用募集ページはこちら

Ryan Dahl is the co-founder and creator of Deno, a runtime for JavaScript, TypeScript, and WebAssembly based on the V8 JavaScript engine and the Rust programming language. He is also the creator of Node.js. We interviewed Dahl for The New Stack Technical Founder Odyssey series. "Yeah, so we have a JavaScript runtime," Dahl said. "It's pretty similar in, in essence, to Node. It executes some JavaScript, but it's much more modern. " The Deno project started four years ago, Dahl said. He recounted how writing code helped him rethink how he developed Node. Dahl wrote a demo of a modern, server-side JavaSript runtime. He didn't think it would go anywhere, but sure enough, it did. People got pretty interested in it. Deno has "many, many" components, which serve as its foundation. It's written in Rust and C++ with a different type of event loop library. Deno has non-blocking IO as does Node. Dahl has built his work on the use of asynchronous technologies. The belief system carries over into how he manages the company. Dahl is an asynchronous guy and runs his company in such a fashion. As an engineer, Dahl learned that he does not like to be interrupted by meetings. The work should be as asynchronous as possible to avoid interruptions. Deno, the company, started during the pandemic, Dahl said. Everyone is remote. They pair program a lot and focus on short, productive conversations. That's an excellent way to socialize and look deeper into problems. How is for Dahl to go from programming to CEO? "I'd say it's relatively challenging," Dahl said. I like programming a lot. Ideally, I would spend most of my time in an editor solving programming problems. That's not really what the job of being a CEO is." Dahl said there's a lot more communication as the CEO operates on a larger scale. Engineering teams need management to ensure they work together effectively, deliver features and solve problems for developers. Overall, Dahl takes it one day at a time. He has no fundamental theory of management. He's just trying to solve problems as they come. "I mean, my claim to fame is like bringing asynchronous sockets to the mainstream with nonblocking IO and stuff. So, you know, asynchronous is deeply embedded and what I'm thinking about. When it comes to company organization, asynchronous means that we have rotating meeting schedules to adapt to people in different time zones. We do a lot of meeting recordings. So if you can't make it for whatever reason, you're not in the right time zone, you're, you know, you're, picking up your kids, whatever. You can go back and watch the recording. So we basically record every every meeting, we try to keep the meeting short. I think that's important because nobody wants to watch hours and hours of videos. And we use, we use chats a lot. And chat and email are forms of asynchronous communication where you don't need to kind of meet with people one on one. And yeah, I guess I guess the other aspect of that is just keeping meetings to a minimum. Like there's there's a few situations where you really need to get everybody in the room. I mean, there are certainly times when you need to do that. But I tried to avoid that as much as possible, because I think that really disrupts the flow of a lot of people working."

Node.js was first introduced in 2009 at the annual European JSConf. It's based on Chrome's V8 JavaScript engine and can be utilized in a variety of environments.  Every major release is actively maintained for at least 18 months. The platform works just as well for smaller businesses and ventures as it does for Fortune 500 companies.  Dev.co provides Node.js planning, development, and deployment that is unrivaled in the industry. We use the top technologies in the industry and employ rigorous testing and continual optimization. More info about node.js development services:    https://dev.co/node-js/   Connect with us:  SEO // PPC // DEV // WEBSITE DESIGN

Nesse episódio convidamos Rodrigo Branas(https://www.linkedin.com/in/rodrigobranas) para conversamos sobre JavaScript e NodeJS. Um pouco da história da linguagem, NodeJS e o futuro da stack front-end. Curso do Branas a respeito de JS > https://app.branas.io/public/products/c09d58ff-ce6b-491b-b158-9982583dff79 Curso Free do Branas a respeito de JS > https://www.youtube.com/playlist?list=PLQCmSnNFVYnT1-oeDOSBnt164802rkegc Curso Free do Branas a respeito de Node > https://www.youtube.com/playlist?list=PLQCmSnNFVYnTFo60Bt972f8HA4Td7WKwq https://www.youtube.com/watch?v=v2ifWcnQs6M - YUI Library https://www.coursera.org/lecture/javascript-jquery-json/bonus-john-resig-jquery-5Kc6W - jQuery https://requirejs.org/ https://tc39.es/ https://github.com/tc39/ecma262 https://www.youtube.com/watch?v=ztspvPYybIY - Ryan Dahl: Original Node.js presentation https://v8.dev/ - V8 JavaScript engine https://libuv.org/ - libuv | Cross-platform asynchronous I/O http://johnny-five.io/ - Johnny-Five https://nodejs.org/en/ - Node.js® is a JavaScript runtime built on Chrome's V8 JavaScript engine. https://deno.land/ - Deno - A modern runtime for JavaScript and TypeScript https://socket.io/ - Socket.IO https://www.npmjs.com/ https://llvm.org/ https://www.manning.com/books/micro-frontends-in-action

The Go Programming Language Go is an open-source programming language with influences from Limbo, C, APL, Modular, Oberon, Pascal, Alex, Erlang, and most importantly, C. While relatively young compared to many languages, there are over 365,000 repositories of Go projects on Github alone. There are a few reason it gained popularity so quickly: it's fast and efficient in the right hands, simple to pick up, doesn't have some of the baggage of some more mature languages, and the name Ken Thompson. The seamless way we can make calls from Go into C and the fact that Ken Thompson was one of the parties responsible for C, makes it seem in part like a modern web enabled language that can stretch between the tasks C is still used for all the way to playing fart sounds in an app. And it didn't hurt that co-author Rob Pike had whelped write books, co-created UTF-8, and was part of the distributed operating system Plan 9  team at Bell Labs and had worked on the Limbo programming language there.  And Robert Griesemer was another co-author. He'd begun his career studying under Niklaus Wirth, the greater of Pascal, Modula, and Oberon. So it's no surprise that he'd go on to write compilers and design languages. Before go, he'd worked on the V8 JavaScript engine at Google and a compiler for the Java HotSpot Virtual Machine. So our intrepid heroes assembled (pun intended) at Google in 2009. But why? Friends don't let friends write in C. Thompson had done something amazing for the world with C. But that was going on 50 years ago. And others had picked up the mantle with C++. But there were shortcomings the team wanted to address. And so Go has the ability to concatenate string variables without using a preprocessor, has many similarities to languages like BASIC from the Limbo influences, but the most impressive feature about this programming language is its support for concurrent execution. And probably the best garbage collection facility I've ever seen.  The first version of the language wasn't released to the public and wouldn't be for a few years. The initial compiler was written in C but over time they got to where it can be self-hosted, which is to say that Go is compiled in Go.  Go is a compiled language that can run on a command line, in a browser, on the server, or even be used to compile itself. Go compiles fast and has no global variables to clutter memory. This simplicity makes it easy to read through Go code line by line without consulting any parsing tools or syntax charts. Let's look at a quick Hello World: // A basic Go program that demonstrates "Hello World!"
package main
import "fmt"
func main() {
    fmt.Println("Hello World!")
} The output would be a simple Hello World! Fairly straight forward but the power gets into more of the scripting structures - especially given that a micro service is just a lot of little functional scripts. The language itself has no connection to any other functional programming languages and does not include support for object orientation or reflection. The language consists of two parts: a parser (which processes an input file) and a bytecode interpreter, which translates all source code into machine code. Consequently, Go programs tend to compile quickly and run very efficiently because they are mainly independent of the runtime environment and can execute directly on the hardware without being interpreted by some sort of virtual machine first. Additionally, there is no need for a separate interpreter during execution since everything runs natively. The libraries and sources built using the Go programming language provide developers with a straightforward, safe, and extensibility system to build on. We have things like Go Kit, GORM, cli, Vegeta, fuzzy, Authboss, Image, Time, gg, and mgo. These can basically provide pre-built functions and APIs to hook into any old type of service or give a number of things for free. Go was well designed from the outset and while it's evolved over the years, it hasn't changed as much as many other languages. with the latest release being Go 1.17. 1.1 came just a couple of months after the initial release to increase how much memory could be used on 64 bit chips by about 10-fold, add detection for race conditions, added the uint for 64 bit integers. Oh and fixed a couple of issues in the compiler. 1.2 also came in 2013 and tweaked how slicing of arrays worked in a really elegant way (almost ruby-like) and allowed developers to call the runtime scheduler for non-inline calls. And added a thread limit, like the ulimit a bash would have, for 10,000 threads. And they doubled the grouting minimum size of the stack.  Then the changes got smaller. This happens as every language gets more popular. The more people use it, the more havoc the developers cause when they make breaking changes. Bigger changes are contiguous models of grouting stacks in 1.3, the addition of internal packages in 1.4, a redesigned garbage collector in 1.5 when Go was moved away from C and implemented solely in Go and assembler. And 17 releases later, it's more popular than ever. While C remains the most popular language today, Go is hovering in the top 10. Imagine, one day saying let's build a better language for concurrent programming. And then viola; hundreds of thousands of people are using it. 

Today we're joined by Ilya Grigorik to talk about Shopify's developer preview release of Hydrogen and the preview release of Oxygen which is in early access preview with select merchants on Shopify. Hydrogen is their React framework for dynamic, contextual, and personalized e-commerce. And Oxygen is Shopify's hosted V8 JavaScript worker runtime that leverages all of their platform with the hope of scaling millions of storefronts. We cover what developers can expect from the Hydrogen framework, Shopify's big bet on React Server Components, the future of Shopify at scale with Hydrogen powered by Oxygen, and a world where merchants never have to think about the complexities of scaling infrastructure.

Today we're joined by Ilya Grigorik to talk about Shopify's developer preview release of Hydrogen and the preview release of Oxygen which is in early access preview with select merchants on Shopify. Hydrogen is their React framework for dynamic, contextual, and personalized e-commerce. And Oxygen is Shopify's hosted V8 JavaScript worker runtime that leverages all of their platform with the hope of scaling millions of storefronts. We cover what developers can expect from the Hydrogen framework, Shopify's big bet on React Server Components, the future of Shopify at scale with Hydrogen powered by Oxygen, and a world where merchants never have to think about the complexities of scaling infrastructure.

Listen the Frontend News #11 - the podcast about tech and front end innovations with our hosts - Chris and Tommy K. Looking for a team for your project? Ask us for free consultation on https://frontendhouse.com. What is Frontend News #11 about? 00:00 - Intro00:47 - Contents1:53 - Chrome 92 boosts PWAPWA is Progressive Web Application - basically it is an application which can run in a browser and looks like an application: https://blog.chromium.org/2021/06/chrome-92-web-apps-as-file-handlers-new.html5:18 - DevTools updatesDevTools is a set of tools for web developers built into Google Chrome. https://developer.chrome.com/blog/new-in-devtools-92/ 8:47 - Node - Another great releaseNode is the regular guest of Frontend News as a bellowed by Frontend House developers JavaScript runtime on Chrome's V8 JavaScript engine: https://nodejs.org/en/blog/release/v16.3.0/ 10:38 - Happy Birthday Node!https://twitter.com/nodejs/status/1397914989931864080 11:00 - Maps and WebGL - what's in common?Web Graphics Library is a JavaScript API for rendering 3D and 2D graphics. https://cloud.google.com/blog/products/maps-platform/using-new-webgl-powered-maps-featuresCheck the video about projects for Google Maps: https://www.youtube.com/watch?v=WaTS9jctwuE&t=2s 13:29 - Electrifying Electron ReleaseElektron is a framework which enables building native applications with JavaScript, HTML, and CSS. You can check releases here: https://www.electronjs.org/blog/electron-13-014:44 - React Components Librarieshttps://retool.com/blog/react-component-libraries/If you have any development issues or have an idea for application you can always contact our Frontend House experts and have a free consultation on https://frontendhouse.com/

This week on The Chrome Cast, we begin the show by covering down on all the new features available in Chrome and Chrome OS 91. Between updates to the V8 JavaScript engine - dubbed Sparkplug - and the arrival of Nearby Share, version 91 of Chrome OS is a nice, incremental update that should improve performance across the board and provide a new, useful way for files to be shared across Google's growing line of Android and Chrome OS hardware. For the second half of the show, we focus in on reports surrounding the upcoming - and mysterious - Pixel Fold. As it turns out, Samsung is now supplying Google with not only foldable OLED screens, but also the ultra-thin glass it uses in the manufacturing of devices like the Galaxy Flip and Galaxy Fold phones. There are no additional details for now on what Google is planning or when we could see a folding Pixel, but this new news is definitely great fodder for discussion. NOTABLE LINKS Google is prepping a foldable device using Samsung's Ultra-Thin Glass Chrome OS 91 feature highlight: Nearby Share is fantastic [VIDEO] Phone Hub could soon bring app streaming to Chromebooks Chrome OS 91 is now rolling out to most Chromebooks, newer models still waiting Nearby Share arrives as Chrome OS 91 begins rolling out Chrome 91 adds built-in screenshot tool on Android and it is awesome Chrome 91 has up to 23% faster performance as a result of its new JavaScript compiler This episode is brought to you by VIZOR for Chromebooks! Are you a School or District with a Chromebook 1:1 program? If so, get ready for your summer intake today with VIZOR for Chromebooks. VIZOR is a Chromebook management solution that seamlessly integrates with the Google Admin Console and your Student information system. With VIZOR you can easily see which student has which Chromebook, manage repairs, and even automate disabling lost or stolen devices while notifying parents, all in one click. Listeners to this podcast get 2 months free, so be sure to tell them you heard about VIZOR on The Chrome Cast podcast to qualify. Click here to learn more about VIZOR for Chromebooks and qualify for 2 months free! This episode is brought to you by NordVPN. Get a VPN that takes your privacy seriously. NordVPN is our VPN of choice and will secure your browsing on your Chromebook or on any device. Use NordVPN to keep your private data to yourself whether you are at home or on the go! Click here to try it out and get a 3-year deal for $3.49/month. --- Support this podcast: https://anchor.fm/chromeunboxed/support

Anotaciones de tipos: ¿Son pythónicas? También versiones de paquetes y grafos de dependencias https://podcast.jcea.es/python/18 En este audio hay un hablante que no identifico. ¿Quien es?. Es quien habla, por ejemplo, en 01:06:00 o en 01:12:00. ¿Antoni? 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. Dani, conectando desde Málaga. Eduardo Castro, email: info@ecdesign.es. Conectando desde A Guarda. 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] Preámbulo. Design of CPython’s Garbage Collector: https://devguide.python.org/garbage_collector/. Dificultades con el horario de la tertulia. Podría haber más tertulias en otros horarios, llevadas por otras personas. Problemas para publicar los audios. Editar es un infierno. Las notas de los audios tienen una importancia transcendental. Dinámica de las tertulias. Antiguo podcast "Python en español": https://podcast.jcea.es/python/. [08:32] Presentaciones. Raspberry Pi Pico: https://www.raspberrypi.org/products/raspberry-pi-pico/. Micropython: https://www.micropython.org/. [13:32] El aviso legal para poder grabar los audios. [14:32] 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. [16:27] Lo importante que es abrir bugs, para que puedan solucionarse. Queja productiva. [18:12] Nueva versión de MYPY http://mypy-lang.org/ y MYPYC https://github.com/mypyc/mypyc, que aprovechan Python 3.9. Sigue fallando mucho. [20:42] pyannotate https://pypi.org/project/pyannotate/ para meter anotaciones de tipos de forma automática. Las dificultades de meter tipos en un proyecto ya maduro. [22:52] Puedes usar tipos o no. Son opcionales. Ventajas en equipos grandes. Linter: https://es.wikipedia.org/wiki/Lint. Impone disciplina y una cultura. Las anotaciones de tipos no se verifican en tiempo de ejecución. Se usan en el sistema de test e integración continua. Una de la ventaja de los "__slots__" es que si te equivocas en el nombre de atributo en una asignación, te dará un error claro. Los tipos ayudan aquí también. "pyannotate" https://pypi.org/project/pyannotate/. Las anotaciones de tipos te permiten luego compilar Python para ganar rendimiento "sin coste". Las anotaciones se pueden meter en el mismo código o en un fichero "compañero". Usar un fichero "compañero" es útil para poder usar anotaciones modernas en versiones antiguas de Python. Evitar "contaminar" el sistema de control de versiones con cambios masivos irrelevantes que ofuscan la historia de un proyecto. Por ejemplo, el autor original del código. Que los creadores de código y los etiquetadores de tipos sean personas diferentes. "typeshed": Collection of library stubs for Python, with static types: https://github.com/python/typeshed. ¿Y meter tipos en los comentarios, como se hacía antiguamente? Hay mucha literatura de ingeniería de software sobre si es bueno documentar tipos o no, según el tipo de equipo y el tipo de proyecto. [40:17] Python podría ser mucho más rápido aunque no se usen tipos. Podría ser mucho más inteligente. Descubrimiento de tipos en tiempo de ejecución. Tema recurrente. Numba: https://numba.pydata.org/. Javascript V8: https://en.wikipedia.org/wiki/V8_(JavaScript_engine). [43:06] Habiendo tantos compiladores, ¿por qué no se integra alguno en el intérprete normal de Python? Complejidad y compatibilidad. Faltan manos. Hay muchos "gérmenes" que no germinan. Dispersión de esfuerzos. [46:12] Puntos de dolor de Python para la gente que viene de otros lenguajes: Tipos. Velocidad. Espacios significantes. [46:37] ¿Qué es "Python"? Cada novedad de sintaxis de Python cambia el lenguaje. ¿Qué es Python? Problemas para los que llegan nuevos al lenguaje. Hay organizaciones grandes que un lenguaje sin tipos ni siquiera lo consideran. [51:22] Cultura común en todos los proyectos Python. Baja barrera de entrada si conoces esa cultura. La cultura va evolucionando. Solución de compromiso: Meter tipos solo en la frontera. [53:02] El tipado avanzado de Python 3.9 da un error de sintaxis al importar el código en una versión anterior de Python. [54:46] El operador morsa no se puede usar dentro de un "list comprehension": >>> [i for i in ('a', '' ,'b') if i := i.strip()] File "", line 1 [i for i in ('a', '' ,'b') if i := i.strip()] ^ SyntaxError: invalid syntax No queda otra que escribirlo como: >>> [i.strip() for i in ('a', '' ,'b') if i.strip()] ['a', 'b'] duplicando el i.strip(). [56:40] En versiones de Python anteriores a 3.8 no se podría usar un continue en un finally. El texto era https://docs.python.org/3.7/reference/compound_stmts.html#the-try-statement: When a return, break or continue statement is executed in the try suite of a try...finally statement, the finally clause is also executed ‘on the way out.’ A continue statement is illegal in the finally clause. (The reason is a problem with the current implementation — this restriction may be lifted in the future). Eso se solucionó en Issue32489: Allow 'continue' in 'finally' clause: https://bugs.python.org/issue32489. [57:47] f-string con datetime https://docs.python.org/3/library/datetime.html. Ya está en los propios ejemplos de PEP 498: Literal String Interpolation: https://www.python.org/dev/peps/pep-0498/. [59:22] Modo depuración en f-strings en Python 3.8: >>> a = 5 >>> f'{a=}' 'a=5' Útil para el loging. [01:00:47] Versiones fijas de dependencias y actualizar un despliegue. Herramientas para esto: "pip" https://pypi.org/project/pip/, "virtualenv" https://pypi.org/project/virtualenv/. "pipenv" https://pypi.org/project/pipenv/. "Poetry": https://pypi.org/project/poetry/. Grafo de dependencias "pip-tree": https://pypi.org/project/pip-tree/. Paralelismos con el enlazado estático y dinámico. [01:14:22] ¿Por qué se ha instalado este paquete, qué paquetes exige y qué paquetes dependen de él? pip show. Grafo de dependencias "pip-tree": https://pypi.org/project/pip-tree/. [01:19:22] Visualizar el grafo de versiones de un sistema de control de versiones moderno. Por ejemplo con Mercurial: "hg glog" https://www.mercurial-scm.org/. [01:23:07] Recogida de basuras: Design of CPython’s Garbage Collector: https://devguide.python.org/garbage_collector/. Hora de sacar la basura garbage collector - Pablo Galindo y Victor Terrón - PyConES 2018 https://www.youtube.com/watch?v=G9wOSExzs5g. La recolección de basura de la generación más antigua funciona de forma diferente. En vez de ser por un número fijo de desequilibrio entre creación y destrucción de objetos, funciona por porcentaje. [01:31:37] Divagación: Powerball https://powerball.org.uk/. [01:31:52] Explicación de cómo funciona "__slots__" https://docs.python.org/3/reference/datamodel.html. [01:34:22] Libro "CPython Internals": https://realpython.com/products/cpython-internals-book/. Website de "Real Python": https://realpython.com/. Merece bastante la pena. También tienen podcast: "The Real Python Podcast: Python Tips, Interviews, and More" https://realpython.com/podcasts/rpp/. [01:36:42] Más sobre "__slots__" https://docs.python.org/3/reference/datamodel.html. Técnica estándar. Un diccionario vacío ocupa 64 bytes: sys.getsizeof({}). Se puede usar para evitar errores mecanográficos al escribir en atributos. [01:38:52] "AutoScraper: A Smart, Automatic, Fast and Lightweight Web Scraper for Python" https://pypi.org/project/autoscraper/. Búsquedas "borrosas". Seguimos sin encontrar la biblioteca de scraping de foros de la que ha hablado Eduardo en tertulias anteriores. [01:43:02] Librería para dibujar grafos: graphviz https://pypi.org/project/graphviz/. Le das un texto describiendo nodos y conexiones entre nodos y calcula un gráfico. Sería trivial para dibujar el grafo de dependencias de "pip". Ejemplo: El gráfico de antes, con ciclos: https://lists.es.python.org/pipermail/general/attachments/20201229/0c14bc58/attachment-0002.png. El gráfico de después, sin ciclos: https://lists.es.python.org/pipermail/general/attachments/20201229/0c14bc58/attachment-0003.png. [01:47:22] ¿Cómo asegurarse que el nombre de un fichero no tenga caracteres extraños? ¡Problema de seguridad! Expresiones regulares. Cuidado con el unicode https://en.wikipedia.org/wiki/Unicode. Mejor usar una lista blanca que una lista negra. Usar pathlib.is_relative_to() https://docs.python.org/3/library/pathlib.html#pathlib.PurePath.is_relative_to. Novedad en Python 3.9. [01:52:07] ¡Usa la versión actual de Python, leches! Ahora mismo, Python 3.9. Ventajas de compilar el intérprete desde código fuente para no depender de la versión que te proporciona el sistema operativo. Puedes tener tu propio intérprete de Python dentro de un "virtualenv" https://pypi.org/project/virtualenv/. Proyectos "llave en mano". El cliente quiere algo que se instale como un componente en lo que ya conoce. Por ejemplo, en un panel de configuración en un servicio de hospedaje. [01:56:47] Jesús Cea repite una vez más la anécdota de que al principio de los tiempos para conducir un coche tenías que ser mecánico, pero ya no. Falta toda la base, pero... ¿Hace falta? [01:59:12] Memoria escasa en un microcontrolador. [01:59:55] Final.

Simple Programmer is now BACK with a brand new YouTube ChannelSUBSCRIBE HERE: https://simpleprogrammer.com/subscribespyt   You're going for your next coding interview for a node.js job. Then, you should expect lots of different questions regarding node.js. What do you do then? Why don't so many developers still don't prepare for questions about programming language and stuff? Node.js framework is actually not a framework or a library, but a runtime environment, based on Chrome’s V8 JavaScript engine. The technology was first introduced back in 2009 by Ryan Dahl at the annual European JSConf and was immediately recognized as “the most exciting single piece of software in the current JavaScript universe”. However, it wasn’t until recently that a wide adoption of server-side JavaScript with Node.js started. The interest in this technology peaked in 2014, as per Google Trends, and remains high. (Source: https://www.altexsoft.com/blog/engineering/the-good-and-the-bad-of-node-js-web-app-development/) In this case, you definitely should be prepared to answer questions like what are the pros & cons of node.js, what is node.js, and more. Answers should look like this: "Using Node.js for backend, you automatically get all the pros of full stack JavaScript development, such as: better efficiency and overall developer productivity code sharing and reuse speed and performance easy knowledge sharing within a team huge number of free tools" In today's video we'll go through some Q&A about node.js and how you can nail your next coding interview applying for a node.js position.

Scientists at MIT have taken peptides from a South American wasp's venom to create a medicine that kills bacteria but not human cells. It's official. Microsoft will rebuild the Edge browser to run on Chromium and use the Blink and V8 JavaScript engines. The Large Hadron Collider is shutting down for two years for upgrades. Netflix confirmed to the LA times it is testing an instant replay feature. And our recaps of what we loved in 2018!

Diese Revision hatten wir Benedikt Meurer (Web, Twitter, Github), seines Zeichens Tech Lead bei V8, zu Gast. Schaunotizen [00:00:55] Die V8 JavaScript Engine Benedikt erzählt uns, was sich in V8 seit Revision 8 und der Einführung von Crankshaft getan hat. Eigentlich ist kein Stein auf dem anderen geblieben. Nach einem kleinen Überblick über optimierende Compiler […]

Myles Borins talks with Mark and Francesc about Node.js from its history, how to contribute, the consensus-seeking governance, and why it's important to Google Cloud Platform. Node.js is an open-source, JavaScript runtime environment built on Chrome's V8 JavaScript engine, and Google is a Platinum Member of the Node.js Foundation. About Myles Borins Myles Borins is a developer, musician, artist, and maker he works for Google as a developer advocate serving the Node.js ecosystem he graduated with a Master of Music Science and Technology from c.c.r.m.a. a.k.a the center for computer research in music and acoustics Cool things of the week Reduced GPU prices on GCP and preemptible local SSDs blog Skylake processors now available in 7 regions blog New Episodes of Learn TensorFlow and Deep Learning, without a PhD: Modern Convolutional Neural Nets video Modern RNN Architectures video Deep Reinforcement Leanring video Interview Node.js site Node.js on Google Cloud Platform site docs Node School site Node.js with Justin Beckwith podcast App Engine site docs Cloud Functions site docs Kubernetes Engine site doc Introduction to Kubernetes: How to Deploy a Node.js Docker App site Socket.io site Question of the week How do you give public postmordems? Fearless shared postmortems - CRE life lessons blog Where can you find us next? Mark will be Montreal in December to speak at Montreal International Games Summit. Melanie will be at SOCML (Self-Organizing Conference on Machine Learning) end of this week and NIPS (Neural Information Processing Systems) in Long Beach next week.

@yosuke_furukawaさんとNode.jsの過去・現在の話をしました（前編） The C10K problem Ryan Dahl: Node.js, Evented I/O for V8 Javascript libebb http://socket.io/ どうしてこうなった？ Node.jsとio.jsの分裂と統合の行方。これからどう進化していくのか？ Node Forward Node.jsのコミュニティに変化を与えるnode-forwardについて io.jsについて知っていること

Panel Kris Kowal (twitter github blog) Domenic Denicola (twitter github blog) AJ O’Neal (twitter github blog) Jamison Dance (twitter github blog) Joe Eames (twitter github blog) Merrick Christensen (twitter github) Charles Max Wood (twitter github Teach Me To Code Intro to CoffeeScript) Discussion 02:41 - Promises Asynchonous programming 05:09 - Using Promises from top to bottom 07:08 - Domains NodeConf SummerCamp 07:55 - Q 10:22 - q.nfbind 11:15 - Q vs jQuery You’re Missing the Point of Promises Coming from jQuery 15:41 - long-stack-traces turn chaining JavaScriptStackTraceApi: Overview of the V8 JavaScript stack trace API (error.prepare stack trace) 19:36 - Original Promises/A spec and Promises/A+ spec when.js Promises Test Suite Underscore deferred 24:22 - .then Chai as Promised 26:58 - Nesting Promises spread method 28:38 - Error Handling causeway 32:57 - Benefits of Promises Error Handling Multiple Async at once Handle things before and after they happen 40:29 - task.js 41:33 - Language e programming language CoffeeScript 44:11 - Mocking Promises 45:44 - Testing Promises Mocha as Promised Picks Code Triage (Jamison) The Creative Sandbox Guidebook (Joe) Steam (Joe) Pluralsight (Joe) montage (Kris) montagejs / mr (Kris) CascadiaJS 2012 - Domenic Denicola (Domenic) Omnifocus (Chuck) Buckyballs (AJ) Transcript JOE: I can’t imagine your baby face with a beard, Jamison. JAMISON: I never thought I had a baby face. AJ: It was always a man face to me. JOE: Everybody who is 15 years younger than me has a baby face. [This episode is sponsored by ComponentOne, makers of Wijmo. If you need stunning UI elements or awesome graphs and charts, then go to wijmo.com and check them out.] [This show is sponsored by Gaslight Software. They are putting on Mastering Backbone training in San Francisco at the Mission Bay Conference Center, December 3rd through 5th. They'll be covering Jasmine, Backbone and CoffeeScript. For more information or to register, go to training.gaslightsoftware.com] [Hosting and bandwidth provided by the Blue Box Group. Check them out at bluebox.net] CHUCK: Hey everybody. Welcome to episode 37 of the JavaScript Jabber show. This week on our panel, we have AJ O'Neal. AJ: Yo, yo, yo, comin' at you live from the executive boardroom suite of Orem, Utah. CHUCK: Jamison Dance. JAMISON: Hey guys! CHUCK: Joe Eames. JOE: Hey there! CHUCK: Merrick Christensen MERRICK: What's up. CHUCK: I'm Charles Max Wood from devchat.tv and this week we have some guests -- and that is Kris Kowal. KRIS: Hello. Yeah, Kowal. CHUCK: Kowal. OK. And Domenic Denicola. Did I say that right? DOMENIC: Denicola. CHUCK: Denicola. DOMENIC: It’s OK I got Americanized. That's probably the proper Italian pronunciation. Hi guys! CHUCK: I speak proper Italian, so probably. KRIS: Yeah and for what it’s worth, I think that the proper Polish is Kowal or something, but yeah. JAMISON: Kris, are you from the Midwest? You have kind of Minnesota-ish accent. KRIS: No. I'm actually unfortunately from somewhere in the suburbs of Los Angeles, but I grew up indoors and did listen to Prairie Home Companion. So I don’t know. Maybe. [laughter] CHUCK: Awesome. All right. So this week we are going to be talking about… actually there's one thing I need to announce before. If you are listening to this episode, you’ll probably notice a little bit of a difference with our sponsorship message. I actually left off one important piece to one of the sponsorship messages and that is for the Gaslight software training that's going to be in San Francisco, if you wanna sign up, go to training.gaslightsoftware.com and you can sign up there. They’ve been a terrific sponsor and I feel kind of bad that I botched that. But anyway,

Panel Kris Kowal (twitter github blog) Domenic Denicola (twitter github blog) AJ O’Neal (twitter github blog) Jamison Dance (twitter github blog) Joe Eames (twitter github blog) Merrick Christensen (twitter github) Charles Max Wood (twitter github Teach Me To Code Intro to CoffeeScript) Discussion 02:41 - Promises Asynchonous programming 05:09 - Using Promises from top to bottom 07:08 - Domains NodeConf SummerCamp 07:55 - Q 10:22 - q.nfbind 11:15 - Q vs jQuery You’re Missing the Point of Promises Coming from jQuery 15:41 - long-stack-traces turn chaining JavaScriptStackTraceApi: Overview of the V8 JavaScript stack trace API (error.prepare stack trace) 19:36 - Original Promises/A spec and Promises/A+ spec when.js Promises Test Suite Underscore deferred 24:22 - .then Chai as Promised 26:58 - Nesting Promises spread method 28:38 - Error Handling causeway 32:57 - Benefits of Promises Error Handling Multiple Async at once Handle things before and after they happen 40:29 - task.js 41:33 - Language e programming language CoffeeScript 44:11 - Mocking Promises 45:44 - Testing Promises Mocha as Promised Picks Code Triage (Jamison) The Creative Sandbox Guidebook (Joe) Steam (Joe) Pluralsight (Joe) montage (Kris) montagejs / mr (Kris) CascadiaJS 2012 - Domenic Denicola (Domenic) Omnifocus (Chuck) Buckyballs (AJ) Transcript JOE: I can’t imagine your baby face with a beard, Jamison. JAMISON: I never thought I had a baby face. AJ: It was always a man face to me. JOE: Everybody who is 15 years younger than me has a baby face. [This episode is sponsored by ComponentOne, makers of Wijmo. If you need stunning UI elements or awesome graphs and charts, then go to wijmo.com and check them out.] [This show is sponsored by Gaslight Software. They are putting on Mastering Backbone training in San Francisco at the Mission Bay Conference Center, December 3rd through 5th. They'll be covering Jasmine, Backbone and CoffeeScript. For more information or to register, go to training.gaslightsoftware.com] [Hosting and bandwidth provided by the Blue Box Group. Check them out at bluebox.net] CHUCK: Hey everybody. Welcome to episode 37 of the JavaScript Jabber show. This week on our panel, we have AJ O'Neal. AJ: Yo, yo, yo, comin' at you live from the executive boardroom suite of Orem, Utah. CHUCK: Jamison Dance. JAMISON: Hey guys! CHUCK: Joe Eames. JOE: Hey there! CHUCK: Merrick Christensen MERRICK: What's up. CHUCK: I'm Charles Max Wood from devchat.tv and this week we have some guests -- and that is Kris Kowal. KRIS: Hello. Yeah, Kowal. CHUCK: Kowal. OK. And Domenic Denicola. Did I say that right? DOMENIC: Denicola. CHUCK: Denicola. DOMENIC: It’s OK I got Americanized. That's probably the proper Italian pronunciation. Hi guys! CHUCK: I speak proper Italian, so probably. KRIS: Yeah and for what it’s worth, I think that the proper Polish is Kowal or something, but yeah. JAMISON: Kris, are you from the Midwest? You have kind of Minnesota-ish accent. KRIS: No. I'm actually unfortunately from somewhere in the suburbs of Los Angeles, but I grew up indoors and did listen to Prairie Home Companion. So I don’t know. Maybe. [laughter] CHUCK: Awesome. All right. So this week we are going to be talking about… actually there's one thing I need to announce before. If you are listening to this episode, you’ll probably notice a little bit of a difference with our sponsorship message. I actually left off one important piece to one of the sponsorship messages and that is for the Gaslight software training that's going to be in San Francisco, if you wanna sign up, go to training.gaslightsoftware.com and you can sign up there. They’ve been a terrific sponsor and I feel kind of bad that I botched that. But anyway,

Panel Kris Kowal (twitter github blog) Domenic Denicola (twitter github blog) AJ O’Neal (twitter github blog) Jamison Dance (twitter github blog) Joe Eames (twitter github blog) Merrick Christensen (twitter github) Charles Max Wood (twitter github Teach Me To Code Intro to CoffeeScript) Discussion 02:41 - Promises Asynchonous programming 05:09 - Using Promises from top to bottom 07:08 - Domains NodeConf SummerCamp 07:55 - Q 10:22 - q.nfbind 11:15 - Q vs jQuery You’re Missing the Point of Promises Coming from jQuery 15:41 - long-stack-traces turn chaining JavaScriptStackTraceApi: Overview of the V8 JavaScript stack trace API (error.prepare stack trace) 19:36 - Original Promises/A spec and Promises/A+ spec when.js Promises Test Suite Underscore deferred 24:22 - .then Chai as Promised 26:58 - Nesting Promises spread method 28:38 - Error Handling causeway 32:57 - Benefits of Promises Error Handling Multiple Async at once Handle things before and after they happen 40:29 - task.js 41:33 - Language e programming language CoffeeScript 44:11 - Mocking Promises 45:44 - Testing Promises Mocha as Promised Picks Code Triage (Jamison) The Creative Sandbox Guidebook (Joe) Steam (Joe) Pluralsight (Joe) montage (Kris) montagejs / mr (Kris) CascadiaJS 2012 - Domenic Denicola (Domenic) Omnifocus (Chuck) Buckyballs (AJ) Transcript JOE: I can’t imagine your baby face with a beard, Jamison. JAMISON: I never thought I had a baby face. AJ: It was always a man face to me. JOE: Everybody who is 15 years younger than me has a baby face. [This episode is sponsored by ComponentOne, makers of Wijmo. If you need stunning UI elements or awesome graphs and charts, then go to wijmo.com and check them out.] [This show is sponsored by Gaslight Software. They are putting on Mastering Backbone training in San Francisco at the Mission Bay Conference Center, December 3rd through 5th. They'll be covering Jasmine, Backbone and CoffeeScript. For more information or to register, go to training.gaslightsoftware.com] [Hosting and bandwidth provided by the Blue Box Group. Check them out at bluebox.net] CHUCK: Hey everybody. Welcome to episode 37 of the JavaScript Jabber show. This week on our panel, we have AJ O'Neal. AJ: Yo, yo, yo, comin' at you live from the executive boardroom suite of Orem, Utah. CHUCK: Jamison Dance. JAMISON: Hey guys! CHUCK: Joe Eames. JOE: Hey there! CHUCK: Merrick Christensen MERRICK: What's up. CHUCK: I'm Charles Max Wood from devchat.tv and this week we have some guests -- and that is Kris Kowal. KRIS: Hello. Yeah, Kowal. CHUCK: Kowal. OK. And Domenic Denicola. Did I say that right? DOMENIC: Denicola. CHUCK: Denicola. DOMENIC: It’s OK I got Americanized. That's probably the proper Italian pronunciation. Hi guys! CHUCK: I speak proper Italian, so probably. KRIS: Yeah and for what it’s worth, I think that the proper Polish is Kowal or something, but yeah. JAMISON: Kris, are you from the Midwest? You have kind of Minnesota-ish accent. KRIS: No. I'm actually unfortunately from somewhere in the suburbs of Los Angeles, but I grew up indoors and did listen to Prairie Home Companion. So I don’t know. Maybe. [laughter] CHUCK: Awesome. All right. So this week we are going to be talking about… actually there's one thing I need to announce before. If you are listening to this episode, you’ll probably notice a little bit of a difference with our sponsorship message. I actually left off one important piece to one of the sponsorship messages and that is for the Gaslight software training that's going to be in San Francisco, if you wanna sign up, go to training.gaslightsoftware.com and you can sign up there. They’ve been a terrific sponsor and I feel kind of bad that I botched that. But anyway,

Technical Fellow Steve Lucco (architect and lead engineer of IE's Chakra JS VM) and Google's V8 and Dart architect Lars Bak discuss JavaScript, from a virtual machine perspective (implementer's view point). IE and Chrome employ different strategies (although they do share some things in common) to make JavaScript execute faster. What are these strategies? How do Chakra and V8 differ? How are they similar? How fast can Lars and Steve make JavaScript go, anyway? What's the speed limit for JavaScript execution? What languages are used to write these VMs? (Hint, both start with C...)This is a candid technical conversation among two excellent software engineers tasked with making JavaScript run as fast as possible in their respective JS VMs. The conversation also includes a brief discussion on open source technologies.This was filmed at GOTO Aarhus 2012, an excellent developer event. Huge thanks to Lars and Steve for the excellent conversation and to the folks at GOTO for providing a room for me for all these interviews (and lights, too!).