Java, Vaadin, Web and vanilla Web Components

An airhacks.fm conversation with Alejandro Duarte (@alejandro_du) about: IBM PC with DOS and Windows 311, starting windows with "win", playing Wolfenstein 3d, writing anti-virus simulations, enjoying watching others playing, developing pixel-draw, learning C after Q-Basic, fascination with executable files, building the apocalypse game "2040", working with tiles, the Object Oriented programming and gaming, learning Java after C++, Java's portability is a fake, ray tracing vs. ray casting, three.js and a-frame, Struts 1 and Angular 1 were similar, using JQuery, the JQuery spaghetti code, we only can hope, that Google Web Toolkit (GWT) works well, starting with Java EE company in financial sector, Vaadin was the remedy to GWT, writing a "Vaadin 7 UI Design by Example" book for Packt, the desire to learn Java EE, working for Vaadin in Finland, the great city of Turku, publishing the "Data-centric applications with Vaadin 8" book, I know Angular ...should I also learn JavaScript?, Vaadin would extend the components for you, using vanilla Web Components with Vaadin Components, using Bulma CSS for consistency, SAP UI 5 Web Components, ING Lion and Vaadin Web Components, the challenge of keeping the build system operational, typescript in Vaadin, syncing the client-side Data Transfer Objects with the backend, JavaScript prior 2015 was problematic, modern JavaScript looks like Java, JavaScript destructuring is great, object destructuring will come to Java, ES Modules are like Java packages, JavaScript is like HashMap of HashMaps, Alejandro Duarte on twitter: @alejandro_du, Alejandro's alejandrodu.com, and Alejandro on github