Computer program which translates code from one programming language to another
POPULARITY
In this interview, our Moore's Lobby host, Daniel Bogdanoff, chats with Rodger Richey, Vice President of Development Tools and Academic Programs at Microchip Technology. Rodger shares how his passion for engineering began with childhood curiosity, dismantling and repairing devices like a microwave. Those early hands-on experiences laid the foundation for his electrical engineering career, which started with designing underwater electronics for the U.S. Navy. Rodger discusses the evolution of development tools and the growing complexity of embedded systems over his 30-year tenure at Microchip. He emphasizes the importance of creating accessible and user-friendly tools, such as IDEs and development boards, to help developers tackle increasingly sophisticated projects. The integration of AI into development workflows is a major milestone, enabling enhanced productivity and better debugging. Rodger also highlights his involvement in academia, spearheading initiatives like virtual internships and hands-on learning programs to better prepare students for industry roles. By providing real-world tools and fostering collaboration, these programs aim to bridge the gap between theoretical education and practical application. Rodger attributes his longevity at Microchip to its strong values, collaborative culture, and dedication to innovation, which have remained consistent even as the company has grown significantly.
Dr. Beckett and Rich Klein dive into a 'Hobby Significance Tournament,' evaluating the hobby impact of various Baseball Hall of Fame contenders, then also exploring the significance of defunct football card companies from 1992 such as ProSet, Action Packed, and Wildcard. The discussion covers player impact, market evolution, and card company innovations. 03:17 Analyzing the Impact of Steroid-Era Players 04:59 The Case for Compilers and Controversial Figures 06:35 Players with Slim Hall of Fame Chances 07:46 The Final Batch of Baseball Candidates 09:23 1992 Football Card Manufacturers Tournament
Lua – уникальный язык программирования, так и не ставший массовым, но при этом занявший кучу разных ниш. Его используют, чтобы писать моды для Factorio, Minecraft и Roblox, высоконагруженную логику для nginx, скрипты для redis, плагины для neovim и wireshark, и даже софт для микроконтроллеров. Все это стало возможным благодаря некоторым дизайновым решениям, которые сделали Lua самым удобным языком для встраивания в другие системы. Антон Солдатов, долгое время разрабатывавший код на Lua в IPONWEB, а также участвовавший в разработке внутреннего форка LuaJIT, рассказал нам все, что нужно знать про этот язык. Партнёр эпизода — образовательная платформа Грейд от Яндекс Практикума. Грейд помогает руководителям и тимлидам точечно обучать сотрудников или целые команды навыкам для конкретных бизнес-задач: подготовить команду к новому проекту, вырастить стажеров или переобучить сотрудника для новой роли. На платформе Грейда более 1000 навыков, а также возможность конструировать обучение под запрос, наблюдать за прогрессом и измерять эффективность — там, где раньше нужно было несколько разных решений, теперь достаточно одной подписки. Переходите по ссылке (https://cutt.ly/seIUESyu) и оставляйте заявку, чтобы получить бесплатный демо-доступ на неделю — он работает сразу для всей команды. Реклама. АНО ДПО «Образовательные технологии Яндекса», ИНН 7704282033, erid:2SDnjdHxW98 Также ждем вас, ваши лайки, репосты и комменты в мессенджерах и соцсетях! Telegram-чат: https://t.me/podlodka Telegram-канал: https://t.me/podlodkanews Страница в Facebook: www.facebook.com/podlodkacast/ Twitter-аккаунт: https://twitter.com/PodlodkaPodcast Ведущие в выпуске: Стас Цыганов, Егор Толстой Полезные ссылки: LuaVela GitHub https://github.com/luavela/luavela HOPL Paper on Lua https://www.lua.org/doc/hopl.pdf Reddit: Where is Lua Used in the Real World https://www.reddit.com/r/lua/comments/1awn54q/where_is_lua_used_in_the_real_world/ LuaJIT https://luajit.org/ Sailor Project GitHub https://github.com/sailorproject/sailor Reddit: Tracing JIT Compilers https://www.reddit.com/r/Compilers/comments/7pf8b1/have_tracing_jit_compilers_lost/ LuaLang Telegram https://t.me/LuaLang ProLua Telegram https://t.me/ProLua Awesome Lua GitHub https://github.com/LewisJEllis/awesome-lua LuaRocks https://luarocks.org/ Reddit: Lua to Lisp Discussion https://www.reddit.com/r/lisp/comments/x0covh/lua_to_lisp_is_lua_just_sugared_lisp/?rdt=38752
In this episode Tor and Romain find themselves without a guest and decide to chat about micro optimizations and writing custom tools. Tor and Romain Chapters: Intro (00:00) Micro optimizations (00:32) Kotlin explorer (3:25) Avoiding object allocations (6:49) Code Inefficiencies (8:10) Compilers (12:13) Understand assembly with AI (18:39) Layout opt (21:20) Programmers writing tools (21:52) char.isBlank (25:35) Lint checks (27:59) Companion objects (29:40) Java assertion mechanism (32:00) Hash maps (35:13) When to micro optimize and when not to (43:46) Benchmarking (47:26) New optimizations (48:46) Wrap up (50:46) Romain: @romainguy, threads.net/@romainguy, romainguy@androiddev.social Tor: threads.net/@tor.norbye and tornorbye@androiddev.social Catch videos on YouTube → https://goo.gle/adb-podcast Subscribe to Android Developers → https://goo.gle/AndroidDevs
As you'd expect, any conversation with Aaron inevitably involves Ruby, Rails, compilers, and profiling. In this episode, we delve into all these topics. Enjoy!
Join us as we dive into the world of tech with award-winning software developer and robotics expert, Ron Evans. With a rich background in IoT, computer vision, and open source contributions, Ron has helped giants like AT&T, Intel, and Northvolt tackle their toughest challenges. As the maintainer of TinyGo and the creator of Gobot and GoCV, Ron shares his journey, insights, and captivating stories in this episode. Don't miss this opportunity to learn from a true pioneer in the field!00:00 Introduction00:24 First Paid Hardware Project08:50 Working at Apple 22:40 Leaving Apple27:23 Finance and Tech 46:13 Ron and TinyGo 53:20 Compilers and WASM1:03:42 Mechanoid Project 1:10:28 GoCV Project1:17:25 Contact InformationConnect with Ron: Twitter: https://twitter.com/@deadprogramLinkedIn: https://www.linkedin.com/in/deadprogram/Mentioned in today's episode:TinyGo: https://tinygo.org/RISC-V: https://riscv.org/WASI: https://pkg.go.dev/github.com/stealthrocket/wasi-goRust: https://www.rust-lang.org/learnZig: https://ziglang.org/GoCV: https://gocv.io/Want more from Ardan Labs? You can learn Go, Kubernetes, Docker & more through our video training, live events, or through our blog!Online Courses : https://ardanlabs.com/education/ Live Events : https://www.ardanlabs.com/live-training-events/ Blog : https://www.ardanlabs.com/blog Github : https://github.com/ardanlabs
This is a recap of the top 10 posts on Hacker News on May 19th, 2024.This podcast was generated by wondercraft.ai(00:36): Llama3 implemented from scratchOriginal post: https://news.ycombinator.com/item?id=40408880&utm_source=wondercraft_ai(02:09): Coding My HandwritingOriginal post: https://news.ycombinator.com/item?id=40408291&utm_source=wondercraft_ai(03:58): The Lunacy of ArtemisOriginal post: https://news.ycombinator.com/item?id=40410404&utm_source=wondercraft_ai(05:49): Transforming a QLC SSD into an SLC SSDOriginal post: https://news.ycombinator.com/item?id=40405578&utm_source=wondercraft_ai(07:43): Operation CHARM: Car repair manuals for everyoneOriginal post: https://news.ycombinator.com/item?id=40409588&utm_source=wondercraft_ai(09:37): Hertz Charging a Tesla Renter for Gas Was Not an Isolated IncidentOriginal post: https://news.ycombinator.com/item?id=40410341&utm_source=wondercraft_ai(11:09): Swarming Proxima Centauri: Picospacecraft Swarms over Interstellar DistancesOriginal post: https://news.ycombinator.com/item?id=40407228&utm_source=wondercraft_ai(12:57): Compilers for free with wevalOriginal post: https://news.ycombinator.com/item?id=40406194&utm_source=wondercraft_ai(14:52): AI doppelgänger experiment – Part 1: The trainingOriginal post: https://news.ycombinator.com/item?id=40407927&utm_source=wondercraft_ai(16:53): Beating Jeff's 3.14 Ghz Raspberry Pi 5Original post: https://news.ycombinator.com/item?id=40409718&utm_source=wondercraft_aiThis is a third-party project, independent from HN and YC. Text and audio generated using AI, by wondercraft.ai. Create your own studio quality podcast with text as the only input in seconds at app.wondercraft.ai. Issues or feedback? We'd love to hear from you: team@wondercraft.ai
Ali Rida Rizek (Ph.D., Arabic and Islamic Studies, University of Göttingen 2021) is a scholar of the social and intellectual history of Islam, with a particular focus on Twelver Shiʿism. He received his BA and MA in Arabic Language and Literature from the American University of Beirut (AUB) in Lebanon. He has taught at the American University of Beirut (AUB), the Lebanese American University (LAU), the University of Leiden, the University of Göttingen, and the University of Bayreuth in Germany. His research focuses on the history of Islamic law, Qurʾanic studies, Arabic literature, and classical Islamic education. He has published studies on hadith, legal history, and the classical Islamic ethical discourse. His upcoming book examines, for the first time in a monograph, the life, work, and impact of two early Imāmī legal scholars, namely Ibn Abī ʿAqīl al-ʿUmānī and Ibn al-Junayd al-Iskāfī (both flourishing in the 4th/10th century).
Wes and Scott dive deep into the world of JavaScript toolchains, exploring everything from linters and compilers to transpilers and formatters. Tune in as they shed light on cutting-edge technologies like Biome, UnJS, and Ezno that are shaping the future for developers. Show Notes 00:00 Welcome to Syntax! 01:37 Syntax is on YouTube. 02:09 Do we really need tooling? 04:02 Popular tools are predominantly plug and play. 06:15 What can tooling do for us? 07:16 The tools in today's workflow. 07:21 Linters. 11:29 Compilers and transpilers. 13:30 Formatters. 16:18 Tokenizers and Parsers. 16:46 Bundlers. 17:59 Macros. 20:26 The new tools in the space. 20:47 Biome, one toolchain for your web project. 28:27 Oxc, the JavaScript oxidation compiler. 33:01 Deno, code formatting. 34:13 ESBuild, an extremely fast bundler for the web. 34:37 Rolldown, fast Rust-based bundler for JavaScript. 38:34 Ezno, TypeScript type checker. 40:24 UnJS, Unleash JavaScript's Potential. 41:45 Lightning CSS, CSS parser, transformer, bundler, and minifier. 42:31 Is JavaScript good enough to handle these tools? 43:26 Sick Picks + Shameless Plugs. Sick Picks Scott: Shinobi-Geddon: The 1980s Ninja Craze Wes: Bachans Japanese Barbecue Sauce Shameless Plugs Scott: Syntax on YouTube Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott:X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads
Grace Hopper is one of the most iconic people in the world of software. Her career as a mathematician, software innovator, computer science advocate, programmer, and technical leader spanned the early era of computing through to the 1990s. One of the first notable computer programmers, Hopper developed the first programming text book, one of the first compilers, and perhaps most importantly she was the visionary who ideated and developed the first programming language with an English-like syntax. That programming language, FLOW-MATIC, was instrumental in the later development of COBOL, which she advised. COBOL is still used to this day. Her contributions were immense and her legacy has been honored by multiple national awards and the naming of the largest conference for women in software. Show Notes Harvard IBM Mark I - Manual via Harvard The Queen of Code via YouTube Grace Hopper: The Math Genius who Taught Computers to Talk via Fierce Grace Hopper: Full lecture at the University of Tennessee, 1983 via YouTube Grace Hopper via Wikipedia FLOW-MATIC via Wikipedia Episode 11: What is a Programming Language? Episode 87: Compilers and Interpreters Episode 129: BASIC Follow us on X @KopecExplains. Theme “Place on Fire” Copyright 2019 Creo, CC BY 4.0 Find out more at http://kopec.liveRead transcript
Richard talks to Thorsten Ball, a programmer at Zed Industries and author of two books on compilers. They start out talking about the differences between compilers and interpreters, what the trickiest parts are of teaching compilers, and then end up talking about the unnecessary complexity that has taken over modern Web Development.
In this episode we talk with Guannan Wei, from Purdue University. Guannan finished his PhD last year under Tiark Rompf, and is currently doing his Post-Doc with Tiark. Guannan has worked on a plethora of different compilers topics, and in this conversation we will talk about Staging, Futamura Projections, Symbolic Execution, Compiler Applications in Smart Contracts and Quantum Programming. Towards the end of the episode we also talk about his application experiences for the position of a Professorship in the US an a few other contries. Guannan's Website @guannanwei on X
In this episode we talk with Guannan Wei, from Purdue University. Guannan finished his PhD last year under Tiark Rompf, and is currently doing his Post-Doc with Tiark. Guannan has worked on a plethora of different compilers topics, and in this conversation we will talk about Staging, Futamura Projections, Symbolic Execution, Compiler Applications in Smart Contracts and Quantum Programming. Towards the end of the episode we also talk about his application experiences for the position of a Professorship in the US an a few other contries. Guannan's Website @guannanwei on X
In this episode we talk with Guannan Wei, from Purdue University. Guannan finished his PhD last year under Tiark Rompf, and is currently doing his Post-Doc with Tiark. Guannan has worked on a plethora of different compilers topics, and in this conversation we will talk about Staging, Futamura Projections, Symbolic Execution, Compiler Applications in Smart Contracts and Quantum Programming. Towards the end of the episode we also talk about his application experiences for the position of a Professorship in the US an a few other contries. Guannan's Website @guannanwei on X
Intro topic: Monitor setupsNews/Links:BlueScuti, Willis, beats Tetrishttps://www.youtube.com/watch?v=GuJ5UuknsHUPalWorld accused of being an AI Producthttps://www.forbes.com/sites/paultassi/2024/01/22/palworld-accused-of-using-genai-with-no-evidence-so-far/?sh=26a9651b42394 Billion if-statements to determine if a number is even or oddhttps://andreasjhkarlsson.github.io/jekyll/update/2023/12/27/4-billion-if-statements.htmlSeamless M4Thttps://ai.meta.com/blog/seamless-m4t/Book of the ShowPatrick:Foundation by Isaac Asimovhttps://amzn.to/3SrmgnPJason: Propaganda by Edward Bernayshttps://amzn.to/47JUCXJPatreon Plug https://www.patreon.com/programmingthrowdown?ty=hTool of the ShowPatrick: The Room Gamehttps://www.fireproofgames.com/games/the-roomJason:Incredibuildhttps://www.incredibuild.com/Topic: Compilers and Interpreters (Request by Jessica W.)Machine CodeArchitecture SpecificAssemblySingle vs Two Pass CompilerHigh level LanguagesIntermediate RepresentationJVM ByteCode vs Machine Code for portabilityScripting/InterpretersJITProfile Guided OptimizationResourceshttps://www.craftinginterpreters.com/https://nandgame.com/Turing Complete ★ Support this podcast on Patreon ★
On today's episode, Elixir Wizards Owen Bickford and Dan Ivovich compare notes on building web applications with Elixir and the Phoenix Framework versus Ruby on Rails. They discuss the history of both frameworks, key differences in architecture and approach, and deciding which programming language to use when starting a project. Both Phoenix and Rails are robust frameworks that enable developers to build high-quality web apps—Phoenix leverages functional programming in Elixir and Erlang's networking for real-time communication. Rails follows object-oriented principles and has a vast ecosystem of plug-ins. For data-heavy CRUD apps, Phoenix's immutable data pipelines provide some advantages. Developers can build great web apps with either Phoenix or Rails. Phoenix may have a slight edge for new projects based on its functional approach, built-in real-time features like LiveView, and ability to scale efficiently. But, choosing the right tech stack depends heavily on the app's specific requirements and the team's existing skills. Topics discussed in this episode: History and evolution of Phoenix Framework and Ruby on Rails Default project structure and code organization preferences in each framework Comparing object-oriented vs functional programming paradigms CRUD app development and interaction with databases Live reloading capabilities in Phoenix LiveView vs Rails Turbolinks Leveraging WebSockets for real-time UI updates Testing frameworks like RSpec, Cucumber, Wallaby, and Capybara Dependency management and size of standard libraries Scalability and distribution across nodes Readability and approachability of object-oriented code Immutability and data pipelines in functional programming Types, specs, and static analysis with Dialyzer Monkey patching in Ruby vs extensible core language in Elixir Factors to consider when choosing between frameworks Experience training new developers on Phoenix and Rails Community influences on coding styles Real-world project examples and refactoring approaches Deployment and dev ops differences Popularity and adoption curves of both frameworks Ongoing research into improving Phoenix and Rails Links Mentioned in this Episode: SmartLogic.io (https://smartlogic.io/) Dan's LinkedIn (https://www.linkedin.com/in/divovich/) Owen's LinkedIn (https://www.linkedin.com/in/owen-bickford-8b6b1523a/) Ruby https://www.ruby-lang.org/en/ Rails https://rubyonrails.org/ Sams Teach Yourself Ruby in 21 Days (https://www.overdrive.com/media/56304/sams-teach-yourself-ruby-in-21-days) Learn Ruby in 7 Days (https://www.thriftbooks.com/w/learn-ruby-in-7-days---color-print---ruby-tutorial-for-guaranteed-quick-learning-ruby-guide-with-many-practical-examples-this-ruby-programming-book--to-build-real-life-software-projects/18539364/#edition=19727339&idiq=25678249) Build Your Own Ruby on Rails Web Applications (https://www.thriftbooks.com/w/build-your-own-ruby-on-rails-web-applications_patrick-lenz/725256/item/2315989/?utm_source=google&utm_medium=cpc&utm_campaign=low_vol_backlist_standard_shopping_customer_acquisition&utm_adgroup=&utm_term=&utm_content=593118743925&gad_source=1&gclid=CjwKCAiA1MCrBhAoEiwAC2d64aQyFawuU3znN0VFgGyjR0I-0vrXlseIvht0QPOqx4DjKjdpgjCMZhoC6PcQAvD_BwE#idiq=2315989&edition=3380836) Django https://github.com/django Sidekiq https://github.com/sidekiq Kafka https://kafka.apache.org/ Phoenix Framework https://www.phoenixframework.org/ Phoenix LiveView https://hexdocs.pm/phoenixliveview/Phoenix.LiveView.html#content Flask https://flask.palletsprojects.com/en/3.0.x/ WebSockets API https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API WebSocket connection for Phoenix https://github.com/phoenixframework/websock Morph Dom https://github.com/patrick-steele-idem/morphdom Turbolinks https://github.com/turbolinks Ecto https://github.com/elixir-ecto Capybara Testing Framework https://teamcapybara.github.io/capybara/ Wallaby Testing Framework https://wallabyjs.com/ Cucumber Testing Framework https://cucumber.io/ RSpec https://rspec.info/
This episode came together at ~4 hrs notice since Dylan had just landed in SF and we had to setup quickly; you might notice some small audio issues in some segments, we apologize. We're currently building our own podcast studio for 2024!
Two software engineers come together to discuss all the aspects of solving problems at the hardware software interface. Our firmware intern Jacob Little joins us from North Carolina State University, and speaks to one of Ampere's technical leaders, Kevin Smith. Kevin is the Vice President of Languages and Compilers. Topics in this episode include working across organizations, how to up-level your communications, explaining concepts to audiences both technical and non-technical, and uplifting our peers!
Can you decipher the jargon of cybersecurity and ace the CISSP exam? Get ready to take notes as host Sean Gerber, a maestro of cybersecurity, breaks down the baffling world of libraries, ides, compilers, and object-oriented programming. With an emphasis on mastering the CISSP exam, Sean meticulously dissects complex concepts and questions, focusing on domain 8.1, and delivers a comprehensive understanding of the management thought process behind it.This week, we're peeling back the layers of cybersecurity! Sean expertly navigates topics such as inheritance in object-oriented programming, the cardinal role of redundancy in avoiding system failures, and the significance of assurance levels. Delve into the intricate world of secure authentication and session management for web applications, and discover what critical elements to prioritize. Plus, learn the ins and outs of error handling, and how polymorphism, cohesion, and coupling are vital in object-oriented application development. This episode is a must-listen if you're preparing for the CISSP exam or looking to expand your cybersecurity knowledge!Gain access to 30 FREE CISSP Exam Questions each and every month by going to FreeCISSPQuestions.com and sign-up to join the team for Free.
Ready to level up your cybersecurity knowledge and coding prowess? We promise to elevate your understanding of CISSP development and libraries, as we venture into the world of code collections. Get a firm grip on the different types of libraries, from standard to custom, and learn about the potential dangers associated with cryptographic libraries. We also delve into the intriguing world of language-specific libraries and the pivotal role of packaging in the development realm.We then shift gears towards the dynamic field of development tools. From the nitty-gritty of integrated development environments to the intricacies of chat GPTs, we discuss their pros and cons, and the significance of understanding the code. Get a closer look at compilers and version control systems, your crucial allies for translating and tracking changes in source code. Finally, we tackle the key concepts of Object-Oriented Programming (OOP), their practical implications in cybersecurity, and the power of encryption algorithms. So buckle up and prepare to enter a world of code, cybersecurity, and essential development tools.Gain access to 30 FREE CISSP Exam Questions each and every month by going to FreeCISSPQuestions.com and sign-up to join the team for Free.
Richard talks to Futhark language co-creator Troels Henriksen about how to design compilers for faster performance.
Grace Hopper war schon als Kind von der Funktionsweise von Maschinen fasziniert. Während des Zweiten Weltkriegs trat sie der US Navy bei, wo sie an den Anfängen der Computertechnologie arbeitete, genauer gesagt als eine der ersten Programmiererinnen des Harvard Mark I, eines der ersten Großrechner. Doch ihre eigentliche Pionierleistung kam später mit der Entwicklung des ersten Compilers - ein innovatives Tool, das menschliche Sprache in Maschinencode übersetzte und den Weg für moderne Programmiersprachen ebnete. "Historische Heldinnen" lässt mithilfe von Künstlicher Intelligenz wichtige Frauen der Weltgeschichte auf ihr eigenes Leben zurückblicken. Selbstbewusst erzählen sie uns von ihrem Mut und ihrer Durchsetzungskraft. Viertausendhertz 2023
Welcome to episode two of our limited series on compilers! In this episode, our host James Tang talks COBOL Java interoperability with Joran Siu and David Tremaine.
The Future of computer chip design: delve into a revolutionary approach to chip design. A re-run of a conversation Russ had in 2021 with Priyanka Raina, an assistant professor of electrical engineering. Priya is an expert in computer chip design. Whether or not you realize it, chips are everywhere and power everything from your toaster to your car. Priya discusses the slowing pace of progress in improving chip efficiency, and how she sees a future where chip makers will need to shift away from general-purpose computer chips to task-specific chips.Chapter Time Stamps:(00:00:00) IntroductionHost Russ Altman introduces the episode and the guest, Professor Priyanka Raina, an expert in electrical engineering.(00:01:15) The Traditional Chip Design ParadigmExplore the traditional chip design process and its challenges, including long development times and limitations in reusability.(00:04:28) The Role of Specialized ChipsUnderstand the emergence of specialized chips and how they target specific applications for improved performance.(00:07:56) The Promise of Core-Grain Reconfigurable Arrays (CGRAs)Learn about core-grain reconfigurable arrays and how they bridge the gap between specialization and adaptability.(00:10:12) Balancing Flexibility and SpecializationDiscover the concept of specialized compute units within CGRAs and how they can be tailored to various applications.(00:13:25) Agile Hardware DesignExplore the concept of agile hardware design and how it enables faster chip development iterations.(00:16:40) Overcoming Hardware and Software ChallengesUnderstand the challenges of combining adaptable hardware with rapidly changing software and applications.(00:19:02) The Role of Compilers in Chip DesignExplore the significance of compilers in translating high-level programming into efficient hardware instructions.(00:21:30) Adapting Compilers for CGRAsDiscover how compilers are adapted to work seamlessly with core-grain reconfigurable arrays, enabling automatic updates as hardware changes.(00:23:40) Benefits of Agile Chip DevelopmentLearn about the potential benefits of agile chip development, including reduced time-to-market and adaptability to evolving applications.(00:26:15) Revolutionizing Chip Development with CGRAsDiscuss how CGRAs can reshape the landscape of chip design, offering a new approach to balancing specialization and adaptability.
Our guest this week is Rick Rieder. This is Rick's second appearance on The Long View. We last interviewed him in May 2020, and we are happy to welcome him back. Rick is BlackRock's chief investment officer of Global Fixed Income, head of the Fundamental Fixed Income Business, and head of the Global Allocation Investment Team. Rick also is a member of the firm's Global Executive Committee, its Investment Subcommittee, and is chairman of the firmwide BlackRock Investment Council. In addition to these duties, Rick manages numerous multi-asset and fixed-income strategies, including BlackRock Global Allocation Fund and a new active exchange-traded fund that the firm recently launched called BlackRock Flexible Income ETF. BackgroundBio“Rick Rieder: Nobody Has Ever Seen Anything Like This,” The Long View podcast, Morningtar.com, May 20, 2020.BlackRock Flexible Income ETF BINCDispersion and Liquidity“Investors Rediscover the Importance of Getting Paid Back,” by Rick Rieder, blackrock.com, June 21, 2023.“BlackRock's Rieder: Grab High Yields on Super-Safe Bonds While You Can,” by Tom Lauricella, Morningstar.com, May 18, 2023.The Economy and Inflation“BlackRock Bond Chief Rieder Says U.S. Economy in ‘Much Better Shape' Than Doomsayers Say,” by Hugh Son, cnbc.com, May 23, 2023.“The Polyurethane Economy: Flexible and Adaptable,” by Rick Rieder, blackrock.com, Feb. 22, 2023.“5 Reasons to Call an Investment ‘Time-Out,'” by Rick Rieder, blackrock.com, March 31, 2023.“The New Inflation Regime,” blackrock.com.“Fed Chair Powell May Lean Hawkish on Inflation, but Stocks Have ‘Tremendous' Technical Backdrop, Says BlackRock's Rick Rieder,” by Christine Idzelis, marketwatch.com, July 26, 2023.Consumer Spending and Allocation“Investing in a Changing World: From Carburetors to Compilers,” by Rick Rieder, blackrock.com, Aug. 10, 2023.“July Jobs Report Shows the Post-Pandemic Labor Market Is Over,” by Myles Udland, finance.yahoo.com, Aug. 4, 2023.“Rotation to Duration: Seeking a More Resilient Portfolio,” by Rick Rieder, blackrock.com, Aug. 1, 2023.BlackRock Global Allocation Fund MALOX
C-Lo joins Al on a Summer Friday to discuss Yankees pitching moves, the Giants and Jets' preseason games, and Mark Sanchez at Jets camp. To learn more about listener data and our privacy practices visit: https://www.audacyinc.com/privacy-policy Learn more about your ad choices. Visit https://podcastchoices.com/adchoices
It's the Season 10 finale of the Elixir Wizards podcast! José Valim, Guillaume Duboc, and Giuseppe Castagna join Wizards Owen Bickford and Dan Ivovich to dive into the prospect of types in the Elixir programming language! They break down their research on set-theoretical typing and highlight their goal of creating a type system that supports as many Elixir idioms as possible while balancing simplicity and pragmatism. José, Guillaume, and Giuseppe talk about what initially sparked this project, the challenges in bringing types to Elixir, and the benefits that the Elixir community can expect from this exciting work. Guillaume's formalization and Giuseppe's "cutting-edge research" balance José's pragmatism and "Guardian of Orthodoxy" role. Decades of theory meet the needs of a living language, with open challenges like multi-process typing ahead. They come together with a shared joy of problem-solving that will accelerate Elixir's continued growth. Key Topics Discussed in this Episode: Adding type safety to Elixir through set theoretical typing How the team chose a type system that supports as many Elixir idioms as possible Balancing simplicity and pragmatism in type system design Addressing challenges like typing maps, pattern matching, and guards The tradeoffs between Dialyzer and making types part of the core language Advantages of typing for catching bugs, documentation, and tooling The differences between typing in the Gleam programming language vs. Elixir The possibility of type inference in a set-theoretic type system The history and development of set-theoretic types over 20 years Gradual typing techniques for integrating typed and untyped code How José and Giuseppe initially connected through research papers Using types as a form of "mechanized documentation" The risks and tradeoffs of choosing syntax Cheers to another decade of Elixir! A big thanks to this season's guests and all the listeners! Links and Resources Mentioned in this Episode: Bringing Types to Elixir | Guillaume Duboc & Giuseppe Castagna | ElixirConf EU 2023 (https://youtu.be/gJJH7a2J9O8) Keynote: Celebrating the 10 Years of Elixir | José Valim | ElixirConf EU 2022 (https://youtu.be/Jf5Hsa1KOc8) OCaml industrial-strength functional programming https://ocaml.org/ ℂDuce: a language for transformation of XML documents http://www.cduce.org/ Ballerina coding language https://ballerina.io/ Luau coding language https://luau-lang.org/ Gleam type language https://gleam.run/ "The Design Principles of the Elixir Type System" (https://www.irif.fr/_media/users/gduboc/elixir-types.pdf) by G. Castagna, G. Duboc, and J. Valim "A Gradual Type System for Elixir" (https://dlnext.acm.org/doi/abs/10.1145/3427081.3427084) by M. Cassola, A. Talagorria, A. Pardo, and M. Viera "Programming with union, intersection, and negation types" (https://www.irif.fr/~gc/papers/set-theoretic-types-2022.pdf), by Giuseppe Castagna "Covariance and Contravariance: a fresh look at an old issue (a primer in advanced type systems for learning functional programmers)" (https://www.irif.fr/~gc/papers/covcon-again.pdf) by Giuseppe Castagna "A reckless introduction to Hindley-Milner type inference" (https://www.lesswrong.com/posts/vTS8K4NBSi9iyCrPo/a-reckless-introduction-to-hindley-milner-type-inference) Special Guests: Giuseppe Castagna, Guillaume Duboc, and José Valim.
Welcome to our new Compilers series, a new short-run of episodes dedicated to how compilers fit in the DevOps space. Kicking off the series is Roland Koo, an authority on compilers within IBM.
With Bjarne Stroustrup, Frances Buontempo, Gianluca Delfino, Vladimír Arnošt, Andrew Fodiman and other colleagues.Notes: https://cppclub.uk/meetings/2023/161/Video: https://youtu.be/WAhBuIhaDLM
Théophile Kalumbu comes by to talk about how Elm makes developing a frontend fun, building a design system explorer, iterating quickly, and getting Elm to production.Thanks to our sponsor, Logistically. Email: elmtown@logisticallyinc.com.Music by Jesse Moore.Recording date: 2023.03.06GuestThéophile Kalumbu (@kalu_theo)Show notes[00:00:56] Some of Théophile's contributions to Elmkalutheo/ elm-ui-explorerTalk "Building a Design System with Elm" at Elm Europe 2019Recently talked about Elm on the French podcast "If This Then Dev"[00:02:35] Finding passion in programming through Nintendo games[00:09:20] Learning functional programming through React, then Elmlodash/fp[00:11:34] Elm stands apart to make developing a frontend funElm documentation requirements[00:13:29] "Why don't you do it in Elm?"To the Elm audience member at the Elm meetup in Paris who encouraged Théophile to make Elm UI Explorer, if you're listening, please contact Jared (elmtown@jaredmsmith.com) or Théophile (kalutheo@hotmail.com or on Twitter @kalu_theo) to say "Hi".[00:18:10] Don't be afraid to start small"Compilers as Assistants" by Evan Czaplicki"Incremental Type-Driven Development" by Dillon Kearns at Elm Europe 2019dmy/elm-doc-preview[00:26:48] Getting Elm to production at Veepee[00:32:26] Elm as a double-edged sword of reliabilityDillon Kearns' elm-graphql[00:39:48] How Elm has changed the way Théophile writes software in general[00:44:33] PicksThéophile's picksDomain Modeling Made Functional by Scott WlaschinRichard Feldman's elm-cssRichard's Frontend Masters coursesIntroduction to Elm, v2Advanced ElmGeorges Boris' elm-bookJared's picksLuca Mugnaini's Elm 2022, a year in reviewMatthew Griffith's elm-uiThanks, everyone, for coming to Elm Town! If you're enjoying the show, please share it with friends and like/rate it on your podcast platform.
On this episode of Remote Ruby, Jason and Andrew are here, and they are thrilled to have with them, Takashi Kokubun, a Staff Developer at Shopify. He's here to talk about JIT (just-in-time) compilers in Ruby and why we would want to use one in Ruby. We'll hear about his work on YJIT and RJIT, the differences between YJIT and MJIT, and how the primary focus is to make YJIT the best JIT compiler for real-world Ruby apps. There's a conversation about the use of Rust in JIT compiler development for Ruby, and Takashi shares some benefits to using Rust, as well some challenges. Also, there's some exciting upcoming improvements in YJIT, we find out why HAML is Takashi's preferred template language, and he tells us about Hamlit, the template engine he authored and maintains. Hit download to hear much more! [00:01:54] Since Takashi worked on the original MJIT, he tells us what a JIT compiler is and why we would want to use one in Ruby.[00:06:41] Takashi talks about working on the original MJIT (Ruby 2.6). [00:11:15] Jason wonders what kind of performance gains Takashi saw on average in Ruby 2.6 using MJIT in production. He explains that it was designed to optimize specific benchmarks such as Optcarrot but was not efficient for general purpose applications like Rails. [00:12:49] We find out why MJIT was slower on Rails which has to do with it using a sync compiler. [00:14:41] What kind of improvements were there in running Optcarrot with MJIT?[00:16:41] Takashi shares why he joined in Shopify and what he did with YJIT.[00:20:34] We hear some differences that YJIT has taken from MJIT. For example, YJIT is a JIT compiler that generates machine code directly, making it more efficient and faster than MJIT, which uses a C compiler. Also, he explains the architecture being very different between MJIT and YJIT. [00:24:52] We learn some performance benefits using YJIT.[00:26:19] Let's listen to Takashi talk about his work on RJIT, and he touches on John Hawthorn and Aaron Patterson's compilers, hawthjit and TenderJit. [00:31:23] Takashi talks about the primary focus to make YJIT the best JIT compiler for real world Ruby apps. [00:34:20] Takashi shares his mixed feelings with Rust, as well as the challenges. [00:39:29] There's some exciting improvements coming up in the JIT world! [00:42:33] Andrew wonders if ERB gets any benefit to the stuff happening in YJIT.[00:43:14] HAML is Takashi's preferred template language, and he tells us about a HAML package he authored and maintains called, Hamlit. [00:44:42] Takashi maintains many libraries, he works on YJIT at Shopify, and writes assembly code. How does he have time for all this? [00:45:46] Find out where you can follow Takashi online.Panelists:Jason CharnesAndrew MasonGuest:Takashi KokubunSponsor:HoneybadgerLinks:Jason Charnes TwitterChris Oliver TwitterAndrew Mason TwitterTakashi Kokubun TwitterTakashi Kokubun GitHubOptcarrot yjit-benchTenderJIThawthjitHamlitRuby Radar TwitterRuby for All Podcast
Thorsten Ball is a Staff Engineer at Sourcegraph and also the author of two self-published books. He currently focuses on assisting development teams within the company and correcting scaling issues for large clients. In this episode, he takes us through his journey from growing up in small town Germany to starting a band in Berlin and finally ending up as a Staff Engineer. 00:00 Introduction 05:30 Journey Begins 07:30 First memory of a computer13:00 Technology in the family 19:00 Interests growing up 21:30 Thoughts after high school 25:40 Living in Australia36:50 Getting into programming as a career43:20 Leaving UPS59:00 Moving closer to home 1:07:25 Finding Sourcegraph1:09:30 Discovering Golang1:20:10 Current tasks at Sourcegraph1:30:45 Contact Information Connect with Thorsten: Website: https://thorstenball.comMentioned in today's episode:Sourcegraph: https://sourcegraph.com/searchGolang: https://go.dev Want more from Ardan Labs? You can learn Go, Kubernetes, Docker & more through our video training, live events, or through our blog!Online Courses: https://ardanlabs.com/education/ Live Events: https://www.ardanlabs.com/live-training-events/ Blog: https://www.ardanlabs.com/blog Github: https://github.com/ardanlabs
Mark Jackson, senior quantum evangelist at Quantinuum is interviewed by Yuval Boger. Mark and Yuval talk about optimizing compilers, quantum error correction news, whether customers prefer shrink-wrapped quantum software, and much more.
In this episode, we talk with a vyper contributor and compiler expert who pseudonymously goes by @big_tech_sux on Twitter. Bts knows a lot about programming languages, and we go deep into vyper in this episode. We discuss things like vyper's evolution, standardized intermediate representations for web3 compilers, and titanoboa - a new contribution to the vyper development toolchain which is dramatically improving UX.BTS on twitter: https://twitter.com/big_tech_suxVyper: https://vyper.readthedocs.io/en/stable/Titanoboa: https://github.com/vyperlang/titanoboaShow Notes:00:00 Intro2:15 How BTS got into the space4:13 Vyper's evolution7:24 Standardized intermediate representations for EVM languages15:47 How will the web3 language space evolve?20:10 Vyper's design decisions over time37:01 Titanoboa & its features 50:31 Why the name Big Tech Sux?52:02 BTS' long term vision for the space
Hyperfiddle is an app builder in Clojure/Clojurescript that uses a compiler to manage the network connections in the app for you. We discuss what makes code easy vs simple, arches for software, home-cooked apps, and the implications of a compiler for everything.Links/Resources:- [https://www.hyperfiddle.net/](https://www.hyperfiddle.net/)- [https://hyperfiddle.notion.site/Reactive-Clojure-You-don-t-need-a-web-framework-you-need-a-web-language-44b5bfa526be4af282863f34fa1cfffc](https://www.notion.so/Reactive-Clojure-You-don-t-need-a-web-framework-you-need-a-web-language-44b5bfa526be4af282863f34fa1cfffc)- [https://www.hytradboi.com/2022/uis-are-streaming-dags](https://www.hytradboi.com/2022/uis-are-streaming-dags) - [https://hyperfiddle.notion.site/UIs-are-streaming-DAGs-e181461681a8452bb9c7a9f10f507991](https://www.notion.so/UIs-are-streaming-DAGs-e181461681a8452bb9c7a9f10f507991)- How hyperfiddle changed over time - [https://web.archive.org/web/20180217034740/http://www.hyperfiddle.net/](https://web.archive.org/web/20180217034740/http://www.hyperfiddle.net/)- First video proof of Hyperfiddle's "distributed dataflow" architecture for server-streamed UI. "UI as an Expression” [https://twitter.com/dustingetz/status/1474050461745528839](https://twitter.com/dustingetz/status/1474050461745528839)- [https://github.com/hyperfiddle/hyperfiddle-2020](https://github.com/hyperfiddle/hyperfiddle-2020)- [https://www.youtube.com/watch?v=6888V9YsObM](https://www.youtube.com/watch?v=6888V9YsObM)Show Notes:- Have you tried rubbing a database on it? https://www.hytradboi.com/- Self-adjusting Computations https://www.youtube.com/watch?v=G6a5G5i4gQU- Sloth ecosystems https://www.youtube.com/watch?v=VU9Tn_Qkjb8- Simple Made Easy https://www.youtube.com/watch?v=SxdOUGdseq4- Apps can be home-cooked meals https://www.robinsloan.com/notes/home-cooked-app/- Bundling and Unbundling https://reallifemag.com/bundling-and-unbundling/- Alan Kays: STEPS http://www.vpri.org/pdf/tr2012001_steps.pdf and the Niles Compiler https://github.com/damelang/nile https://raw.githubusercontent.com/wiki/damelang/nile/socal.pdfChapters:0:00 Intros[00:02:05] What is Hyperfiddle?[00:08:53] Managed Network through a Compiler[00:15:49] Arches for Software[00:19:21] Beyond Low Code[00:26:39] Abstractions: Simple vs Easy[00:29:14] Core of what's hard about apps[00:33:16] The Eight Fallacies[00:34:54] Home-cooked apps[00:40:28] The Piped Piper Dream[00:45:57] Reports for everyone![00:51:35] A compiler to help manage state?[00:55:12] A Compiler for the Metaverse [01:01:44] Making Integration Smoother[01:04:38] OG "bare metal"[01:12:01] Hypertext as Application State[01:20:03] Compilers do hard things all the time===== About “The Technium” ===== The Technium is a weekly podcast discussing the edge of technology and what we can build with it. Each week, Sri and Wil introduce a big idea in the future of computing and extrapolate the effect it will have on the world. Follow us for new videos every week on web3, cryptocurrency, programming languages, machine learning, artificial intelligence, and more!===== Socials =====WEBSITE: [https://technium.transistor.fm/](https://technium.transistor.fm/)SPOTIFY: [https://open.spotify.com/show/1ljTFMgTeRQJ69KRWAkBy7](https://open.spotify.com/show/1ljTFMgTeRQJ69KRWAkBy7)APPLE PODCASTS: [https://podcasts.apple.com/us/podcast/the-technium/id1608747545](https://podcasts.apple.com/us/podcast/the-technium/id1608747545)
FEATURED VOICES IN THIS EPISODEDan GuidoDan Guido is the CEO of Trail of Bits, a cybersecurity firm he founded in 2012 to address software security challenges with cutting-edge research. In his tenure leading Trail of Bits, Dan has grown the team to 80 engineers, led the team to compete in the DARPA Cyber Grand Challenge, built an industry-leading blockchain security practice, and refined open-source tools for the endpoint security market. In addition to his work at Trail of Bits, he's active on the boards of four early-stage technology companies. Dan contributes to cybersecurity policy papers from RAND, CNAS, and Harvard. He runs Empire Hacking, a 1,500-member meetup group focused on NYC-area cybersecurity professionals. His latest hobby coding project -- AlgoVPN -- is the Internet's most recommended self-hosted VPN. In prior roles, Dan taught a capstone course on software exploitation at NYU as a faculty member and the Hacker in Residence, consulted at iSEC Partners (now NCC Group), and worked as an incident responder for the Federal Reserve System.Nat ChinNat Chin is a security engineer 2 at Trail of Bits, where she performs security reviews of blockchain projects, and develops tools that are useful when working with Ethereum. She is the author of solc-select, a tool to help switch Solidity versions. She worked as a smart contract developer and taught as a Blockchain Professor at George Brown College, before transitioning to blockchain security when she joined Trail of Bits.Opal WrightOpal Wright is a cryptography analyst at Trail of Bits. Two of the following three statements about her are true: (a) she's a long-distance unicyclist; (b) she invented a public-key cryptosystem; (c) she designed and built an award-winning sex toy.Jim MillerJim Miller is the cryptography team lead at Trail of Bits. Before joining Trail of Bits, Jim attended graduate programs at both Cambridge and Yale, where he studied and researched both Number Theory and Cryptography, focusing on topics such as lattice-based cryptography and zero-knowledge proofs. During his time at Trail of Bits, Jim has led several security reviews across a wide variety of cryptographic applications and has helped lead the development of multiple projects, such as ZKDocs and PrivacyRaven.Josselin FeistJosselin Feist is a principal security engineer at Trail of Bits where he participates in assessments of blockchain software and designs automated bug-finding tools for smart contracts. He holds a Ph.D. in static analysis and symbolic execution and regularly speaks at both academic and industrial conferences. He is the author of various security tools, including Slither - a static analyzer framework for Ethereum smart contracts and Tealer - a static analyzer for Algorand contracts.Peter GoodmanPeter Goodman is a Staff Engineer in the Research and Engineering practice at Trail of Bits, where he leads all de/compilation efforts. He is the creator of various static and dynamic program analysis tools, ranging from the Remill library for lifting machine code into LLVM bitcode, to the GRR snapshot/record/replay-based fuzzer. When Peter isn't writing code, he's mentoring a fleet of interns to push the envelope. Peter holds a Master's in Computer Science from the University of Toronto.Host: Nick SelbyAn accomplished information and physical security professional, Nick leads the Software Assurance practice at Trail of Bits, giving customers at some of the world's most targeted companies a comprehensive understanding of their security landscape. He is the creator of the Trail of Bits podcast, and does everything from writing scripts to conducting interviews to audio engineering to Foley (e.g. biting into pickles). Prior to Trail of Bits, Nick was Director of Cyber Intelligence and Investigations at the NYPD; the CSO of a blockchain startup; and VP of Operations at an industry analysis firm.Production StaffStory Editor: Chris JulinAssociate Editor: Emily HaavikExecutive Producer: Nick SelbyExecutive Producer: Dan GuidoRecordingRocky Hill Studios, Ghent, New York. Nick Selby, EngineerPreuss-Projekt Tonstudio, Salzburg, Austria. Christian Höll, EngineerRemote recordings:Whistler, BC, Canada; (Nick Selby) Queens, NY; Brooklyn, NY; Rochester, NY (Emily Haavik);Toronto, ON, Canada. TAPES//TYPES, Russell W. Gragg, EngineerTrail of Bits supports and adheres to the Tape Syncers United Fair Rates CardEdited by Emily Haavik and Chris JulinMastered by Chris JulinMusicDISPATCHES FROM TECHNOLOGY'S FUTURE, THE TRAIL OF BITS THEME, Chris JulinOPEN WINGS, Liron MeyuhasNEW WORLD, Ian PostFUNKYMANIA, Omri Smadar, The Original OrchestraGOOD AS GONE, INSTRUMENTAL VERSION, Bunker Buster ALL IN YOUR STRIDE, AbeBREATHE EASY, Omri SmadarTREEHOUSE, LingerwellLIKE THAT, Tobias BergsonSCAPES, Gray NorthReproductionWith the exception of any Copyrighted music herein, Trail of Bits Season 1 Episode 0; Immutable © 2022 by Trail of Bits is licensed under Attribution-NonCommercial-NoDerivatives 4.0 International. This license allows reuse: reusers may copy and distribute the material in any medium or format in unadapted form and for noncommercial purposes only (noncommercial means not primarily intended for or directed towards commercial advantage or monetary compensation), provided that reusers give credit to Trail of Bits as the creator. No derivatives or adaptations of this work are permitted. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-nd/4.0/.Meet the Team:CHRIS JULINChris Julin has spent years telling audio stories and helping other people tell theirs. These days he works as a story editor and producer for news outlets like APM Reports, West Virginia Public Broadcasting, and Marketplace. He has also taught and mentored hundreds of young journalists as a professor. For the Trail of Bits podcast, he serves as story and music editor, sound designer, and mixing and mastering engineer.EMILY HAAVIKFor the past 10 years Emily Haavik has worked as a broadcast journalist in radio, television, and digital media. She's spent time writing, reporting, covering courts, producing investigative podcasts, and serving as an editorial manager. She now works as an audio producer for several production shops including Us & Them from West Virginia Public Broadcasting and PRX, and APM Reports. For the Trail of Bits podcast, she helps with scripting, interviews, story concepts, and audio production.
Jordan Poole with THE highlight of Game 2, with a perfectly launched rainbow three at the 3Q buzzer. Too bad Mike Breen was still in Covid Jail! Czabe is joined by AL GALDI to discuss the current "state of the NBA art" along with the Draymond Green double standard. Christian Yelich is lost. Can he find his way back? What stats matter in MLB? How about the NFL? College baseball as an under-leveraged sports property? Compilers. "Crazy don't get tired." MORE.....Advertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacy
By several measures, including a 2021 survey by IEEE, Python is the most popular programming language in the world. But why? What's special about it? In this episode we'll go over Python's history, key technical aspects of the language, and the niches within software development that it dominates. We also discuss some problems in the Python world. Show Notes Episode 11: What is a Programming Language? Episode 87: Compilers and Interpreters Episode 35: The C Programming Language Top Programming Languages 2021 via IEEE Follow us on Twitter @KopecExplains. Theme “Place on Fire” Copyright 2019 Creo, CC BY 4.0 Find out more at http://kopec.live
Hey folks,Apologies for 2 weeks of missing podcasts. The episode 2 weeks ago was all coding and didn't make much sense to just do the audio for. And last week I was busy redoing my recording studio cabling and equipment.In this episode I talk about compilers: a bit about how they work, and a lot about how useful they have been at various points in my career. They are a fun subject and it was an easy episode to record!I mentioned a book, The Essentials of Programming Languages. It's the one by Friedman, Wand et al. I reaaally enjoyed working through this book, although I did study Scheme in other books first.I also mentioned the bare-bones user manual for my Wyvern game's autobag minilanguage: It's at https://ghosttrack.com/autobag if you want to have a look.I hope this episode was interesting. It's a challenging topic to talk about at a high level without getting bogged down in the details. I did a lot of editing in this episode, but it may have needed more. Let me know!
It's about time we asked a question about compilers. It's been a scary proposition. Compilers have a reputation for density, complexity, and a fair bit of mysticism. But when we looked into them, we learned they're really just like any other program. So we wondered: Who's afraid of compilers? In this episode of Compiler, we start to break down the reputation by opening up the black box. What do compilers do? How do they work? And what can you gain by learning more about the inner workings of compilers?
A compiler is a program that takes source code written in a programming language and converts it into machine code that a microprocessor can understand. Compilers are sophisticated programs composed of several different phases including (but not limited to) tokenization, parsing, and machine code generation. In this episode we breakdown why compilers are important, how they work, and how they differ from interpreters. We also explain tangential topics like just-in-time compilers and transpilers. Ultimately compilers and interpreters often have to deal with several trade offs. After listening to this episode, you will better understand those tradeoffs and why one compiler will differ from another. Show Notes Episode 35: The C Programming Language Crafting Interpreters via Amazon The Dragon Book via Amazon Ukraine Humanitarian Organizations via Readdle Follow us on Twitter @KopecExplains. Theme “Place on Fire” Copyright 2019 Creo, CC BY 4.0 Find out more at http://kopec.live
Oxide and Friends Twitter Space: January 3rd, 2022Predictions 2022We've been holding a Twitter Space weekly on Mondays at 5p for about an hour. Even though it's not (yet?) a feature of Twitter Spaces, we have been recording them all; here is the recording for our Twitter Space for January 3rd, 2022.In addition to Bryan Cantrill and Adam Leventhal, our special guest on January 3rd included was tech prediction expert and noted Red Sox fan Steven O'Grady.Below is a table of the oracles and their predictions: (If you made predictions, please submit a PR to add or clarify yours) Futurist 1 year 3 year 6 year | @openlabbott 47:15 | Discord are going to annoy their userbase. | We'll finally get a RISC V server in a datacenter, in some shape or form. | Email goes the way of the landline. | @MattSci2 1:10:05 | The framework laptop company will be unsuccessful. Existing laptops are not substantially different; with some retooling. | One major FPGA vendor will have a completely open toolchain for high end FPGAs. | At least 1 RISC-V supercomputer in the Top 500. | @tomk_ 1:16:45 | At least one of the hyperscalers will become startlingly good at partnering. | Stablecoins will become regulated. | The biggest datacenter server provider (outside the hyperscalers) will be a company that hasn't yet shipped its first server. | @tinco 1:18:57 | Multiple companies will have demonstrated a AGI (one shot machine learning system). It's not gonna be useful for anything, but I think the problem is less hard than many critics think it is and several companies/organizations are actually going to be showing the first versions of these systems. | Drones autonomously flying around private properties will be a common thing. Factory managers, powerlines inspectors, large building sites etc. will have commonly available and affordable options to inspect or patrol their properties. | Web3 will actually happen, but not in the way it's currently being talked about. In 6 years time bots will have improved to the point that they can not be warded off the major platforms (or any platforms) and will make the web absolutely unusable due to them disrupting all established crowd funded moderation systems. A new paradigm will have to emerge that fundamentally changes how we use the web (thus web3), so that we can still derive value from it. | Ben Stoltz 1:24:40 | Smart glasses become a viable alternative for computer monitors youtube. People who used to look away from their phones to have their own thoughts, and are now using smart glasses in real life situations, are subjected to an ads vs. attention “Tragedy of the commons”. As costs per unit decrease leading to ubiquity, this forces a modern-day “Highway Beautification Act” to legislate Ad Blocking. | A significant percentage of commercial office space will be converted to housing. | The best AIs have emotional problems. We don't really know how they work. AI specialists are more therapists than programmers. | @kelseyhightower 1:29:30 | This year will be more of the same, competition to define the new normal as the pandemic winds down. | Pandemic-era solutions will backfire; crypto-currencies will give governments an excuse to track all actual spending. “We will give you the transparency, but not the kind you wanted.” | Technology will be recognized as sovereignty like money and land used to be. Governments will be wary of using technology from weak allies or competitors. Local hardware manufacturing, growth of local university training, etc. Possibly manifesting as national protectionism, or a reprise of the space-race. Open source will be the default model. | @orangecms 1:53:45 | a major OS from China emerges | high performance computing from Europe | ARM no longer as relevant | @ahl 1:58:00 | web3 is done; we're not talking about it, it's not a thing, we don't use the term and we only vaguely recall what it was supposed to mean. | Productivity per watt becomes a highly important metric in computing. Tools tell us about our power use. We spin workloads up and down depending on power cost and availability. | AWS offers RISC-V instance types. | @AaronDGoldman 1:07:14 | Single-node computing: people will realize that that distributed computing has a lot of overhead and that one server can do a lot of work. This will lead people to people doing business analytics jobs by pulling all their data to a single a computer and doing the calculation, getting the result 100x faster than splitting data over many computers. | Microservices inlining: taking a lot of microservices and statically linking them together. This will enable calling functions without network overhead, making things run 100x faster. | We will start do scaling properly. Instead of thinking “how can I make this big data and scale up to infinity”, we will try to get the most out of single node. Only once a single node has been pushed to its limit will we scale up to first a rack, then a datacenter, and then the world. | @dancrossnyc 2:01:10 | Major workplace changes due to the pandemic will amplify and accentuate the wealth gap and disparity. Only some industries are privileged enough to be able to work from home. This will create social problems. | Regulation of social media in the aftermath of widespread political unrest, particularly after the US 2024 political season. | The effects of climate change will be sufficiently apparent that people will get serious about retooling around compute and power efficiency. | @iangrunert 56:06 | No one year prediction. | CCPA copycat laws in other states, perhaps US federal legislation, plus changing global regulatory environment lead to GDPR-like protections to no longer be geo-fenced by bigger players. This'll also have impacts on SaaS adoption - spreading data around makes right to amendment and right to deletion harder. | RISC-V chip in mainstream phone (likely Samsung). Previously moving target, but longer upgrade times and slower pace of improvements will cause Samsung to chase RISC-V for high volume phones due to better unit economics. Will have prior experience in RISC-V fab for other applications. | Zach 59:50 | Not much will happen in with tech industry anti-trust. Any bills in progress will be watered down. | Antitrust enforcement will have a chilling effect on acquisitions. | Section 230 of the Communications Decency Act lives. The ARM/NVidia merger will not go through, but it'll will take 5 years to find out. Didn't make it to the Twitter Space, but have a vision of the future? Submit a PR to add your own predictions. Be sure to abide by the rules. Deadline: 2/1/2022 Futurist 1 year 3 year 6 year | @dendibakh Prediction about optimizing compilers | We've reached the point of diminishing returns in existing LLVM optimization passes (
Dr. Brian Callahan Brian is a Lecturer at Rensselaer Polytechnic Institute and an OpenBSD Developer LinkedIn: https://www.linkedin.com/in/brian-robert-callahan-ph-d-707738137/ Notes: https://briancallahan.net/ https://mastodon.com/bcallah@bsdnetwork Brian's interview on BSD Now : https://www.bsdnow.tv/422 Credits: Music by ikson: https://www.iksonmusic.com Special Guest: Brian Callahan.
In today's episode, I talk about compilers and micor-libraries, and how they're helper improve web performance.In today's episode, I talk about compilers and micor-libraries, and how they’re helper improve web performance.Show Notes & Transcript →
In today's episode, I talk about compilers and micor-libraries, and how they're helper improve web performance. Links Preact Preact Performance Preact Rendering Updates AlpineJS Petite Vue SolidJS Rich Harris on client-side JS Svelte SvelteKit Astro Astro Performance Astro Tutorial
Paul Biggar got started as a computer engineer early in life. He became a specialist in the field of compilers (software engineers use compilers to test code to see if it works or not). He liked compilers so much he completed a PhD on the topic. Paul had a few false starts as an entrepreneur, including a stint in the Y-Combinator program, but nothing really took off.Eventually in his late twenties, while working at Mozilla, Paul foresaw that the process of compiling and testing software will move to the cloud. He had the skillset and experience to understand the need, so decided to launch another startup -- and CircleCi.com was born.Paul, along with his co-founder, built the first version of CircleCi, charging a monthly fee for access. They were able to acquire early clients thanks to a strategic investor who introduced them to 20+ companies who needed what CircleCI offered.The Road To A Billion Dollar ValuationDuring the interview Paul said he didn't expect CircleCI to one day crack unicorn status. At the time of this recording, during the most recent round of funding, CircleCI was valued at $1.7 billion dollars.Paul stayed on as CEO all the way up to their A round of funding, raising $6 million at a $20+ million valuation. He left after this, when he realized he was more of a product guy than a CEO who has to focus on culture and hiring.Paul today remains on the board of directors of CircleCI, but is focussed on DarkLang.com, an ambitious project aimed to take out the layers of complexity that software developers have to deal with when coding applications.I appreciate Paul taking the time during the interview to break down some of the more technical aspects of what he has built and what he is still working on. As a technical co-founder, this podcast will especially be of interest because Paul offers his advice on how to succeed as a technical founder.Enjoy the episode.Yaro Podcast: https://www.yaro.blog/pod/Blog: https://www.yaro.blog/
SANS Internet Stormcenter Daily Network/Cyber Security and Information Security Stormcast
Architecture, Compilers and Black Magic https://isc.sans.edu/forums/diary/Architecture+compilers+and+black+magic+or+what+else+affects+the+ability+of+AVs+to+detect+malicious+files/27510/ ALPACA TLS Attack https://alpaca-attack.com/ALPACA.pdf Google Chrome Update https://chromereleases.googleblog.com/2021/06/stable-channel-update-for-desktop.html
Nicolò Ribaudo talks about his life as a math student, learning jQuery before JavaScript, doing oss on the side, his experiences in oss, doing an internship, participating in TC39, and some thoughts after three years of being on the team. (recorded in October). Transcript at https://podcast.babeljs.io/nicoloNicolò: https://twitter.com/NicoloRibaudoHenry: https://twitter.com/left_padSections: Intro This is just applied math Starting in open source Why Babel? What matters now? Open source and Internships Maintenance Boredom
Welcome to the History of Computing Podcast, where we explore the history of information technology. Because understanding the past prepares us for the innovations of the future! Today we're going to look at the Tech Model Railroad Club, an obsessive group of young computer hackers that helped to shape a new vision for the young computer industry through the late 50s and early 60s. We've all seen parodies it in the movies. Queue up a montage. Iron Man just can't help but tinker with new models of his armor. Then viola, these castaway hack jobs are there when a new foe comes along. As is inspiration to finish them. The Lambda Lamda Lamda guys get back at the jock frat boys in Revenge of the Nerds. The driven inventor in Honey I Shrunk the Kids just can't help himself but build the most insane inventions. Peter Venkman in Ghostbusters. There's a drive. And those who need to understand, to comprehend, to make sense of what was non-sensical before. I guess it even goes back to Dr Frankenstein. Some science just isn't meant to be conquered. But trains. Those are meant to be conquered. They're the golden spike into the engineering chasm that young freshman who looked like the cast of Stand By Me, but at MIT, wanted to conquer. You went to MIT in the 50s and 60s because you wanted a deeper understanding of how the world worked. But can you imagine a world where the unofficial motto of the MIT math department was that “there's no such thing as computer science. It's witchcraft!” The Tech Model Railroad Club, or TMRC, had started in 1946. World War II had ended the year before and the first first UN General Assembly and Security Council met, with Iran filing the first complaint against the Soviet Union and UNICEF being created. Syria got their independence from France. Jordan got their independence from Britain. The Philippines gained their independence from the US. Truman enacted the CIA, Stalin accounted a 5 year plan for Russia, ushering in the era of Soviet reconstruction and signaling the beginning of the col war, which would begin the next year. Anti-British protests exploded in India, and Attlee agreed to their independence. Ho Chi Minh became president of the Democratic Republic of Vietnam and France recognized their statehood days later, with war between his forces and the French breaking out later that year resulting in French martial law. Churchill gave his famous Iron Curtain Speech. Italy and Bulgaria abolished their monarchies. The US Supreme Court ordered desegregation of busses and Truman ordered desegregation of the armed forces and created the Committee on Civil Rights using an executive order. And there was no true computer industry. But the ENIAC went into production in 1946. And a group of kids at the Massachusetts Institute of Technology weren't thinking much about the new world order being formed nor about the ENIAC which was being installed just a 5 or 6 hour drive away. They were thinking about model trains. And over the next few years they would build, paint, and make these trains run on model tracks. Started by Walter Marvin and John Fitzallen Moore, who would end up with over a dozen patents after earning his PhD from Columbia and having a long career at Lockheed, EMI Medical who invented the CT scan. By the mid-50s the club had grown and there were a few groups of people who were really in it for different things. Some wanted to drink cocacola while they painted trains. But the thing that drew many a student though was the ARRC, or Automatic Railroad Running Computer. This was built by the Signals and Power Subcommittee who used relays from telephone switches to make the trains do all kinds of crazy things, even cleaning the tracks. Today there we're hacking genes, going to lifehacker.com, and sometimes regrettably getting hacked, or losing data in a breach. But the term came from one who chops or cuts, going back to the 1200s. But on a cool day in 1955, on the third floor of Build 20, known as the Plywood Palace, that would change. Minutes of a meeting at the Tech Model Railroad Club note “Mr. Eccles requests that anyone working or hacking on the electrical system turn the power off to avoid fuse blowing.” Maybe they were chopping parts of train tracks up. Maybe the term was derived from something altogether separate. But this was the beginning of a whole new culture. One that survives and thrives today. Hacking began to mean to do technical things for enjoyment in the club. And those who hacked became hackers. The OG hacker was Jack Dennis, an alumni of the TMRC. Jack Dennis had gotten his bachelors from MIT in 1953 and moved on to get his Masters then Doctorate by 1958, staying until he retired in 1987, teaching and influencing many subsequent generations of young hackers. You see, he studied artificial intelligence, or taking these computers built by companies like IBM to do math, and making them… intelligent. These switches and relays under the table of the model railroad were a lot of logical circuits strung together and in the days before what we think of as computers now, these were just a poor college student's way of building a computer. Having skipped two grades in high school, this “computer” was what drew Alan Kotok to the TMRC in 1958. And incoming freshman Peter Samson. And Bob Saunders, a bit older than the rest. Then grad student Jack Dennis introduced the TMRC to the IBM 704. A marvel of human engineering. It was like your dad's shiny new red 1958 corvette. Way too expensive to touch. But you just couldn't help it. The young hackers didn't know it yet, but Marvin Minsky had shown up to MIT in 1958. John McCarthy was a research fellow there. Jack Dennis got his PhD that year. Outside of MIT, Robert Noyce and Jack Kilby were giving us the Integrated Circuit, we got FORTRAN II, and that McCarthy guy. He gave us LISP. No, he didn't speak with a LISP. He spoke IN LISP. And then president Lyndon Johnson established ARPA in response to Sputnik, to speed up technological progress. Fernando Corbato got his PhD in physics in 1956 and stayed on with the nerds until he retired as well. Kotok ended up writing the first chess program with McCarthy on the IBM 7090 while still a teenager. Everything changed when Lincoln Lab got the TX-0, lovingly referred to as the tikso. Suddenly, they weren't loading cards into batch processing computers. The old IBM way was the enemy. The new machines allowed them to actually program. They wrote calculators and did work for courses. But Dennis kinda' let them do most anything they wanted. So of course we ended up with very early computer games as well, with tic tac toe and Mouse in the Maze. These kids would write anything. Compilers? Sure. Assemblers? Got it. They would hover around the signup sheet for access to the tikso and consume every minute that wasn't being used for official research. At this point, the kids were like the budding laser inventors in Weird Science. They were driven, crazed. And young Peter Deutsch joined them, writing the Lisp 1.5 implementation for the PDP at 12. Can you imagine being a 12 year old and holding your own around a group of some of the most influential people in the computer industry. Bill Gosper got to MIT in 1961 and so did the second PDP-1 ever built. Steve Russell joined the team and ended up working on Spacewar! When he wasn't working on Lisp. Speaking of video games. They made Spacewar during this time with a little help from Kotok Steve Piner, Samson, Suanders, and Dan Edwards. In fact, Kotok and Saunders created the first gamepad, later made popular for Nintendo, so they could play Spacewar without using the keyboard. This was work that would eventually be celebrated by the likes of Rolling Stone and Space War and in fact would later become the software used to smoke test the PDP once it entered into the buying tornado. Ricky Greenblatt got to MIT in 1962. And this unruly, unkempt, and extremely talented group of kids hacked their way through the PDP, with Greenblatt becoming famous for his hacks, hacking away the first FORTRAN compiler for the PDP and spending so much time at the terminal that he didn't make it through his junior year at MIT. These formative years in their lives were consumed with cocacola, Chinese food, and establishing many paradigms we now consider fundamental in computer science. The real shift from a batch process mode of operations, fed by paper tape and punchcards, to a interactive computer was upon us. And they were the pioneers who through countless hours of hacking away, found “the right thing.” Project MAC was established at MIT in 1963 using a DARPA grant and was initially run by legendary J. C. R. Licklider. MAC would influence operating systems with Multics which served as the inspiration for Unix, and the forming of what we now know as computer science through the 1960s and 70s. This represented a higher level of funding and a shift towards the era of development that led to the Internet and many of the standards we still use today. More generations of hackers would follow and continue to push the envelope. But that one special glimpse in time, let's just say if you listen at just the right frequency you can hear screaming at terminals when a game of Spacewar didn't go someone's way, or when something crashed, or with glee when you got “the right thing.” And if you listen hard enough at your next hackathon, you can sometimes hear a Kotok or a Deutsch or a Saunders whisper in your ear exactly what “the right thing” is - but only after sufficient amounts of trial, error, and Spacewar. This free exercise gives way to innovation. That's why Google famously gives employees free time to pursue their passions. That's why companies run hackathons. That's why everyone from DARPA to Netflix has run bounty programs. These young mathematicians, scientists, physicists, and engineers would go on to change the world in their own ways. Uncle John McCarthy would later move to Stanford, where he started the Stanford Artificial Intelligence Laboratory. From there he influenced Sun Microsystems (the S in Sun is for Stanford), Cisco, and dozens of other Silicon Valley powerhouses. Dennis would go on to found Multics and be an inspiration for Ken Thompson with the first versions of Unix. And after retiring he would go to NASA and then Acorn Networks. Slug Russell would go on to a long career as a developer and then executive, including a stop mentoring two nerdy high school kids at Lakeside School in Seattle. They were Paul Allen and Bill Gates, who would go on to found Microsoft. Alan Kotok would go on to join DEC where he would work for 30 years, influencing much of the computing through the 70s and into the 80s. He would work on the Titan chip at DEC and in the various consortiums around the emergent Internet. He would be a founding member of the World Wide Web Consortium. Ricky Greenblatt ended up spending too much of his time hacking. He would go on to found Lisp Machines, coauthor the time sharing software for the PDP-6 and PDP-10, write Maclisp, and write the first computer chess program to beat world class players in Hubert Dreyfus. Peter Samson wrote the Tech Model Railroad Club's official dictionary which would evolve into the now-famous Jargon file. He wrote the Harmony compiler, a FORTRAN compiler for the PDP-6, made music for the first time with computers, became an architect at DEC, would oversee hardware engineering at NASA, and continues to act as a docent at the Computer History Museum. Bob Saunders would go on to be a professor at the University of California, becoming president of the IEEE, and Chairman of the Board during some of the most influential years in that great body of engineers and scientists. Peter Deutsch would go on to get his PhD from Berkeley, found Aladdin Enterprises, write Ghostscript, create free Postscript and PDF alternatives, work on Smalltalk, work at Sun, be an influential mind at Xerox PARC, and is now a composer. We owe a great deal to them. So thank you to these pioneers. And thank you, listeners, for sticking through to the end of this episode of the History of Computing Podcast. We're lucky to have you.
Welcome to the History of Computing Podcast, where we explore the history of information technology. Because by understanding the past, we're able to be prepared for the innovations of the future! Today's episode is on one of the finest minds in the history of computing: Grace Brewster Murray Hopper. Rear Admiral Hopper was born on December 9th, 1906 in New York City. She would go on to graduate from Vassar College in 1928, earn a master's degree at Yale in 1930, and then a PhD from Yale in 1933, teaching at Vassar from 1931 until 1941. And her story might have ended there. But then World War Two happened. Her great-grandfather was an admiral in the US Navy during the Civil War, and so Grace Hopper would try to enlist. But she was too old and a little too skinny. And she was, well, a she. So instead she went on to join the women's branch of the United States Naval Reserve called WAVES, or Women Accepted for Volunteer Emergency Service, at the time. She graduated first in her class and was assigned to the Bureau of Ships project at Harvard as a Lieutenant where she was one of the original programmers of the IBM Automatic Sequence Controlled Calculator, better known as the Mark I. The Mark I did what the analytical engine tried to do but using electromechanical components. Approved by the original IBM CEO Thomas Watson Sr, the project had begun in 1937 and was shipped to Harvard in 1944. If you can imagine, Hopper and the other programmers did conditional branching manually. Computers played a key role in the war effort and Hopper played a key role in the development of those computers. She co-authored three papers on the Mark I during those early days. She also found a moth in the Mark II in 1947, creating a term everyone in software uses today: debugging. When peace came, she was offered a professorship at Vassar. But she had a much bigger destiny to fulfill. Hopper stayed on at Harvard working on Navy contracts because the Navy didn't want her yet. Yet. She would leave Harvard to go into the private sector for a bit. At this point she could have ended up with Remington Rand designing electric razors (yes, that Remington), or working on the battery division, which would be sold to Rayovac decades later. But she ended up there as a package deal with the UNIVAC. And her destiny began to unfold. You see, writing machine code sucks. She wanted to write software, not machine language. She wanted to write code in English that would then run as machine code. This was highly controversial at the time because programmers didn't see the value in allow what was mainly mathematical notation for data processing to be available in a higher level language, which she proposed would be English statements. She published her first paper on what she called compilers in 1952. There's a lot to unpack about what compilers brought to computing. For starters, they opened up programming to people that would otherwise have seen a bunch of mathematical notations and run away. In her words: “I could say "Subtract income tax from pay" instead of trying to write that in octal code or using all kinds of symbols.” This opened the field up to the next generation of programmers. It also had a second consequence: the computer was no longer just there to do math. Because the Mark I had been based on the Analytical Engine, it was considered a huge and amazing calculator. But putting actual English words out there and then compiling (you can't really call it converting because that's an oversimplification) those into machine code meant the blinders started to come off and that next generation of programmers started to think of computers as… more. The detractors had a couple of valid points. This was the early days of processing. The compiler created code that wasn't as efficient as machine code developed by hand. Especially as there were more and more instructions you could compile. There's really no way around that. But the detractors might not have realized how much faster processors would get. After all they were computing with gears just a few decades earlier. The compiler also opened up the industry to non-mathematicians. I'm pretty sure an objection was that some day someone would write a fart app. And they did. But Grace Hopper was right, the compiler transformed computing into the industry it is today. We still compile code and without the compiler we wouldn't be close to having the industry we have today. In 1954 she basically became the first director of software development when she was promoted to the Director of Automatic Programming. Feeling like an underachiever yet? She was still in the Navy Reserve and in 1957 was promoted to Commander. But she was hard at work at her day job as she and her team at Remington Rand developed a language called FLOW-MATIC the first natural language programming language. In 1959, a bunch of computer nerds were assembled in a conference called CODASYL, or Conference on Data Systems Languages for short. Here, they extended FLOW-MATIC into COBOL making Hopper the mother of compilers and thus the grandmother of COBOL. Picking up a bunch of extra names to add to the end of your title doesn't necessarily mean a dragon flies away with you though. She retired from the Navy in 1966. But again, her story doesn't end there. Hopper went back to the Navy in 1967 after a very successful career with Remington Rand, overseeing the Navy Programming Languages Group. After all, putting language into programming was something she, um, pioneered. She was promoted to a Captain in the Navy in 1973. Here, she directed and developed validation software for COBOL and its compiler through much of the 70s. Armed with those standards, she was then able to go to the Defense Department and push for more computers that were smaller. The rest of the world had no idea the mini-computer (or PC revolution) was coming but she did. Her standards would evolve into the standards managed by the National Institute of Standards and Technology, or NIST, today. You know those NIST configuration guides for configuring a Mac or Windows computer? They do that. The Navy promoted her to a commodore in 1983, a rank renamed to rear admiral just before her retirement in 1986. She earned her Defense Distinguished Service Medal after coming home to the Navy time and time again during her 42 year career there. I guess the meaning of her life was computers and the US Navy. After her retirement, she wasn't ready to slow down. She went to work for Digital Equipment Corporation (DEC) speaking at conferences and industry forums and traveling to the DEC offices. At the time, DEC was the number two computer company in the world. She stayed there until she passed away in 1992. Since her death, she has had a college at Yale renamed in her honor, had a destroyer named after her, and was awarded the Presidential Medal of Honor by then US president Barack Obama. If you don't yet have a spirit animal, you could do worse than to pick her.