Podcasts about frontend

Founder of VoidZero and founder of Vue and Vite Evan You joins us to talk about the evolution of JavaScript tooling, the success of Vite, and what's coming next with VitePlus — a unified toolchain aiming to simplify dev workflows. We also touch on Nitro, multi-runtime support, and where AI might (or might not) fit into the mix. Links https://evanyou.me https://x.com/youyuxi https://bsky.app/profile/evanyou.me https://github.com/yyx990803 We want to hear from you! How did you find us? Did you see us on Twitter? In a newsletter? Or maybe we were recommended by a friend? Let us know by sending an email to our producer, Emily, at emily.kochanekketner@logrocket.com (mailto:emily.kochanekketner@logrocket.com), or tweet at us at PodRocketPod (https://twitter.com/PodRocketpod). Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form (https://podrocket.logrocket.com/get-podrocket-stickers), and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket provides AI-first session replay and analytics that surfaces the UX and technical issues impacting user experiences. Start understand where your users are struggling by trying it for free at [LogRocket.com]. Try LogRocket for free today.(https://logrocket.com/signup/?pdr) Special Guest: Evan You.

Kicking off the Wonder series, Ryan Haskell shares his approach to teaching Elm, his gap year adventures, and his current work at Brilliant. He gives insights into creating accessible learning materials, building games, and finding inspiration outside the Elm ecosystem.Thanks to our sponsor, Logistically. Email: elmtown@logisticallyinc.com.Music by Jesse Moore.Edited by Toni Cañete.Recording date: 2024.11.27GuestRyan HaskellShow notes[00:00:21] Sponsored by Logistically[00:00:43] Introductionryan.townWelcome to Elm! YouTube seriesElm Town 62 – The Map to Elm LandElm Landryan-haskell/date-format[00:01:34] Gap Year[00:03:31] Building a game in GodotTurbo Champ[00:11:01] Welcome to Elm YouTube SeriesRichard Feldman's "Teaching Elm to Beginners" (elm-conf 2017)[00:17:06] Teaching style"Parentheses are like hugs" - from Section 1.5 Advanced Functions[00:24:52] From Wolfgang: Finding inspirationInspiration for Vendr's elm-gql from watching Ben Awad's videos[00:29:07] Remaking Ryan's website[00:32:41] Working at BrilliantBrilliantElm Town 57 – Brilliant ways to use Elm with Aaron StrickRed Blob Games[00:39:15] PicksRyan's picksDracula by Bram StokerThe Picture of Dorian Gray by Oscar WildeVite 6.0The Legend of Zelda: Ocarina of Time (N64)Horizon Zero DawnSatisfactoryJared's picksSatisfactory Night Fever by Dan BullRichard Feldman's "Teaching Elm to Beginners" (elm-conf 2017)Frontend Masters Elm courses by Richard FeldmanIntroduction to Elm, v2Advanced ElmElm in Action by Richard Feldman (Manning)Welcome to Elm! YouTube series

Hoje o papo é sobre decisões. Neste episódio, conversamos com o time da Revolut sobre como administrar e equilibrar as decisões que guiam o desenvolvimento da experiência da pessoa usuária na web e no mobile, incluindo o momento de pender para o nativo ou para o multiplataforma. Vem ver quem participou desse papo: André David, o host que organiza excursões Vinny Neves, Líder de Front-End na Alura Maurício “Balboa” Linhares, engenheiro de software e Hipster de longa data Deni Junior, Software Engineer e Dev Web na Revolut Tiago Leme, Software e iOS Engineer na Revolut

Josh Cirre joins us to discuss his transition from the JavaScript ecosystem to Laravel, revealing why PHP frameworks can offer a compelling alternative for full-stack development. We explore the "identity crisis" many frontend developers face when needing robust backend solutions, how Laravel's batteries-included approach compares to piecing together JavaScript services, and the trade-offs between serverless and traditional hosting environments. Josh also shares insights on Laravel's developer experience, front-end integration options, and his thoughts on what JavaScript frameworks could learn from Laravel's approach to abstraction and infrastructure.Show Notes0:00 - Intro1:02 - Sponsor: Wix Studio1:46 - Introduction to Laravel2:25 - Josh's Journey from Frontend to Backend5:40 - Building the Same Project Across Frameworks6:32 - Josh's Breakthrough with Laravel8:20 - Laravel's Frontend Options10:25 - React Server Components Comparison12:00 - Livewire and Volt13:41 - Josh's Course on Laracasts14:08 - Laravel's DX and Ecosystem16:46 - MVC Structure Explained for JavaScript Developers18:25 - Type Safety Between PHP and JavaScript21:12 - Laravel Pain Points and Criticisms22:40 - Laravel Team's Response to Feedback24:50 - Laravel's Limitations and Use Cases26:10 - Laravel's Developer Products27:20 - Option Paralysis in Laravel30:46 - Laravel's Driver System33:14 - Web Dev Challenge Experience33:38 - TanStack Start Exploration34:50 - Server Functions in TanStack37:38 - Infrastructure Agnostic Development41:02 - Serverless vs. Serverful Cost Comparison44:50 - JavaScript Framework Evolution46:46 - Framework Ecosystems Comparison48:25 - Picks and Plugs Links Mentioned in the EpisodeLaravel - PHP frameworkTanStack Start - React meta-framework Josh created a YouTube video aboutLivewire - Laravel's HTML-over-the-wire front-end frameworkInertia.js - Framework for creating single-page appsVolt - Single file component system for LivewireLaravel Cloud - Managed hosting solution for Laravel applicationsHerd - Laravel's tool for setting up PHP development environmentsForge - Laravel's server management toolEnvoyer - Laravel's zero-downtime deployment toolLaracasts - Where Josh has a course on LivewireJosh Cirre's YouTube channelHTMX - Frontend library Josh compared to LivewireWeb Dev Challenge with Jason Lengstorf (featuring Josh and Amy)Josh Cirre's BlueSky account (@joshcirre)Amy's BlueSky accountBrad's BlueSky account Additional ResourcesLaravel DocumentationSvelte's new starter kit (mentioned as a good example)Nightwatch - Latest product from LaravelLaravel Vapor - Serverless deployment platform for LaravelTheo's Laravel exploration (discussed in the criticism section)Laravel BreezeLaravel JetstreamLaravel Fortify (authentication package mentioned)Adonis.js (JavaScript framework compared to Laravel)Anker USB powered hub (Josh's pick)Grether's Sugar Free Black Currant Pastilles (Josh's pick)JBL Portable Speaker (Amy's pick)

Join hosts Michael Thiessen and Alexander Lichter for a special episode of DejaVue - a fascinating panel discussion on open source sustainability with three open source enthusiasts: Daniel Roe (Nuxt Team Lead),Chad Whitacre (Head of Open Source at Sentry), and Rijk van Zanten (CTO and co-founder of Directus).The panelists dive deep into what sustainability truly means in open source and get deep into the weeds of different licensing models, debating whether open source functions as a gift economy, and discuss the challenges of project governance.The panel also discusses important questions about leadership structures in open source projects, the role of companies in funding development, and practical ways everyone can contribute to making the ecosystem more sustainable - whether financially or through other meaningful contributions.Enjoy the episode!Our GuestsDaniel Roe - Nuxt Team Lead  BlueskyWeb Chad Whitacre - Head of Open Source at Sentry  BlueskyTwitterWebRijk van Zanten - CTO and co-founder of Directus  BlueskyTwitterWebChapters(00:00) - Welcome to DejaVue (04:06) - What is Open Source Sustainability (12:51) - Open Source as a gift economy (19:20) - The Projects and their Licenses (29:50) - Sentry is not Open Source (34:53) - Open Source Definition and OSI (37:09) - Why people adopt open source software? (39:44) - Open Source Governance (47:50) - Stewarding an open source team (52:22) - Open Source Leadership (55:40) - What can YOU do to help open source? Links and ResourcesMastering Nuxt*xkcd on standardsJacob Kaplan-Moss: Paying Maintainers is GoodSentryDirectusNuxtBSLFair Source MITAGPLOSIBDFLNuxt GovernanceOpen Source Steward in the CRADaniel Roe: Contributing to NuxtOpen Source PledgeYour HostsAlexander LichterBlueskyYouTubeWebsiteMichael ThiessenTwitterYouTubeWebsite---Links marked with * are affiliate links. We get a small commission when you register for the service through our link. This helps us to keep the podcast running. We only include affiliate links for services mentioned in the episode or that we use ourselves.

Hello you lovely FECers you, and welcome to Episode 210 of the long-running, will-it-never-end, Front End Chatter podcast for motorcycles and motorcyclists, spoken out loud by Simian Hardgleaves and Marsupial Fatz-Domino.  We are, as ever, indebted and beholden unto Lord Bennetts, Britannia's Best Bike Insurers and may his whaling fleet never run out of blubber, and bikesocial.co.uk, the hostess with the mostess, you know, you know... the one that goes up to 11.  And on this month's episode we have, among many other things:  • a bit of gen on Honda's Hornet 1000 and SP, including how much a piston costs and how many years' warranty you get • who Ixion was, what he has to do with Canon Basil H Davies, and why his 1279 miles in 1905 on a Triumph came to be repeated in 2025... • a game of 'If bikes were family members...' • you know what, it's so long ago I've already forgotten but it's jam-packed with yummy goodness, trust me, I should know.  Get him and he on the socials:  @Mugfa @SimonHBikes (or something like that) And please email your missives and massives to anything@frontendchatter.com Does anyone actually ever read this? 

Bewerbung für ein Erstgespräch: https://bit.ly/4iTod7i Frontend und Backend sind zwei Begriffe, die du bestimmt schon mal gehört hast, wenn du dich mit der Programmierung länger beschäftigst. In dieser Folge erklärt dir Junus, was es mit diesen Begriffen auf sich hat, was der Unterschied ist und was du zuerst lernen solltest, wenn du gerade mit dem Programmieren lernen angefangen hast. YouTube: https://www.youtube.com/c/Programmierenlernen Instagram: https://www.instagram.com/junus.ergin/

Nuxt 3.16 dropped and it's packed with goodies! In this episode, Alex and Michael break down all the cool stuff in this release that'll make your Nuxt development smoother.They dive into the new command to initialize a Nuxt application, the performance-game-changing lazy hydration support that'll boost your app's performance, and named layer aliases (that you've been waiting for). Plus, huge performance improvements, better error messages with Nitro 2.11 and debugging improvements that'll save you hours of head-scratching.But wait, there's more! The duo also geeks out over Nuxt UI v3, which (surprise!) now works with plain Vue.js too - not just Nuxt. Learn how it leverages Tailwind v4, introduces a sweet CSS variables-based design system, and builds on Reka UI primitives for better accessibility. And somehow, a discount code for Nuxt UI Pro* *cough DEJAVUE cough* gets snuck in there too!Enjoy the episode!Chapters(00:00) - Intro (00:54) - Nuxt 3.16 Feature Overview (01:27) - A new way to initialize Nuxt projects (07:06) - Lazy Hydration in Nuxt (16:05) - Named Layer Aliases (17:45) - Lines of Code vs. Complexity (20:16) - What a new Nitro minor brings to the table (21:33) - Fine-grained debugging options (23:25) - Nuxt Devtools v2 (25:47) - Faster module resolution (and faster boot up time) (27:39) - Using OXC to speed up component parsing (28:58) - Benchmark performance improvements (31:43) - Nuxt UI v3 (40:58) - Sneak peek at next weeks episode

Daniele Pishinin, engenheira de software especializada em tecnologias front-end, compartilhou sua trajetória no Emílias Podcast. Ela atua como Frontend Engineer. Além disso, ela é embaixadora do Google Women Techmakers, mentora na Reprograma e colaboradora em eventos comunitários como o DevOps Day Campinas 2024. Durante o episódio, Daniele abordou temas como sua motivação para ingressar na área de computação, destacando o impacto de videogames em sua infância e a escolha por uma carreira focada no desenvolvimento frontend. Ela compartilhou boas práticas para acessibilidade e segurança no desenvolvimento de aplicações, incluindo o uso de guidelines como as do W3C. Além disso, discutiu as ferramentas que utiliza no trabalho, como Visual Studio Code e React Query.Daniele também relatou desafios enfrentados por mulheres na tecnologia, incluindo assédio no início da carreira e dificuldades para mulheres em transição de carreira. Como mentora na Reprograma, ela destacou a importância de criar oportunidades para mulheres ingressarem no mercado. Sobre sua atuação como embaixadora do Google Women Techmakers, enfatizou o papel do programa em conectar mulheres e fortalecer redes de apoio.Por fim, Daniele incentivou mulheres a persistirem na área de computação e indicou os filmes Estrelas Além do Tempo e Batalhão 6888, além do livro Os Irmãos Karamazov. Ela encerrou o episódio agradecendo a oportunidade e reforçando sua disponibilidade para conexões profissionais via LinkedIn.Links de Daniele:https://www.instagram.com/danipishinin/https://www.danipishinin.com/ https://www.linkedin.com/in/danipishinin/Indicações de Daniele:Estrelas Além do Tempo https://www.imdb.com/pt/title/tt4846340Batalhão 6888 https://www.imdb.com/pt/title/tt24458622 Irmãos Karamázov https://www.goodreads.com/book/show/43176794-os-irm-os-karamazov Entrevistadores:Adolfo Neto - Professor da UTFPR https://adolfont.github.io/ Nathálya Chaves - Estudante de Sistemas de Informação da UTFPR e Bolsista do Emílias Podcast.Editor: Allax Almeida Episódio 122 do Emílias Podcast.O Emílias Podcast é um projeto de extensão da UTFPR Curitiba que faz parte da Rede Emílias de Podcasts ⁠⁠https://fronteirases.github.io/redeemilias .  Descubra tudo sobre o programa Emílias - Armação em Bits em ⁠⁠⁠⁠⁠⁠⁠⁠⁠https://linktr.ee/Emilias   #podcast  #EMILIAS

Hey everyone, Alex here

Send us a textJeremy spoke with a couple mentees at Parsity which led to a conversation where I learned about his unusual (and long) journey into software.If you're a career changer and you're dealing with impostor syndrome or tutorial hell and need some practical advice on breaking into tech, you're going to get a lot out of this episode.Connect with Jeremy here: https://www.linkedin.com/in/jrobinparker/Shameless Plugs

[קישור לקובץ mp3]פרק מספר 493 של רברס עם פלטפורמה (אוטוטו 500…), שהוקלט ב-18 במרץ בפברואר 2025 - הפסקת-אש קורסת

Konuklar: Damla Köksal, Onur Can Avcı, Yusuf Batuhan Topçu, Oğuzhan Sofuoğlu 72. bölümümüzde konuğumuz Payment & Financial Products Frontend Chapter ekibi oldu. Ekip yapısını, projelerini, teknoloji stack seçimlerini ve çok daha fazlasını konuştuk! Trendyol Talks'da Trendyol'daki kültürümüzü, kültürümüzden beslenen iş yapış biçimlerimizi ve ritüellerimizi konuşuyoruz. Trendyol Talks podcast kanalımızı takip etmeyi unutmayın!    

Send us a textIn this episode, we're joined by Toby Weiss, CEO of Fiery LLC, and Marcelo Tomoyose, responsible for business development in industrial inkjet solutions at Fiery. Together, we'll explore how Fiery's cutting-edge digital front-end technologies are shaping the future of industrial printing, simplifying complex production processes, and empowering manufacturers to accelerate their transition from analogue to digital. Toby and Marcelo will share valuable insights, real-world examples, and discuss key industry partnerships that are driving innovation in digital printing. Listen on:Apple PodcastGoogle PodcastSpotifyWhat is FuturePrint? FuturePrint is a digital and in person platform and community dedicated to future print technology. Over 15,000 people per month read our articles, listen to our podcasts, view our TV features, click on our e-newsletters and attend our in-person and virtual events. We hope to see you at one of our future in-person events:FuturePrint TECH: Leaders Summit 1 April '25, Valencia, Spain FuturePrint TECH: Packaging & Labels 2-3 April '25, Valencia, SpainFuturePrint TECH: Industrial Print: 22-23 October '25, Munich, Germany

In episode 52 of DejaVue (yes, it is a whole year), Dennis Adriaansen joins Michael and Alex to discuss data visualization in Vue.js. Dennis shares insights about building chart components, his experience with different charting libraries, and introduces his own Vue charting library. They explore topics like chart customization, performance considerations, and integrating charts into dashboards.The conversation also gets into broader topics such as open source sustainability, UI libraries, and backend integrations with Nuxt.Enjoy the episode!Our GuestDennis AdriaansenVue Chart LibraryXBSkyChapters(00:00) - Welcome to DejaVue (00:33) - A year of DejaVue (01:20) - Another announcement from Michael (02:52) - How did you get into programming? (07:07) - Would people choose Vue more if it was more popular? (11:37) - Podcasts and Hot Takes (19:03) - Why charts? (21:05) - How do you get started with building chart components? (23:39) - What was your use case for charts? (25:16) - What does Unovis provide? (29:31) - Why not other Chart Libraries? (34:34) - Performance of Charts (38:48) - A tiny Vapor update (40:40) - Which Charts does your library support? (44:10) - When do you do Open Source? (45:05) - Open Source Funding & Contributions (49:47) - What makes a good Dashboard? (52:03) - Which backend do you use with Nuxt? (58:41) - Do you have a preferred UI library? (01:01:43) - Where can people find you? Links and ResourcesDejaVue #051 - Vite Inside Out (with Matias "Patak" Capeletto)Mastering Nuxt*DejaVue #E049 - The Fusion of Laravel and Vue (with Aaron Francis)DejaVue #E041 - The Quadruple Migration (with Rijk van Zanten)D3.jsTremor Labschart.jsUnovisDennis' Nuxt error dashboardVapor PlaygroundReading Vue VaporVue Chrts (Dennis' Lib)Open Source PledgeBBF PatternzodvalibotStandard SchemaNuxt UI*Inspira UIReka UIYour HostsAlexander LichterBlueskyYouTubeWebsiteMichael ThiessenTwitterYouTubeWebsite---Links marked with * are affiliate links. We get a small commission when you register for the service through our link. This helps us to keep the podcast running. We only include affiliate links for services mentioned in the episode or that we use ourselves.

Tänases Algorütmi episoodis räägime Svelte raamistikust ja sellest, miks arendajad seda nii kõrgelt hindavad. Stuudios on külas Nortali tarkvaraarendaja Annett Saarik, kellega arutame, miks Svelte on kujunenud front-end maailmas justkui vastukaaluks Reacti ja Angulari keerukusele. Uurime, kuidas Svelte'i lihtsus aitab väikestes projektides kiirust lisada, kuid millised võivad olla kitsaskohad suurte rakenduste puhul. Lisaks räägime, kuidas Svelte erineb teistest raamistikest, milline on selle tulevik ja mida muudab uue versiooni tulek.-----Jaga meile enda jaoks olulisimat mõtet episoodist meie Discord kanalis: https://discord.gg/8X5JTkDxccEpisoodi veavad Priit Liivak ja Martin KappAlgorütmi toetavad Patchstack https://patchstack.comNortal https://nortal.com/Veriff https://www.veriff.com/

Join Amy, Brad, and special guest Ryan Chenkie as they unpack Prisma's expanding ecosystem of database tools. Ryan explains why Prisma launched their own hosted Postgres service and what sets it apart from competitors in the space. The trio examines Prisma's comprehensive feature set including Accelerate for connection pooling, Pulse for real-time events, and optimization tools that help identify performance bottlenecks. They also discuss the upcoming transition from Rust to TypeScript for Prisma's core engine, making it lighter and faster. If you've been curious about modern approaches to database management or wondering which ORM is right for your next project, this conversation provides practical insights and expert perspectives.Show Notes0:00 - Intro1:12 - Working with Prisma and Supabase2:29 - Prisma Postgres Introduction4:17 - Why Choose Postgres6:36 - Prisma's Database Adapter Flexibility8:14 - Serverless Database Architecture11:13 - Connection Pooling with Accelerate14:13 - Pulse for Real-time Database Events16:54 - Studio Integration in Prisma Console18:01 - Database Optimization Tools20:00 - Benefits of Prisma Schema Language22:10 - Prisma Schema vs SQL Definitions23:01 - Comparing Prisma and Drizzle26:24 - Future Improvements to Prisma28:52 - Ryan's History with Prisma32:05 - Learning Resources for Prisma33:37 - Picks and PlugsLinks and ResourcesPrisma ResourcesPrisma WebsitePrisma Twitter/XPrisma YouTube ChannelPrisma Postgres DocumentationPrisma ConsolePrisma VS Code ExtensionPrisma AcceleratePrisma PulsePrisma OptimizePrisma StudioRyan Chenkie ResourcesRyan's Website: https://holodeck.runRyan's YouTube Channel: https://youtube.com/@holodeck_runRyan on Twitter/XFramework and Technologies MentionedRemixRedwood JSSupabasePlanetScaleDrizzle ORMPostgresMySQLMongoDBBrad's ResourcesYouTube Channel: https://youtube.com/@bradgarropyRemix Starter: https://github.com/bradgarropy/remix-appAmy's ResourcesBuild12 Projects: https://buildtwelve.comOther Resources MentionedSkylight FrameAura FrameNetflix Show: "Making Fun"Netflix Show: "Is It Cake"

Hoje o papo é sobre desenvolvimento mobile. Neste episódio, reunimos um time de peso para explorar o histórico, os desafios e o futuro de quem lida diariamente com o desafio de desenvolver aplicações multiplataforma. Vem ver quem participou desse papo: André David, o host que reflete consigo mesmo Vinny Neves, Líder de Front-End na Alura Yago Oliveira, Coordenador de Conteúdo Técnico na Alura Ilda Neta, Mobile Software Engineer Pedro Mello, Senior Software Engineer

Adam's friend on the frontend, John Long joins the show to explore his usage of AI, design tools and the stack he prefers. We talk Next.js vs Rails, maintaining open source, building websites with Framer, their mutual love for Figma, and more.

Adam's friend on the frontend, John Long joins the show to explore his usage of AI, design tools and the stack he prefers. We talk Next.js vs Rails, maintaining open source, building websites with Framer, their mutual love for Figma, and more.

We cover how the Shadow DOM encapsulates styles and behavior, why it matters for Drupal theming, and how Web Components fit into modern workflows.

Termin "microservices architecture" w ostatnich latach był odmieniany przez wszystkie możliwe przypadki. Przeważnie jednak ten styl architektoniczny przewijał się w kontekście rozwiązań backendowych i wyciągania z monolitów fragmentów jego funkcjonalności. Rzadko jednak mówiło się o projektowaniu rozwiązań frontendowych w tego rodzaju systemach...Netlifx, Amazon, Spotify czy Uber - te firmy przychodzą z pewnością na myśl jako przykłady popularnych wdrożeń mikroserwisów. W Polsce zdecydowanie jest to Allegro, które dokonało migracji z monolitycznego systemu PHP do właśnie takiej architektury i innych technologii.Tomasz Ducin i Bartosz Gałek, Principal Engineer w Allegro, zaglądają "pod maskę" największego portalu ecommerce w Polsce, aby porozmawiać na temat architektury microfrontendów.Materiały dodatkowe do tego odcinka znajdują się na stronie tego odcinka na bettersoftwaredesign.pl.

Passion to Profession is back, and this time, we're diving into the fast-growing world of F1 cards.Mike at Leahi51513, the largest seller of F1 cards on eBay, joins the show to break down how he built a thriving business, why he believes F1 cards are a generational opportunity, and what he's seeing in collector behavior.We talk about:How F1 cards went from overlooked to must-haveThe global collector base driving demandLessons from the basketball boom and how they apply to F1Why curated auctions are changing the gameThe patience and mindset needed to turn passion into professionWhether you're deep into F1 or just curious about new opportunities in the hobby, this one's worth your time.A special thank you to eBay for sponsoring Passion to Profession. The biggest and best marketplace to buy your next favorite trading card.Get exclusive content, promote your cards, and connect with other collectors who listen to the pod today by joining the Patreon: Join Stacking Slabs Podcast Patreon[Distributed on Sunday] Sign up for the Stacking Slabs Weekly Rip Newsletter using this linkCheck out Card Ladder the official data partner of Stacking SlabsFollow Stacking Slabs: | Twitter | Instagram | Facebook | TiktokFollow Leahi: | Instagram | F1 Featured Auction | eBay Store

Hello and welcome to Front End Chatter, and it's episode 209 of the 209 episode-long motorcycling podcast presented, and I use the word in its loosest sense, by Martina Fitz-Gibbons and Simone Hargreaves, a pair of transitioning motorcycle journalists whose personal pronouns are 'it'. Fronty End Prongs is supported and comported by Bennetts, Britain's biggest and best bike insurers, and without whom you would all be pretty bloody sorry, I can tell you, so make the most of their offers and support their support of motorcycling ya ingrates. And also BikeSocial.co.uk, the hub of motorcycling's metaphorical Akront rim, with their Youtube channel and website and lots of bike-related content to tuck into. So on this episode of FEC we chatter about:  • the latest news from the ailing KTM factory • bad news from the Nürburgring • last-minute booking news if you're thinking about coming to ride with us in Scotland in May on the FEC Highland Fling 2 tour • a ride on Ducati's Multistrada V2 S and exactly how Ducati is it?  • Honda's new NT1100 and what have they done to it?  • Honda's new Hornet and wow, how good is it?  • Honda's last-ever CB1300 and can I have one please?  • why a 270° parallel twin is rarely an exciting engine • how to describe engine configurations • and many more musing and amusings from the FEC Sack of your thoughts, queries, ruminations on a theme Thank you for listening and supporting us with your ears, and please email your own thoughts and musings to: anything@frontendchatter.com Thanks again FECers!  @Simonhbikes @Mufga

Hoje o papo é sobre uma engenharia. Neste episódio, conversamos sobre o histórico, as técnicas, as ferramentas e – talvez mais importante – as armadilhas quando o assunto é engenharia de plataformaVem ver quem participou desse papo: André David, o host que quer virar cozinheiro em alto mar. Ou não. Maurício “Balboa” Linhares, engenheiro de software e Hipster de longa data Vinny Neves, Líder de Front-End na Alura Paulo Alves, Coordenador da escola de DevOps da Alura Gui Santos, Fundador da Platform Rocks

Join Jason Callori and special guest Kim Stokell, Director of Consumer Health Marketing at Cardinal Health, as they dive deep into front-end optimization. This episode explores the importance of a well-designed and merchandised front-end space, how to identify your customer base and their health priorities, and the role of private label products in driving sales.  Kim shares valuable insights on how to create a high-performing front end that enhances patient care, boosts profits, and positions your pharmacy as a trusted resource in your community. Learn about the latest trends in customer buying habits, the importance of community engagement, and how to achieve front-end success.

CLOSE TO ONE MILLIONNNNNNNN VIEWS!I am BLOWN away by the traction of this post!! Check it out! When you lead THAT School, Start With The CROWN, amid the chaos! Partner with Ken to bring the award-winning Ruthless Equity to your school/district! Check out ⁠⁠The Virtual PD Experience ⁠⁠with Ken WilliamsCheck out ⁠⁠The In-Person PD Experience⁠⁠ with Ken Williams⁠⁠Click here ⁠⁠to grab the 2023 IBPA Benjamin Franklin Silver Award Winner  Ruthless Equity: Disrupt The Status-Quo And Ensure Learning For ALL Students. It is a game-changer, baby! For A Signed Copy of Ruthless Equity: go to ⁠⁠https://www.unfoldthesoul.com/store⁠⁠ and order the book there.Get 20% off orders of 20 or more copies of Ruthless Equity: Go to ⁠⁠https://www.unfoldthesoul.com/bulk20⁠⁠⁠⁠Click here⁠⁠ to access everything I do and every FREE resource I have! Remember to save me as a contact!Follow me on:Twitter: https://twitter.com/unfoldthesoulFacebook: https://www.facebook.com/kenspeaks/LinkedIn: https://www.linkedin.com/feed/Instagram: https://www.instagram.com/unfoldthesoul/To schedule a talk with Ken about speaking, coaching, or consulting: ⁠⁠https://www.unfoldthesoul.com/contact⁠⁠Visit The Unfold The Soul Shop: ⁠⁠https://www.unfoldthesoul.com/store⁠⁠Please⁠⁠ leave a review of my book⁠⁠, Ruthless Equity, on Amazon. Thank you!!!

Join Jason Callori and special guest Kim Stokell, Director of Consumer Health Marketing at Cardinal Health, as they dive deep into front-end optimization. This episode explores the importance of a well-designed and merchandised front-end space, how to identify your customer base and their health priorities, and the role of private label products in driving sales.  Kim shares valuable insights on how to create a high-performing front end that enhances patient care, boosts profits, and positions your pharmacy as a trusted resource in your community. Learn about the latest trends in customer buying habits, the importance of community engagement, and how to achieve front-end success.

Hoje o papo é sobre front-end no e-commerce. Neste episódio, conversamos com a equipe da Magalu sobre como lidar com o front no mobile, na web, para dentro e para fora desta gigante do comércio digital do Brasil. Vem ver quem participou desse papo: André David, o host que organiza excursões Vinny Neves, Líder de Front-End na Alura Douglas Zaltron, Especialista Front-end na Luizalabs Francielly Moraes, Especialista Android na Luizalabs Antony Lemos, Especialista Front-End na Luizalabs

Share Your Salary: Front End Lead Amy bonus 433 Thu, 13 Feb 2025 17:29:48 +0000 S6MTGZTipoRjaDoBaQRaFnY3JjrTaLwI society & culture Share Your Salary society & culture Share Your Salary: Front End Lead Amy Because everybody wants to know how much people make for a living, but have been afraid to ask until now… 2024 © 2021 Audacy, Inc. Society & Culture False https://player.amperwavepodcasting.com?feed-link=https%

Hoje o papo é sobre simplificação e escalabilidade. Neste episódio, conversamos sobre design system e front-end no Wellhub: como funciona na prática, quais são os desafios, como é aplicado, e até mesmo o que o back-end tem a ver com essa história. Vem ver quem participou desse papo: André David, o host que segue a linha reta até alguma coisa dar errado Vinny Neves, Líder de Front-End na Alura Marcelo Marcelino, Front-End Software Engineer no Wellhub Sidmar Theodoro, Back-End Software Engineer no Wellhub

У цьому епізоді ведучі разом з нашим гостем, Олегом Дутченком, Senior Frontend Developer в Wezom, обговорили основи JavaScript та TypeScript, їх історію, еволюцію, недоліки та переваги. Чому одні розробники не уявляють без TypeScript життя, а інші категорично його уникають? І чи справді сучасні фреймворки спрощують розробку, чи лише додають хаосу? Ділимося своїм досвідом роботи з цими мовами програмування, а також обговорюємо вплив сучасних фреймворків на розвиток вебтехнологій.Руйнуємо міфи, обговорюємо типізацію, антипатерни, швидкість розробки, а також старі добрі jQuery та React. 00:48 — технічний бекграунд ведучих03:30 — історія JavaScript: витоки та еволюція07:00 — переломні моменти в розвитку JavaScript09:20 — сучасні фреймворки та їх вплив на JavaScript11:21 — недоліки JavaScript та переваги TypeScript18:25 — використання TypeScript у проєктах20:56 — відмова від TypeScript: досвід розробників29:27 — проблеми веброзробки та JavaScript34:04 — порівняння jQuery та сучасних фреймворків40:02 — React vs jQuery: порівняння підходів

I'm calling out five big misconceptions about becoming a frontend developer that might be wrecking your progress. I talk about whether you actually need backend skills to land a frontend gig, if you should learn Next.js, and even if you should learn Tailwind. There's more I dive into, so if you're aiming to become a frontend developer, this one's for you.---------------------------------------------------

En este episodio de Lo que dure la batería, me tiraron la clásica: "Johnny, ¿cuáles son las tendencias de 2025 (y 2026)?" Como si tuviera una bola de cristal.

Join us as Tanner Linsley, the creator and founder of TanStack Start talks about its transition from Vinci to a more streamlined architecture built on Nitro. Learn about the framework's innovative approach to server functions, its isomorphic design philosophy, and how it differs from other frameworks like Remix. Tanner also shares insights into TanStack's sustainable open-source business model and his journey to building developer tools that prioritize user experience over rapid growth.Show Notes0:00 - Intro0:38 - Welcome Tanner Linsley3:43 - React Server Components and TanStack Evolution6:04 - TanStack Start Overview and Vinci Transition11:26 - Nitro Integration and Framework Architecture15:19 - Server Functions and Framework Comparisons20:58 - API Design Philosophy24:19 - Testing and Development Process30:58 - Team and Collaboration Discussion33:38 - Open Source Sponsorship Strategy36:32 - Netlify Partnership Announcement38:37 - Open Source Sustainability Discussion41:03 - Picks and Plugs LinksProducts & Tools:TanStackVinxi by Nikhil SarafNitroReact RouterTRPCRemixH3 (web request library)XPro (Tweet Deck)Deck.blue (BlueSky client)MOTU M4 audio interfaceBamboo Lab A1 3D printerLashbrook Designs (Brad's wedding band)Companies & Sponsors:ConvexClerkAG GridSentryNetlifyGames & Entertainment:Blockus (board game)Severance (TV Show on Apple TV+)"First Lie Wins" (book)Personal Projects & Links:buildtwelve.com (Amy's project)Brad on BlueSky (@bradgaropy.com)Nozzle (Tanner's startup)Technical Resources:Babel Dead Code Elimination (by Pedro Katori)GitHub 3D Contribution Graph GeneratorReact Server Components documentationOther Projects Mentioned:Solid StartAstro

This week we talk to Ryan Carniato, the creator of SolidJS. SolidJS is a modern frontend framework that is designed to be simple, fast, and reactive. It work in almost the exact opposite way of React, but with very familiar patterns. Learn how it's been behind the scenes influencing things for years. https://bsky.app/profile/ryansolid.bsky.social https://www.youtube.com/@ryansolid https://markojs.com/ https://dev.to/ryansolid https://www.solidjs.com/ https://github.com/ryansolid Apply to sponsor the podcast: https://devtools.fm/sponsor Become a paid subscriber our patreon, spotify, or apple podcasts for the ad-free episode. https://www.patreon.com/devtoolsfm https://podcasters.spotify.com/pod/show/devtoolsfm/subscribe https://podcasts.apple.com/us/podcast/devtools-fm/id1566647758 https://www.youtube.com/@devtoolsfm/membership

Luke believes he remembers a very specific scene from a Steve Martin movie that history has mostly forgotten. We check the tape to see how good his memory actually is. He and Andrew also discuss a fascinating story about how Astoria became the location for Kindergarten Cop.

Chris Coyier, co-founder of CodePen, talks about the evolving landscape of HTML heading into 2025. He delves into topics like the slow evolution of HTML compared to CSS and JavaScript, the importance of backwards compatibility, new HTML elements and pseudo-elements, and the potential of declarative shadow DOM for server-side rendering in web components. Links https://chriscoyier.net https://codepen.io/chriscoyier https://front-end.social/@chriscoyier https://github.com/chriscoyier https://www.threads.net/@chriscoyier https://bsky.app/profile/chriscoyier.net We want to hear from you! How did you find us? Did you see us on Twitter? In a newsletter? Or maybe we were recommended by a friend? Let us know by sending an email to our producer, Emily, at emily.kochanekketner@logrocket.com (mailto:emily.kochanekketner@logrocket.com), or tweet at us at PodRocketPod (https://twitter.com/PodRocketpod). Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form (https://podrocket.logrocket.com/get-podrocket-stickers), and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket provides AI-first session replay and analytics that surfaces the UX and technical issues impacting user experiences. Start understand where your users are struggling by trying it for free at [LogRocket.com]. Try LogRocket for free today.(https://logrocket.com/signup/?pdr) Special Guest: Chris Coyier.

In this episode of the Modern Web Podcast, Rob Ocel, Danny Thompson, Adam Rackis, and Brandon Mathis discuss the role of abstractions in software development. They explore frontend tools like React and SolidJS, backend abstractions like serverless platforms, and the importance of understanding patterns and learning through mistakes. The group also highlights emerging trends for 2025, including opportunities in platform plugins and developer marketplaces. Key Points for the Episode: The Role of Abstractions in Development: The panel discusses the benefits and challenges of abstractions in software development, emphasizing the importance of understanding underlying systems to avoid over-reliance on tools like React hooks and serverless platforms. Learning Through Experimentation: Personal experiences with tools like Advent of Code, exploring new languages like Swift and Rust, and experimenting with new frameworks like SolidJS highlight the importance of hands-on learning and stepping outside comfort zones. Platform Opportunities: A growing interest in building apps and plugins on established platforms like Stripe, Zoom, and Chrome Extensions showcases untapped opportunities for developers to create impactful solutions and monetize their skills. Chapters 0:00 - The Potential of Plugins and Platforms 0:42 - Welcome to the Modern Web Podcast 0:47 - Introducing the Hosts and Guests 1:19 - Holiday Projects and Side Gigs 1:31 - Danny's Speedrun of a New Platform 2:07 - Adam's Holiday Reading List 3:38 - Brandon's Advent of Code Challenge in Swift and Rust 5:01 - Learning New Programming Languages Through Challenges 6:52 - Discussion on Abstractions in Software Development 7:10 - The Balance Between Abstractions and Understanding the Basics 8:56 - Learning Through Experience: The Importance of Stepping on Rakes 9:46 - React's Role in Frontend Development and Its Critics 10:39 - The Evolution of Frontend and Backend Abstractions 12:09 - The Impact of Serverless and Cloud Platforms 13:31 - Misuse of Abstractions and Overcomplicated Code 14:27 - The Common Pitfalls of React Hooks Misuse 15:29 - Overuse of `useEffect` and Its Performance Implications 16:41 - Learning from Industry Experts: Insights from Ben Lesh 17:53 - The Evolution of the Web from Static Documents to Interactive Applications 19:04 - The Role of Abstractions in Backend Development and Serverless Adoption 21:06 - Advice for Developers on Understanding Patterns and Abstractions 22:21 - Sponsor Message: This Dot Labs 22:27 - Looking Ahead to 2025: Technologies and Trends 22:43 - Excitement Around SolidJS and Signals-Based Frameworks 23:29 - The Growing Ecosystem Around SolidJS and TanStack Router 24:48 - Insights from a Conversation with Ryan Carniato 25:19 - Interest in TanStack Start and React 19 Features 26:09 - Danny Learning Spanish and Coding Challenges 27:16 - Exploring New Platforms for Side Projects and Monetization 27:55 - The Untapped Potential in Plugin and App Store Ecosystems 29:01 - Case Study: Monetization through Small Chrome and Office Extensions 30:09 - Growth of Developer Marketplaces (Stripe, Slack, Shopify, Zoom) 31:06 - The Challenge of Getting Projects in Front of Users 32:03 - Opportunities in Game Modding and Twitch Extensions 32:32 - Closing Thoughts and Future Podcast Episodes 32:45 - Sponsor Message and Where to Find the Podcast Online Follow the crew on Twitter and Linkedin: Rob Twitter: https://x.com/robocell Rob Linkedin:   / robocel   Danny Twitter: https://x.com/DThompsonDev Danny Linkedin:   / dthompsondev   Adam Twitter: https://x.com/AdamRackis Adam Linkedin:   / adam-rackis-5b655a8   Brandon Twitter: https://x.com/BrandonMathis Brandon Linkedin:   / mathisbrandon   Sponsored by This Dot: thisdot.co

FEC208  Hello moi luverly FECers and this, believe it or not, is Front End Chatter episode 208 in a long-running series with him, believe it or not, Martin Fitz-Gibbons, and him, believe it or not, Simon Hargreaves.   Believe it or not, you should get your bike insurance from Bennetts, Britain's best bike insurers and supporters of Front End Chatter since 1894, with massive range of savings and offers on all sorts of kit and caboodle, plus lots of cool policy add-ons like 90 days EU cover and common mods (like road legal exhausts) covered – as standard! And you also get free BikeSocial membership (which you can also buy for £60 regardless of your insurer), which gives you access to all the above offers and savings, plus VIP experiences, cheap track days; the list goes on. And don't forget to visit bikesocial.co.uk and their Youtube channel for all your biking media consumption needs.  And – last few rooms remaining on the FEC Highland Fling 2 – yes, ride Scotland's greatest hits this May with Simon and Martin, enjoying the best of the NC500, the best of the West Coast, and a romp through the Cairngorms, all while staying at the Aultguish Inn and partaking of libation in the evening. The dates for Fling 2 are arrival Thursday May 6th, departure Sunday May 10th. Visit bit.ly/fecfling2 for more info, or email anything@frontendchatter.com or Paul at MCI Tours – info@mcitours.com  And on that note, what's actually in the podcast? I'd tell you but, honestly, on this occasion it's easier to just listen! Email anything@frontendchatter.com with your thoughts and queries and stuff, and get Martin and Simon on some of the social medias: Insta:MufgaSimonhbikes BSky: @sihbikes.bsky.social @mufga.bsky.social    

A friburguense Julia se formou em Letras e Relações Internacionais e, depois de iniciar um mestrado em Relações Internacionais na Inglaterra, ela concluiu que queria ter mais estabilidade e ter mais liberdade para trabalhar remotamente. Graças ao convite de uma amiga portuguesa que a chamou para passar o Natal em Lisboa, Julia se identificou bastante com o país, e decidiu seguir com o mestrado por lá antes de mudar definitivamente de planos e decidir migrar para o mundo da tecnologia. Com um bootcamp e um curso de programação embaixo do braço, ela conquistou a primeira oportunidade profissional, onde começou sua jornada de aprendizado de front-end na prática. Neste episódio, ela detalha essa curiosa trajetória, além da forma interessante como ela encarou sua mudança de carreira na terra dos Pastéis de Belém. Fabrício Carraro, o seu viajante poliglota Julia M., Desenvolvedora Front-end em Lisboa, Portugal Links: Geek Girls Portugal Inscreva-se na Imersão Front-End da Alura, crie um projeto do zero e comece a construir sua carreira Front-end. Seria cinco aulas grátis, de 27 a 31 de janeiro. TechGuide.sh, um mapeamento das principais tecnologias demandadas pelo mercado para diferentes carreiras, com nossas sugestões e opiniões. #7DaysOfCode: Coloque em prática os seus conhecimentos de programação em desafios diários e gratuitos. Acesse https://7daysofcode.io/ Ouvintes do podcast Dev Sem Fronteiras têm 10% de desconto em todos os planos da Alura Língua. Basta ir a https://www.aluralingua.com.br/promocao/devsemfronteiras/e começar a aprender inglês e espanhol hoje mesmo!  Produção e conteúdo: Alura Língua Cursos online de Idiomas – https://www.aluralingua.com.br/ Alura Cursos online de Tecnologia – https://www.alura.com.br/ Edição e sonorização: Rede Gigahertz de Podcasts

Qual o limite da empatia? Quanto demora pra perceber que seu webamor verdadeiro não é nem amor, nem verdadeiro? Hoje @katbarcelos, @odeiopepe e @principevidane arbitraram se é ou não ok acreditar tanto assim no seu potencial! A primeira imersão do ano da Alura chegou, com foco em Front-End! São 5 aulas grátis para você criar um projeto e ainda sair com certificado, mas essa é a última semana para se inscrever, então corre! https://alura.tv/vortex-imersao-frontend25  Desconto especial nos planos usando o nosso link no Nordvpn: https://nordvpn.com/vortexpod ou CUPOM: VORTEXPOD   Acesse o link do Vortex e ganhe 15% de desconto na sua matrícula na Alura: https://www.alura.com.br/vortex ou CUPOM: VORTEX Link do Bingo: https://drive.google.com/file/d/1ci3tPomA_I82XWuKsZEcSCP82MV59_8Y/view?usp=sharing Criado por: @catharina.art Host: Katiucha Barcelos. Instagram: @katbarcelos | Twitter/X: @katiucha Co-Host: Pedro Pinheiro. Instagram: @odeiopepe | Twitter/X: @OdeioPePe Convidado: Príncipe Vidane. Instagram: @principevidane | Twitter/X: @principevidane | Twitch: twitch.tv/principevidane | Vocês também podem escutar o Vidane nos podcasts Dentro da Minha Cabeça, Mau Acompanhado e Pelada na Net  Nossas redes sociais: Instagram: @feedvortex Twitter: @feedvortex Reddit: r/feedvortex Grupo paralelo não-oficial do Vortex no telegram: https://t.me/+BHlkG92BfPU5Zjdh Esse grupo é dos ouvintes, para os ouvintes e pelos ouvintes. Não temos qualquer afiliação oficial ou responsabilidade por QUALQUER COISA falada neste grupo Link do post do episódio nas redes sociais: Instagram: https://www.instagram.com/p/DFI5HFUvX3Y/?utm_source=ig_web_copy_link Twitter: https://x.com/feedvortex/status/1882141586223665578 Links comentados no episódio: Por que as mulheres ocidentais estão indo para a Coreia do Sul em busca do amor: https://edition.cnn.com/travel/article/south-korea-western-women-seeking-love-intl-hnk-dst/index.html  Francesa que perdeu R$ 5,2 milhões em golpe com 'Brad Pitt' enfrenta depressão: https://extra.globo.com/blogs/page-not-found/post/2025/01/divorciada-de-milionario-e-sem-teto-francesa-que-perdeu-r-52-milhoes-em-golpe-com-brad-pitt-enfrenta-depressao.ghtml França investiga caso de mulher que sofreu golpe de falso Brad Pitt:https://f5.folha.uol.com.br/celebridades/2025/01/brad-pitt-se-manifesta-sobre-golpe-que-fez-mulher-acreditar-que-estava-namorando-o-astro.shtml Jogador de vôlei italiano que caiu em golpe por acreditar namorar a modelo brasileira Alessandra: https://g1.globo.com/mundo/noticia/2021/11/25/jogador-de-volei-italiano-cai-em-golpe-e-acredita-que-namora-a-modelo-brasileira-alessandra-ambrosio.ghtml Polícia faz operação contra suspeitas de enganar italiano que pensou namorar Alessandra Ambrosio: https://oglobo.globo.com/brasil/policia-faz-operacao-contra-suspeitas-de-enganar-italiano-que-pensou-namorar-alessandra-ambrosio-1-25494488 Atleta italiano enganado 15 anos por falsa namorada que usava fotos de Alessandra Ambrosio chorou ao ter revelação; veja vídeo: https://oglobo.globo.com/brasil/atleta-italiano-enganado-15-anos-por-falsa-namorada-que-usava-fotos-de-alessandra-ambrosio-chorou-ao-ter-revelacao-veja-video-1-25292493 === Produção: Thyara Castro, Bruno Azevedo e Aparecido Santos Edição: Joel Suke Ilustração da capa: Brann Sousa

Hoje o papo é sobre GraphQL no mobile. Neste episódio, conversamos sobre o histórico do GraphQL, desde os problemas que ele veio para resolver, até ecossistema, o que é (e o que não é) responsabilidade do GraphQL, vantagens e desvantagens do uso de GraphQL versus REST, e muito mais. Vem ver quem participou desse papo: André David, o host que já é o tradicional co-host Vinny Neves, Líder de Front-End na Alura Yago Oliveira, Coordenador de Conteúdo Técnico na Alura William Bezerra, Instrutor na Alura e Engenheiro Sênior no QuintoAndar

Topics DiscussedThe importance of changeability as a core characteristic of well-maintained software.How GitHub has approached accessibility as a business and legal imperative.The evolution of GitHub's frontend system, spanning over 2,000 pages, and the concept of "frontend vintages."Primer: GitHub's design system and the paradox of its success—consistency vs. changeability.The disproportionate maintenance costs of frontend systems compared to backend systems.Using tools like Axe and keyboard-only tests to identify and resolve accessibility issues.The philosophical balance between creativity and usability in software design.Practical advice for teams starting their accessibility journey with limited resources.How frontend complexity affects scalability, especially in app-like experiences.Joel's advocacy for adopting off-the-shelf components to reduce complexity for smaller teams.Key Takeaways[00:01:12] What Defines Well-Maintained Software?Joel explains how changeability—the confidence to make and deploy changes—provides the foundation for high-quality software.[00:03:05] Accessibility as a PriorityThe Microsoft acquisition drove GitHub's investment in accessibility, introducing SLAs, automated tools, and manual processes to track progress.[00:08:49] Primer: GitHub's Design SystemPrimer fosters consistency but introduces the challenge of making changes across a vast, interconnected system.[00:12:54] The Cost of Frontend ComplexityJoel shares how browser quirks, device diversity, and other variables make frontend maintenance far more expensive than backend systems.[00:28:05] Where to Start with AccessibilityJoel recommends focusing on key user workflows like signing up, making payments, and completing core tasks. He emphasizes the importance of tools like Axe and keyboard-driven tests.Notable Time-Stamps[00:01:12] What Makes Software Well-Maintained? Joel shares how changeability drives quality.[00:03:05] GitHub's Accessibility Journey: The role of SLAs, audits, and automation.[00:08:49] Primer and Design Systems: Balancing consistency with innovation.[00:12:54] The Hidden Costs of Frontend Complexity: Lessons learned at GitHub.[00:20:33] Balancing Creativity with Usability: Joel reflects on the intersection of design and functionality.[00:28:05] Accessibility Best Practices: Where teams should focus their initial efforts.ResourcesJoel Hawksley's WebsitePrimer Design SystemAxe Accessibility ToolsGitHub's ViewComponent FrameworkBook Recommendation:How Buildings Learn by Stewart BrandGuest's LinksJoel Hawksley on GitHubJoel Hawksley's WebsiteThanks to Our Sponsor!Turn hours of debugging into just minutes! AppSignal is a performance monitoring and error-tracking tool designed for Ruby, Elixir, Python, Node.js, Javascript, and other frameworks.It offers six powerful features with one simple interface, providing developers with real-time insights into the performance and health of web applications.Keep your coding cool and error-free, one line at a time! Use the code maintainable to get a 10% discount for your first year. Check them out! Subscribe to Maintainable on:Apple PodcastsSpotifyOr search "Maintainable" wherever you stream your podcasts.Keep up to date with the Maintainable Podcast by joining the newsletter.

Hello and welcome to Front End Chatter, Britain's physics-bendingiest motorcycling podcast, a vision formed when eccentric inventors Simon Hargreaves and Martin Fitz-Gibbons slipped off a toilet seat and banged their heads on a sink. This is episode #207 which, as always, is powered by the suitcase of stolen plutonium that is Bennetts, the bike insurance specialists, and BikeSocial.co.uk, the first ​place you should point your browser for used-bike buying guides, in-depth product reviews, new-bike technical analysis, the week's hotted two-wheels deals, plus so much more.   And this week, in the absence of much going on in the biking world (other than Simon squeezing Christmas lunch into the panniers of a Triumph Tiger, and Mufga squeezing Christmas lunch into himself several times over), FEC takes a twenty-year trip back in time, back to January 2005, or more specifically the January 2005 issue of Bike magazine. A time when Britain was obsessed with sportsbikes, when Mufga was obsessed with dataloggers, and when Simon was obsessed by Troy Lee decals. How times have changed.   Come between the covers with us (ahem) as Simon and Mufga spill the goss on how Britain's biggest-selling bike magazine was cobbled together 20 years ago, including:   •     Yamaha's MT-01 – what it was, why it was made, whether it was a flop, and why Si had to push one down a hill •     KTM's 990 Super Duke – why it came with the rudest promo video ever, and whether it'd take KTM from unknowns to the biggest brand in Europe •     Yamaha YZF-R6 – why a new set of forks and brakes made Si visit a burger van in the Peak District •     Ducati Monster S2R – why it made Mufga bar-hop through Monte Carlo, and why a WSB legend flicked the Vs at Chippy Wood, Bike's own legend •     Plus the creeping rise of nostalgia in motorcycling; one of the ugliest group tests ever put on paper; the questionably relevance of riding MotoGP bikes; and a plethora of predictions gone horribly wrong.   We hope you enjoy our spectacularly self-indulgent trip down memory lane. If you do, let us know which era we should revisit next by emailing anything@frontendchatter.com – and if you don't, then instead email us with your thoughts, questions, observations, wonderings, ponderings about all things two-wheeled, modern or historical, for us to waffle about this year.   Thank you for listening, and we hope to see you in Scotland on FEC Highland Fling (#1 & #2) in May, and/or the FECstival in October!   Follow us on the socials:   Bluesky @sihbikes.bsky.social @mufga.bsky.social   Instagram @simonhbikes @mufga

Applications for the NYC AI Engineer Summit, focused on Agents at Work, are open!When we first started Latent Space, in the lightning round we'd always ask guests: “What's your favorite AI product?”. The majority would say Midjourney. The simple UI of prompt → very aesthetic image turned it into a $300M+ ARR bootstrapped business as it rode the first wave of AI image generation.In open source land, StableDiffusion was congregating around AUTOMATIC1111 as the de-facto web UI. Unlike Midjourney, which offered some flags but was mostly prompt-driven, A1111 let users play with a lot more parameters, supported additional modalities like img2img, and allowed users to load in custom models. If you're interested in some of the SD history, you can look at our episodes with Lexica, Replicate, and Playground.One of the people involved with that community was comfyanonymous, who was also part of the Stability team in 2023, decided to build an alternative called ComfyUI, now one of the fastest growing open source projects in generative images, and is now the preferred partner for folks like Black Forest Labs's Flux Tools on Day 1. The idea behind it was simple: “Everyone is trying to make easy to use interfaces. Let me try to make a powerful interface that's not easy to use.”Unlike its predecessors, ComfyUI does not have an input text box. Everything is based around the idea of a node: there's a text input node, a CLIP node, a checkpoint loader node, a KSampler node, a VAE node, etc. While daunting for simple image generation, the tool is amazing for more complex workflows since you can break down every step of the process, and then chain many of them together rather than manually switching between tools. You can also re-start execution halfway instead of from the beginning, which can save a lot of time when using larger models.To give you an idea of some of the new use cases that this type of UI enables:* Sketch something → Generate an image with SD from sketch → feed it into SD Video to animate* Generate an image of an object → Turn into a 3D asset → Feed into interactive experiences* Input audio → Generate audio-reactive videosTheir Examples page also includes some of the more common use cases like AnimateDiff, etc. They recently launched the Comfy Registry, an online library of different nodes that users can pull from rather than having to build everything from scratch. The project has >60,000 Github stars, and as the community grows, some of the projects that people build have gotten quite complex:The most interesting thing about Comfy is that it's not a UI, it's a runtime. You can build full applications on top of image models simply by using Comfy. You can expose Comfy workflows as an endpoint and chain them together just like you chain a single node. We're seeing the rise of AI Engineering applied to art.Major Tom's ComfyUI Resources from the Latent Space DiscordMajor shoutouts to Major Tom on the LS Discord who is a image generation expert, who offered these pointers:* “best thing about comfy is the fact it supports almost immediately every new thing that comes out - unlike A1111 or forge, which still don't support flux cnet for instance. It will be perfect tool when conflicting nodes will be resolved”* AP Workflows from Alessandro Perili are a nice example of an all-in-one train-evaluate-generate system built atop Comfy* ComfyUI YouTubers to learn from:* @sebastiankamph* @NerdyRodent* @OlivioSarikas* @sedetweiler* @pixaroma* ComfyUI Nodes to check out:* https://github.com/kijai/ComfyUI-IC-Light* https://github.com/MrForExample/ComfyUI-3D-Pack* https://github.com/PowerHouseMan/ComfyUI-AdvancedLivePortrait* https://github.com/pydn/ComfyUI-to-Python-Extension* https://github.com/THtianhao/ComfyUI-Portrait-Maker* https://github.com/ssitu/ComfyUI_NestedNodeBuilder* https://github.com/longgui0318/comfyui-magic-clothing* https://github.com/atmaranto/ComfyUI-SaveAsScript* https://github.com/ZHO-ZHO-ZHO/ComfyUI-InstantID* https://github.com/AIFSH/ComfyUI-FishSpeech* https://github.com/coolzilj/ComfyUI-Photopea* https://github.com/lks-ai/anynode* Sarav: https://www.youtube.com/@mickmumpitz/videos ( applied stuff )* Sarav: https://www.youtube.com/@latentvision (technical, but infrequent)* look for comfyui node for https://github.com/magic-quill/MagicQuill* “Comfy for Video” resources* Kijai (https://github.com/kijai) pushing out support for Mochi, CogVideoX, AnimateDif, LivePortrait etc* Comfyui node support like LTX https://github.com/Lightricks/ComfyUI-LTXVideo , and HunyuanVideo* FloraFauna AI* Communities: https://www.reddit.com/r/StableDiffusion/, https://www.reddit.com/r/comfyui/Full YouTube EpisodeAs usual, you can find the full video episode on our YouTube (and don't forget to like and subscribe!)Timestamps* 00:00:04 Introduction of hosts and anonymous guest* 00:00:35 Origins of Comfy UI and early Stable Diffusion landscape* 00:02:58 Comfy's background and development of high-res fix* 00:05:37 Area conditioning and compositing in image generation* 00:07:20 Discussion on different AI image models (SD, Flux, etc.)* 00:11:10 Closed source model APIs and community discussions on SD versions* 00:14:41 LoRAs and textual inversion in image generation* 00:18:43 Evaluation methods in the Comfy community* 00:20:05 CLIP models and text encoders in image generation* 00:23:05 Prompt weighting and negative prompting* 00:26:22 Comfy UI's unique features and design choices* 00:31:00 Memory management in Comfy UI* 00:33:50 GPU market share and compatibility issues* 00:35:40 Node design and parameter settings in Comfy UI* 00:38:44 Custom nodes and community contributions* 00:41:40 Video generation models and capabilities* 00:44:47 Comfy UI's development timeline and rise to popularity* 00:48:13 Current state of Comfy UI team and future plans* 00:50:11 Discussion on other Comfy startups and potential text generation supportTranscriptAlessio [00:00:04]: Hey everyone, welcome to the Latent Space podcast. This is Alessio, partner and CTO at Decibel Partners, and I'm joined by my co-host Swyx, founder of Small AI.swyx [00:00:12]: Hey everyone, we are in the Chroma Studio again, but with our first ever anonymous guest, Comfy Anonymous, welcome.Comfy [00:00:19]: Hello.swyx [00:00:21]: I feel like that's your full name, you just go by Comfy, right?Comfy [00:00:24]: Yeah, well, a lot of people just call me Comfy, even when they know my real name. Hey, Comfy.Alessio [00:00:32]: Swyx is the same. You know, not a lot of people call you Shawn.swyx [00:00:35]: Yeah, you have a professional name, right, that people know you by, and then you have a legal name. Yeah, it's fine. How do I phrase this? I think people who are in the know, know that Comfy is like the tool for image generation and now other multimodality stuff. I would say that when I first got started with Stable Diffusion, the star of the show was Automatic 111, right? And I actually looked back at my notes from 2022-ish, like Comfy was already getting started back then, but it was kind of like the up and comer, and your main feature was the flowchart. Can you just kind of rewind to that moment, that year and like, you know, how you looked at the landscape there and decided to start Comfy?Comfy [00:01:10]: Yeah, I discovered Stable Diffusion in 2022, in October 2022. And, well, I kind of started playing around with it. Yes, I, and back then I was using Automatic, which was what everyone was using back then. And so I started with that because I had, it was when I started, I had no idea like how Diffusion works. I didn't know how Diffusion models work, how any of this works, so.swyx [00:01:36]: Oh, yeah. What was your prior background as an engineer?Comfy [00:01:39]: Just a software engineer. Yeah. Boring software engineer.swyx [00:01:44]: But like any, any image stuff, any orchestration, distributed systems, GPUs?Comfy [00:01:49]: No, I was doing basically nothing interesting. Crud, web development? Yeah, a lot of web development, just, yeah, some basic, maybe some basic like automation stuff. Okay. Just. Yeah, no, like, no big companies or anything.swyx [00:02:08]: Yeah, but like already some interest in automations, probably a lot of Python.Comfy [00:02:12]: Yeah, yeah, of course, Python. But I wasn't actually used to like the Node graph interface before I started Comfy UI. It was just, I just thought it was like, oh, like, what's the best way to represent the Diffusion process in the user interface? And then like, oh, well. Well, like, naturally, oh, this is the best way I've found. And this was like with the Node interface. So how I got started was, yeah, so basic October 2022, just like I hadn't written a line of PyTorch before that. So it's completely new. What happened was I kind of got addicted to generating images.Alessio [00:02:58]: As we all did. Yeah.Comfy [00:03:00]: And then I started. I started experimenting with like the high-res fixed in auto, which was for those that don't know, the high-res fix is just since the Diffusion models back then could only generate that low-resolution. So what you would do, you would generate low-resolution image, then upscale, then refine it again. And that was kind of the hack to generate high-resolution images. I really liked generating. Like higher resolution images. So I was experimenting with that. And so I modified the code a bit. Okay. What happens if I, if I use different samplers on the second pass, I was edited the code of auto. So what happens if I use a different sampler? What happens if I use a different, like a different settings, different number of steps? And because back then the. The high-res fix was very basic, just, so. Yeah.swyx [00:04:05]: Now there's a whole library of just, uh, the upsamplers.Comfy [00:04:08]: I think, I think they added a bunch of, uh, of options to the high-res fix since, uh, since, since then. But before that was just so basic. So I wanted to go further. I wanted to try it. What happens if I use a different model for the second, the second pass? And then, well, then the auto code base was, wasn't good enough for. Like, it would have been, uh, harder to implement that in the auto interface than to create my own interface. So that's when I decided to create my own. And you were doing that mostly on your own when you started, or did you already have kind of like a subgroup of people? No, I was, uh, on my own because, because it was just me experimenting with stuff. So yeah, that was it. Then, so I started writing the code January one. 2023, and then I released the first version on GitHub, January 16th, 2023. That's how things got started.Alessio [00:05:11]: And what's, what's the name? Comfy UI right away or? Yeah.Comfy [00:05:14]: Comfy UI. The reason the name, my name is Comfy is people thought my pictures were comfy, so I just, uh, just named it, uh, uh, it's my Comfy UI. So yeah, that's, uh,swyx [00:05:27]: Is there a particular segment of the community that you targeted as users? Like more intensive workflow artists, you know, compared to the automatic crowd or, you know,Comfy [00:05:37]: This was my way of like experimenting with, uh, with new things, like the high risk fixed thing I mentioned, which was like in Comfy, the first thing you could easily do was just chain different models together. And then one of the first things, I think the first times it got a bit of popularity was when I started experimenting with the different, like applying. Prompts to different areas of the image. Yeah. I called it area conditioning, posted it on Reddit and it got a bunch of upvotes. So I think that's when, like, when people first learned of Comfy UI.swyx [00:06:17]: Is that mostly like fixing hands?Comfy [00:06:19]: Uh, no, no, no. That was just, uh, like, let's say, well, it was very, well, it still is kind of difficult to like, let's say you want a mountain, you have an image and then, okay. I'm like, okay. I want the mountain here and I want the, like a, a Fox here.swyx [00:06:37]: Yeah. So compositing the image. Yeah.Comfy [00:06:40]: My way was very easy. It was just like, oh, when you run the diffusion process, you kind of generate, okay. You do pass one pass through the diffusion, every step you do one pass. Okay. This place of the image with this brand, this space, place of the image with the other prop. And then. The entire image with another prop and then just average everything together, every step, and that was, uh, area composition, which I call it. And then, then a month later, there was a paper that came out called multi diffusion, which was the same thing, but yeah, that's, uh,Alessio [00:07:20]: could you do area composition with different models or because you're averaging out, you kind of need the same model.Comfy [00:07:26]: Could do it with, but yeah, I hadn't implemented it. For different models, but, uh, you, you can do it with, uh, with different models if you want, as long as the models share the same latent space, like we, we're supposed to ring a bell every time someone says, yeah, like, for example, you couldn't use like Excel and SD 1.5, because those have a different latent space, but like, uh, yeah, like SD 1.5 models, different ones. You could, you could do that.swyx [00:07:59]: There's some models that try to work in pixel space, right?Comfy [00:08:03]: Yeah. They're very slow. Of course. That's the problem. That that's the, the reason why stable diffusion actually became like popular, like, cause was because of the latent space.swyx [00:08:14]: Small and yeah. Because it used to be latent diffusion models and then they trained it up.Comfy [00:08:19]: Yeah. Cause a pixel pixel diffusion models are just too slow. So. Yeah.swyx [00:08:25]: Have you ever tried to talk to like, like stability, the latent diffusion guys, like, you know, Robin Rombach, that, that crew. Yeah.Comfy [00:08:32]: Well, I used to work at stability.swyx [00:08:34]: Oh, I actually didn't know. Yeah.Comfy [00:08:35]: I used to work at stability. I got, uh, I got hired, uh, in June, 2023.swyx [00:08:42]: Ah, that's the part of the story I didn't know about. Okay. Yeah.Comfy [00:08:46]: So the, the reason I was hired is because they were doing, uh, SDXL at the time and they were basically SDXL. I don't know if you remember it was a base model and then a refiner model. Basically they wanted to experiment, like chaining them together. And then, uh, they saw, oh, right. Oh, this, we can use this to do that. Well, let's hire that guy.swyx [00:09:10]: But they didn't, they didn't pursue it for like SD3. What do you mean? Like the SDXL approach. Yeah.Comfy [00:09:16]: The reason for that approach was because basically they had two models and then they wanted to publish both of them. So they, they trained one on. Lower time steps, which was the refiner model. And then they, the first one was trained normally. And then they went during their test, they realized, oh, like if we string these models together are like quality increases. So let's publish that. It worked. Yeah. But like right now, I don't think many people actually use the refiner anymore, even though it is actually a full diffusion model. Like you can use it on its own. And it's going to generate images. I don't think anyone, people have mostly forgotten about it. But, uh.Alessio [00:10:05]: Can we talk about models a little bit? So stable diffusion, obviously is the most known. I know flux has gotten a lot of traction. Are there any underrated models that people should use more or what's the state of the union?Comfy [00:10:17]: Well, the, the latest, uh, state of the art, at least, yeah, for images there's, uh, yeah, there's flux. There's also SD3.5. SD3.5 is two models. There's a, there's a small one, 2.5B and there's the bigger one, 8B. So it's, it's smaller than flux. So, and it's more, uh, creative in a way, but flux, yeah, flux is the best. People should give SD3.5 a try cause it's, uh, it's different. I won't say it's better. Well, it's better for some like specific use cases. Right. If you want some to make something more like creative, maybe SD3.5. If you want to make something more consistent and flux is probably better.swyx [00:11:06]: Do you ever consider supporting the closed source model APIs?Comfy [00:11:10]: Uh, well, they, we do support them as custom nodes. We actually have some, uh, official custom nodes from, uh, different. Ideogram.swyx [00:11:20]: Yeah. I guess DALI would have one. Yeah.Comfy [00:11:23]: That's, uh, it's just not, I'm not the person that handles that. Sure.swyx [00:11:28]: Sure. Quick question on, on SD. There's a lot of community discussion about the transition from SD1.5 to SD2 and then SD2 to SD3. People still like, you know, very loyal to the previous generations of SDs?Comfy [00:11:41]: Uh, yeah. SD1.5 then still has a lot of, a lot of users.swyx [00:11:46]: The last based model.Comfy [00:11:49]: Yeah. Then SD2 was mostly ignored. It wasn't, uh, it wasn't a big enough improvement over the previous one. Okay.swyx [00:11:58]: So SD1.5, SD3, flux and whatever else. SDXL. SDXL.Comfy [00:12:03]: That's the main one. Stable cascade. Stable cascade. That was a good model. But, uh, that's, uh, the problem with that one is, uh, it got, uh, like SD3 was announced one week after. Yeah.swyx [00:12:16]: It was like a weird release. Uh, what was it like inside of stability actually? I mean, statute of limitations. Yeah. The statute of limitations expired. You know, management has moved. So it's easier to talk about now. Yeah.Comfy [00:12:27]: And inside stability, actually that model was ready, uh, like three months before, but it got, uh, stuck in, uh, red teaming. So basically the product, if that model had released or was supposed to be released by the authors, then it would probably have gotten very popular since it's a, it's a step up from SDXL. But it got all of its momentum stolen. It got stolen by the SD3 announcement. So people kind of didn't develop anything on top of it, even though it's, uh, yeah. It was a good model, at least, uh, completely mostly ignored for some reason. Likeswyx [00:13:07]: I think the naming as well matters. It seemed like a branch off of the main, main tree of development. Yeah.Comfy [00:13:15]: Well, it was different researchers that did it. Yeah. Yeah. Very like, uh, good model. Like it's the Worcestershire authors. I don't know if I'm pronouncing it correctly. Yeah. Yeah. Yeah.swyx [00:13:28]: I actually met them in Vienna. Yeah.Comfy [00:13:30]: They worked at stability for a bit and they left right after the Cascade release.swyx [00:13:35]: This is Dustin, right? No. Uh, Dustin's SD3. Yeah.Comfy [00:13:38]: Dustin is a SD3 SDXL. That's, uh, Pablo and Dome. I think I'm pronouncing his name correctly. Yeah. Yeah. Yeah. Yeah. That's very good.swyx [00:13:51]: It seems like the community is very, they move very quickly. Yeah. Like when there's a new model out, they just drop whatever the current one is. And they just all move wholesale over. Like they don't really stay to explore the full capabilities. Like if, if the stable cascade was that good, they would have AB tested a bit more. Instead they're like, okay, SD3 is out. Let's go. You know?Comfy [00:14:11]: Well, I find the opposite actually. The community doesn't like, they only jump on a new model when there's a significant improvement. Like if there's a, only like a incremental improvement, which is what, uh, most of these models are going to have, especially if you, cause, uh, stay the same parameter count. Yeah. Like you're not going to get a massive improvement, uh, into like, unless there's something big that, that changes. So, uh. Yeah.swyx [00:14:41]: And how are they evaluating these improvements? Like, um, because there's, it's a whole chain of, you know, comfy workflows. Yeah. How does, how does one part of the chain actually affect the whole process?Comfy [00:14:52]: Are you talking on the model side specific?swyx [00:14:54]: Model specific, right? But like once you have your whole workflow based on a model, it's very hard to move.Comfy [00:15:01]: Uh, not, well, not really. Well, it depends on your, uh, depends on their specific kind of the workflow. Yeah.swyx [00:15:09]: So I do a lot of like text and image. Yeah.Comfy [00:15:12]: When you do change, like most workflows are kind of going to be complete. Yeah. It's just like, you might have to completely change your prompt completely change. Okay.swyx [00:15:24]: Well, I mean, then maybe the question is really about evals. Like what does the comfy community do for evals? Just, you know,Comfy [00:15:31]: Well, that they don't really do that. It's more like, oh, I think this image is nice. So that's, uh,swyx [00:15:38]: They just subscribe to Fofr AI and just see like, you know, what Fofr is doing. Yeah.Comfy [00:15:43]: Well, they just, they just generate like it. Like, I don't see anyone really doing it. Like, uh, at least on the comfy side, comfy users, they, it's more like, oh, generate images and see, oh, this one's nice. It's like, yeah, it's not, uh, like the, the more, uh, like, uh, scientific, uh, like, uh, like checking that's more on specifically on like model side. If, uh, yeah, but there is a lot of, uh, vibes also, cause it is a like, uh, artistic, uh, you can create a very good model that doesn't generate nice images. Cause most images on the internet are ugly. So if you, if that's like, if you just, oh, I have the best model at 10th giant, it's super smart. I created on all the, like I've trained on just all the images on the internet. The images are not going to look good. So yeah.Alessio [00:16:42]: Yeah.Comfy [00:16:43]: They're going to be very consistent. But yeah. People like, it's not going to be like the, the look that people are going to be expecting from, uh, from a model. So. Yeah.swyx [00:16:54]: Can we talk about LoRa's? Cause we thought we talked about models then like the next step is probably LoRa's. Before, I actually, I'm kind of curious how LoRa's entered the tool set of the image community because the LoRa paper was 2021. And then like, there was like other methods like textual inversion that was popular at the early SD stage. Yeah.Comfy [00:17:13]: I can't even explain the difference between that. Yeah. Textual inversions. That's basically what you're doing is you're, you're training a, cause well, yeah. Stable diffusion. You have the diffusion model, you have text encoder. So basically what you're doing is training a vector that you're going to pass to the text encoder. It's basically you're training a new word. Yeah.swyx [00:17:37]: It's a little bit like representation engineering now. Yeah.Comfy [00:17:40]: Yeah. Basically. Yeah. You're just, so yeah, if you know how like the text encoder works, basically you have, you take your, your words of your product, you convert those into tokens with the tokenizer and those are converted into vectors. Basically. Yeah. Each token represents a different vector. So each word presents a vector. And those, depending on your words, that's the list of vectors that get passed to the text encoder, which is just. Yeah. Yeah. I'm just a stack of, of attention. Like basically it's a very close to LLM architecture. Yeah. Yeah. So basically what you're doing is just training a new vector. We're saying, well, I have all these images and I want to know which word does that represent? And it's going to get like, you train this vector and then, and then when you use this vector, it hopefully generates. Like something similar to your images. Yeah.swyx [00:18:43]: I would say it's like surprisingly sample efficient in picking up the concept that you're trying to train it on. Yeah.Comfy [00:18:48]: Well, people have kind of stopped doing that even though back as like when I was at Stability, we, we actually did train internally some like textual versions on like T5 XXL actually worked pretty well. But for some reason, yeah, people don't use them. And also they might also work like, like, yeah, this is something and probably have to test, but maybe if you train a textual version, like on T5 XXL, it might also work with all the other models that use T5 XXL because same thing with like, like the textual inversions that, that were trained for SD 1.5, they also kind of work on SDXL because SDXL has the, has two text encoders. And one of them is the same as the, as the SD 1.5 CLIP-L. So those, they actually would, they don't work as strongly because they're only applied to one of the text encoders. But, and the same thing for SD3. SD3 has three text encoders. So it works. It's still, you can still use your textual version SD 1.5 on SD3, but it's just a lot weaker because now there's three text encoders. So it gets even more diluted. Yeah.swyx [00:20:05]: Do people experiment a lot on, just on the CLIP side, there's like Siglip, there's Blip, like do people experiment a lot on those?Comfy [00:20:12]: You can't really replace. Yeah.swyx [00:20:14]: Because they're trained together, right? Yeah.Comfy [00:20:15]: They're trained together. So you can't like, well, what I've seen people experimenting with is a long CLIP. So basically someone fine tuned the CLIP model to accept longer prompts.swyx [00:20:27]: Oh, it's kind of like long context fine tuning. Yeah.Comfy [00:20:31]: So, so like it's, it's actually supported in Core Comfy.swyx [00:20:35]: How long is long?Comfy [00:20:36]: Regular CLIP is 77 tokens. Yeah. Long CLIP is 256. Okay. So, but the hack that like you've, if you use stable diffusion 1.5, you've probably noticed, oh, it still works if I, if I use long prompts, prompts longer than 77 words. Well, that's because the hack is to just, well, you split, you split it up in chugs of 77, your whole big prompt. Let's say you, you give it like the massive text, like the Bible or something, and it would split it up in chugs of 77 and then just pass each one through the CLIP and then just cut anything together at the end. It's not ideal, but it actually works.swyx [00:21:26]: Like the positioning of the words really, really matters then, right? Like this is why order matters in prompts. Yeah.Comfy [00:21:33]: Yeah. Like it, it works, but it's, it's not ideal, but it's what people expect. Like if, if someone gives a huge prompt, they expect at least some of the concepts at the end to be like present in the image. But usually when they give long prompts, they, they don't, they like, they don't expect like detail, I think. So that's why it works very well.swyx [00:21:58]: And while we're on this topic, prompts waiting, negative comments. Negative prompting all, all sort of similar part of this layer of the stack. Yeah.Comfy [00:22:05]: The, the hack for that, which works on CLIP, like it, basically it's just for SD 1.5, well, for SD 1.5, the prompt waiting works well because CLIP L is a, is not a very deep model. So you have a very high correlation between, you have the input token, the index of the input token vector. And the output token, they're very, the concepts are very close, closely linked. So that means if you interpolate the vector from what, well, the, the way Comfy UI does it is it has, okay, you have the vector, you have an empty prompt. So you have a, a chunk, like a CLIP output for the empty prompt, and then you have the one for your prompt. And then it interpolates from that, depending on your prompt. Yeah.Comfy [00:23:07]: So that's how it, how it does prompt waiting. But this stops working the deeper your text encoder is. So on T5X itself, it doesn't work at all. So. Wow.swyx [00:23:20]: Is that a problem for people? I mean, cause I'm used to just move, moving up numbers. Probably not. Yeah.Comfy [00:23:25]: Well.swyx [00:23:26]: So you just use words to describe, right? Cause it's a bigger language model. Yeah.Comfy [00:23:30]: Yeah. So. Yeah. So honestly it might be good, but I haven't seen many complaints on Flux that it's not working. So, cause I guess people can sort of get around it with, with language. So. Yeah.swyx [00:23:46]: Yeah. And then coming back to LoRa's, now the, the popular way to, to customize models is LoRa's. And I saw you also support Locon and LoHa, which I've never heard of before.Comfy [00:23:56]: There's a bunch of, cause what, what the LoRa is essentially is. Instead of like, okay, you have your, your model and then you want to fine tune it. So instead of like, what you could do is you could fine tune the entire thing, but that's a bit heavy. So to speed things up and make things less heavy, what you can do is just fine tune some smaller weights, like basically two, two matrices that when you multiply like two low rank matrices and when you multiply them together, gives a, represents a difference between trained weights and your base weights. So by training those two smaller matrices, that's a lot less heavy. Yeah.Alessio [00:24:45]: And they're portable. So you're going to share them. Yeah. It's like easier. And also smaller.Comfy [00:24:49]: Yeah. That's the, how LoRa's work. So basically, so when, when inferencing you, you get an inference with them pretty efficiently, like how ComputeWrite does it. It just, when you use a LoRa, it just applies it straight on the weights so that there's only a small delay at the base, like before the sampling to when it applies the weights and then it just same speed as, as before. So for, for inference, it's, it's not that bad, but, and then you have, so basically all the LoRa types like LoHa, LoCon, everything, that's just different ways of representing that like. Basically, you can call it kind of like compression, even though it's not really compression, it's just different ways of represented, like just, okay, I want to train a different on the difference on the weights. What's the best way to represent that difference? There's the basic LoRa, which is just, oh, let's multiply these two matrices together. And then there's all the other ones, which are all different algorithms. So. Yeah.Alessio [00:25:57]: So let's talk about LoRa. Let's talk about what comfy UI actually is. I think most people have heard of it. Some people might've seen screenshots. I think fewer people have built very complex workflows. So when you started, automatic was like the super simple way. What were some of the choices that you made? So the node workflow, is there anything else that stands out as like, this was like a unique take on how to do image generation workflows?Comfy [00:26:22]: Well, I feel like, yeah, back then everyone was trying to make like easy to use interface. Yeah. So I'm like, well, everyone's trying to make an easy to use interface.swyx [00:26:32]: Let's make a hard to use interface.Comfy [00:26:37]: Like, so like, I like, I don't need to do that, everyone else doing it. So let me try something like, let me try to make a powerful interface that's not easy to use. So.swyx [00:26:52]: So like, yeah, there's a sort of node execution engine. Yeah. Yeah. And it actually lists, it has this really good list of features of things you prioritize, right? Like let me see, like sort of re-executing from, from any parts of the workflow that was changed, asynchronous queue system, smart memory management, like all this seems like a lot of engineering that. Yeah.Comfy [00:27:12]: There's a lot of engineering in the back end to make things, cause I was always focused on making things work locally very well. Cause that's cause I was using it locally. So everything. So there's a lot of, a lot of thought and working by getting everything to run as well as possible. So yeah. ConfUI is actually more of a back end, at least, well, not all the front ends getting a lot more development, but, but before, before it was, I was pretty much only focused on the backend. Yeah.swyx [00:27:50]: So v0.1 was only August this year. Yeah.Comfy [00:27:54]: With the new front end. Before there was no versioning. So yeah. Yeah. Yeah.swyx [00:27:57]: And so what was the big rewrite for the 0.1 and then the 1.0?Comfy [00:28:02]: Well, that's more on the front end side. That's cause before that it was just like the UI, what, cause when I first wrote it, I just, I said, okay, how can I make, like, I can do web development, but I don't like doing it. Like what's the easiest way I can slap a node interface on this. And then I found this library. Yeah. Like JavaScript library.swyx [00:28:26]: Live graph?Comfy [00:28:27]: Live graph.swyx [00:28:28]: Usually people will go for like react flow for like a flow builder. Yeah.Comfy [00:28:31]: But that seems like too complicated. So I didn't really want to spend time like developing the front end. So I'm like, well, oh, light graph. This has the whole node interface. So, okay. Let me just plug that into, to my backend.swyx [00:28:49]: I feel like if Streamlit or Gradio offered something that you would have used Streamlit or Gradio cause it's Python. Yeah.Comfy [00:28:54]: Yeah. Yeah. Yeah.Comfy [00:29:00]: Yeah.Comfy [00:29:14]: Yeah. logic and your backend logic and just sticks them together.swyx [00:29:20]: It's supposed to be easy for you guys. If you're a Python main, you know, I'm a JS main, right? Okay. If you're a Python main, it's supposed to be easy.Comfy [00:29:26]: Yeah, it's easy, but it makes your whole software a huge mess.swyx [00:29:30]: I see, I see. So you're mixing concerns instead of separating concerns?Comfy [00:29:34]: Well, it's because... Like frontend and backend. Frontend and backend should be well separated with a defined API. Like that's how you're supposed to do it. Smart people disagree. It just sticks everything together. It makes it easy to like a huge mess. And also it's, there's a lot of issues with Gradio. Like it's very good if all you want to do is just get like slap a quick interface on your, like to show off your ML project. Like that's what it's made for. Yeah. Like there's no problem using it. Like, oh, I have my, I have my code. I just wanted a quick interface on it. That's perfect. Like use Gradio. But if you want to make something that's like a real, like real software that will last a long time and will be easy to maintain, then I would avoid it. Yeah.swyx [00:30:32]: So your criticism is Streamlit and Gradio are the same. I mean, those are the same criticisms.Comfy [00:30:37]: Yeah, Streamlit I haven't used as much. Yeah, I just looked a bit.swyx [00:30:43]: Similar philosophy.Comfy [00:30:44]: Yeah, it's similar. It's just, it just seems to me like, okay, for quick, like AI demos, it's perfect.swyx [00:30:51]: Yeah. Going back to like the core tech, like asynchronous queues, slow re-execution, smart memory management, you know, anything that you were very proud of or was very hard to figure out?Comfy [00:31:00]: Yeah. The thing that's the biggest pain in the ass is probably the memory management. Yeah.swyx [00:31:05]: Were you just paging models in and out or? Yeah.Comfy [00:31:08]: Before it was just, okay, load the model, completely unload it. Then, okay, that, that works well when you, your model are small, but if your models are big and it takes sort of like, let's say someone has a, like a, a 4090, and the model size is 10 gigabytes, that can take a few seconds to like load and load, load and load, so you want to try to keep things like in memory, in the GPU memory as much as possible. What Comfy UI does right now is it. It tries to like estimate, okay, like, okay, you're going to sample this model, it's going to take probably this amount of memory, let's remove the models, like this amount of memory that's been loaded on the GPU and then just execute it. But so there's a fine line between just because try to remove the least amount of models that are already loaded. Because as fans, like Windows drivers, and one other problem is the NVIDIA driver on Windows by default, because there's a way to, there's an option to disable that feature, but by default it, like, if you start loading, you can overflow your GPU memory and then it's, the driver's going to automatically start paging to RAM. But the problem with that is it's, it makes everything extremely slow. So when you see people complaining, oh, this model, it works, but oh, s**t, it starts slowing down a lot, that's probably what's happening. So it's basically you have to just try to get, use as much memory as possible, but not too much, or else things start slowing down, or people get out of memory, and then just find, try to find that line where, oh, like the driver on Windows starts paging and stuff. Yeah. And the problem with PyTorch is it's, it's high levels, don't have that much fine-grained control over, like, specific memory stuff, so kind of have to leave, like, the memory freeing to, to Python and PyTorch, which is, can be annoying sometimes.swyx [00:33:32]: So, you know, I think one thing is, as a maintainer of this project, like, you're designing for a very wide surface area of compute, like, you even support CPUs.Comfy [00:33:42]: Yeah, well, that's... That's just, for PyTorch, PyTorch supports CPUs, so, yeah, it's just, that's not, that's not hard to support.swyx [00:33:50]: First of all, is there a market share estimate, like, is it, like, 70% NVIDIA, like, 30% AMD, and then, like, miscellaneous on Apple, Silicon, or whatever?Comfy [00:33:59]: For Comfy? Yeah. Yeah, and, yeah, I don't know the market share.swyx [00:34:03]: Can you guess?Comfy [00:34:04]: I think it's mostly NVIDIA. Right. Because, because AMD, the problem, like, AMD works horribly on Windows. Like, on Linux, it works fine. It's, it's lower than the price equivalent NVIDIA GPU, but it works, like, you can use it, you generate images, everything works. On Linux, on Windows, you might have a hard time, so, that's the problem, and most people, I think most people who bought AMD probably use Windows. They probably aren't going to switch to Linux, so... Yeah. So, until AMD actually, like, ports their, like, raw cam to, to Windows properly, and then there's actually PyTorch, I think they're, they're doing that, they're in the process of doing that, but, until they get it, they get a good, like, PyTorch raw cam build that works on Windows, it's, like, they're going to have a hard time. Yeah.Alessio [00:35:06]: We got to get George on it. Yeah. Well, he's trying to get Lisa Su to do it, but... Let's talk a bit about, like, the node design. So, unlike all the other text-to-image, you have a very, like, deep, so you have, like, a separate node for, like, clip and code, you have a separate node for, like, the case sampler, you have, like, all these nodes. Going back to, like, the making it easy versus making it hard, but, like, how much do people actually play with all the settings, you know? Kind of, like, how do you guide people to, like, hey, this is actually going to be very impactful versus this is maybe, like, less impactful, but we still want to expose it to you?Comfy [00:35:40]: Well, I try to... I try to expose, like, I try to expose everything or, but, yeah, at least for the, but for things, like, for example, for the samplers, like, there's, like, yeah, four different sampler nodes, which go in easiest to most advanced. So, yeah, if you go, like, the easy node, the regular sampler node, that's, you have just the basic settings. But if you use, like, the sampler advanced... If you use, like, the custom advanced node, that, that one you can actually, you'll see you have, like, different nodes.Alessio [00:36:19]: I'm looking it up now. Yeah. What are, like, the most impactful parameters that you use? So, it's, like, you know, you can have more, but, like, which ones, like, really make a difference?Comfy [00:36:30]: Yeah, they all do. They all have their own, like, they all, like, for example, yeah, steps. Usually you want steps, you want them to be as low as possible. But you want, if you're optimizing your workflow, you want to, you lower the steps until, like, the images start deteriorating too much. Because that, yeah, that's the number of steps you're running the diffusion process. So, if you want things to be faster, lower is better. But, yeah, CFG, that's more, you can kind of see that as the contrast of the image. Like, if your image looks too bursty. Then you can lower the CFG. So, yeah, CFG, that's how, yeah, that's how strongly the, like, the negative versus positive prompt. Because when you sample a diffusion model, it's basically a negative prompt. It's just, yeah, positive prediction minus negative prediction.swyx [00:37:32]: Contrastive loss. Yeah.Comfy [00:37:34]: It's positive minus negative, and the CFG does the multiplier. Yeah. Yeah. Yeah, so.Alessio [00:37:41]: What are, like, good resources to understand what the parameters do? I think most people start with automatic, and then they move over, and it's, like, snap, CFG, sampler, name, scheduler, denoise. Read it.Comfy [00:37:53]: But, honestly, well, it's more, it's something you should, like, try out yourself. I don't know, you don't necessarily need to know how it works to, like, what it does. Because even if you know, like, CFGO, it's, like, positive minus negative prompt. Yeah. So the only thing you know at CFG is if it's 1.0, then that means the negative prompt isn't applied. It also means sampling is two times faster. But, yeah. But other than that, it's more, like, you should really just see what it does to the images yourself, and you'll probably get a more intuitive understanding of what these things do.Alessio [00:38:34]: Any other nodes or things you want to shout out? Like, I know the animate diff IP adapter. Those are, like, some of the most popular ones. Yeah. What else comes to mind?Comfy [00:38:44]: Not nodes, but there's, like, what I like is when some people, sometimes they make things that use ComfyUI as their backend. Like, there's a plugin for Krita that uses ComfyUI as its backend. So you can use, like, all the models that work in Comfy in Krita. And I think I've tried it once. But I know a lot of people use it, and it's probably really nice, so.Alessio [00:39:15]: What's the craziest node that people have built, like, the most complicated?Comfy [00:39:21]: Craziest node? Like, yeah. I know some people have made, like, video games in Comfy with, like, stuff like that. So, like, someone, like, I remember, like, yeah, last, I think it was last year, someone made, like, a, like, Wolfenstein 3D in Comfy. Of course. And then one of the inputs was, oh, you can generate a texture, and then it changes the texture in the game. So you can plug it to, like, the workflow. And there's a lot of, if you look there, there's a lot of crazy things people do, so. Yeah.Alessio [00:39:59]: And now there's, like, a node register that people can use to, like, download nodes. Yeah.Comfy [00:40:04]: Like, well, there's always been the, like, the ComfyUI manager. Yeah. But we're trying to make this more, like, I don't know, official, like, with, yeah, with the node registry. Because before the node registry, the, like, okay, how did your custom node get into ComfyUI manager? That's the guy running it who, like, every day he searched GitHub for new custom nodes and added dev annually to his custom node manager. So we're trying to make it less effortless. So we're trying to make it less effortless for him, basically. Yeah.Alessio [00:40:40]: Yeah. But I was looking, I mean, there's, like, a YouTube download node. There's, like, this is almost like, you know, a data pipeline more than, like, an image generation thing at this point. It's, like, you can get data in, you can, like, apply filters to it, you can generate data out.Comfy [00:40:54]: Yeah. You can do a lot of different things. Yeah. So I'm thinking, I think what I did is I made it easy to make custom nodes. So I think that helped a lot. I think that helped a lot for, like, the ecosystem because it is very easy to just make a node. So, yeah, a bit too easy sometimes. Then we have the issue where there's a lot of custom node packs which share similar nodes. But, well, that's, yeah, something we're trying to solve by maybe bringing some of the functionality into the core. Yeah. Yeah. Yeah.Alessio [00:41:36]: And then there's, like, video. People can do video generation. Yeah.Comfy [00:41:40]: Video, that's, well, the first video model was, like, stable video diffusion, which was last, yeah, exactly last year, I think. Like, one year ago. But that wasn't a true video model. So it was...swyx [00:41:55]: It was, like, moving images? Yeah.Comfy [00:41:57]: I generated video. What I mean by that is it's, like, it's still 2D Latents. It's basically what I'm trying to do. So what they did is they took SD2, and then they added some temporal attention to it, and then trained it on videos and all. So it's kind of, like, animated, like, same idea, basically. Why I say it's not a true video model is that you still have, like, the 2D Latents. Like, a true video model, like Mochi, for example, would have 3D Latents. Mm-hmm.Alessio [00:42:32]: Which means you can, like, move through the space, basically. It's the difference. You're not just kind of, like, reorienting. Yeah.Comfy [00:42:39]: And it's also, well, it's also because you have a temporal VAE. Mm-hmm. Also, like, Mochi has a temporal VAE that compresses on, like, the temporal direction, also. So that's something you don't have with, like, yeah, animated diff and stable video diffusion. They only, like, compress spatially, not temporally. Mm-hmm. Right. So, yeah. That's why I call that, like, true video models. There's, yeah, there's actually a few of them, but the one I've implemented in comfy is Mochi, because that seems to be the best one so far. Yeah.swyx [00:43:15]: We had AJ come and speak at the stable diffusion meetup. The other open one I think I've seen is COG video. Yeah.Comfy [00:43:21]: COG video. Yeah. That one's, yeah, it also seems decent, but, yeah. Chinese, so we don't use it. No, it's fine. It's just, yeah, I could. Yeah. It's just that there's a, it's not the only one. There's also a few others, which I.swyx [00:43:36]: The rest are, like, closed source, right? Like, Cling. Yeah.Comfy [00:43:39]: Closed source, there's a bunch of them. But I mean, open. I've seen a few of them. Like, I can't remember their names, but there's COG videos, the big, the big one. Then there's also a few of them that released at the same time. There's one that released at the same time as SSD 3.5, same day, which is why I don't remember the name.swyx [00:44:02]: We should have a release schedule so we don't conflict on each of these things. Yeah.Comfy [00:44:06]: I think SD 3.5 and Mochi released on the same day. So everything else was kind of drowned, completely drowned out. So for some reason, lots of people picked that day to release their stuff.Comfy [00:44:21]: Yeah. Which is, well, shame for those. And I think Omnijet also released the same day, which also seems interesting. Yeah. Yeah.Alessio [00:44:30]: What's Comfy? So you are Comfy. And then there's like, comfy.org. I know we do a lot of things for, like, news research and those guys also have kind of like a more open source thing going on. How do you work? Like you mentioned, you mostly work on like, the core piece of it. And then what...Comfy [00:44:47]: Maybe I should fade it in because I, yeah, I feel like maybe, yeah, I only explain part of the story. Right. Yeah. Maybe I should explain the rest. So yeah. So yeah. Basically, January, that's when the first January 2023, January 16, 2023, that's when Amphi was first released to the public. Then, yeah, did a Reddit post about the area composition thing somewhere in, I don't remember exactly, maybe end of January, beginning of February. And then someone, a YouTuber, made a video about it, like Olivio, he made a video about Amphi in March 2023. I think that's when it was a real burst of attention. And by that time, I was continuing to develop it and it was getting, people were starting to use it more, which unfortunately meant that I had first written it to do like experiments, but then my time to do experiments went down. It started going down, because people were actually starting to use it then. Like, I had to, and I said, well, yeah, time to add all these features and stuff. Yeah, and then I got hired by Stability June, 2023. Then I made, basically, yeah, they hired me because they wanted the SD-XL. So I got the SD-XL working very well withітhe UI, because they were experimenting withámphi.house.com. Actually, the SDX, how the SDXL released worked is they released, for some reason, like they released the code first, but they didn't release the model checkpoint. So they released the code. And then, well, since the research was related to code, I released the code in Compute 2. And then the checkpoints were basically early access. People had to sign up and they only allowed a lot of people from edu emails. Like if you had an edu email, like they gave you access basically to the SDXL 0.9. And, well, that leaked. Right. Of course, because of course it's going to leak if you do that. Well, the only way people could easily use it was with Comfy. So, yeah, people started using. And then I fixed a few of the issues people had. So then the big 1.0 release happened. And, well, Comfy UI was the only way a lot of people could actually run it on their computers. Because it just like automatic was so like inefficient and bad that most people couldn't actually, like it just wouldn't work. Like because he did a quick implementation. So people were forced. To use Comfy UI, and that's how it became popular because people had no choice.swyx [00:47:55]: The growth hack.Comfy [00:47:56]: Yeah.swyx [00:47:56]: Yeah.Comfy [00:47:57]: Like everywhere, like people who didn't have the 4090, they had like, who had just regular GPUs, they didn't have a choice.Alessio [00:48:05]: So yeah, I got a 4070. So think of me. And so today, what's, is there like a core Comfy team or?Comfy [00:48:13]: Uh, yeah, well, right now, um, yeah, we are hiring. Okay. Actually, so right now core, like, um, the core core itself, it's, it's me. Uh, but because, uh, the reason where folks like all the focus has been mostly on the front end right now, because that's the thing that's been neglected for a long time. So, uh, so most of the focus right now is, uh, all on the front end, but we are, uh, yeah, we will soon get, uh, more people to like help me with the actual backend stuff. Yeah. So, no, I'm not going to say a hundred percent because that's why once the, once we have our V one release, which is because it'd be the package, come fee-wise with the nice interface and easy to install on windows and hopefully Mac. Uh, yeah. Yeah. Once we have that, uh, we're going to have to, lots of stuff to do on the backend side and also the front end side, but, uh.Alessio [00:49:14]: What's the release that I'm on the wait list. What's the timing?Comfy [00:49:18]: Uh, soon. Uh, soon. Yeah, I don't want to promise a release date. We do have a release date we're targeting, but I'm not sure if it's public. Yeah, and we're still going to continue doing the open source, making MPUI the best way to run stable infusion models. At least the open source side, it's going to be the best way to run models locally. But we will have a few things to make money from it, like cloud inference or that type of thing. And maybe some things for some enterprises.swyx [00:50:08]: I mean, a few questions on that. How do you feel about the other comfy startups?Comfy [00:50:11]: I mean, I think it's great. They're using your name. Yeah, well, it's better they use comfy than they use something else. Yeah, that's true. It's fine. We're going to try not to... We don't want to... We want people to use comfy. Like I said, it's better that people use comfy than something else. So as long as they use comfy, I think it helps the ecosystem. Because more people, even if they don't contribute directly, the fact that they are using comfy means that people are more likely to join the ecosystem. So, yeah.swyx [00:50:57]: And then would you ever do text?Comfy [00:50:59]: Yeah, well, you can already do text with some custom nodes. So, yeah, it's something we like. Yeah, it's something I've wanted to eventually add to core, but it's more like not a very... It's a very high priority. But because a lot of people use text for prompt enhancement and other things like that. So, yeah, it's just that my focus has always been on diffusion models. Yeah, unless some text diffusion model comes out.swyx [00:51:30]: Yeah, David Holtz is investing a lot in text diffusion.Comfy [00:51:34]: Yeah, well, if a good one comes out, then we'll probably implement it since it fits with the whole...swyx [00:51:39]: Yeah, I mean, I imagine it's going to be a close source to Midjourney. Yeah.Comfy [00:51:43]: Well, if an open one comes out, then I'll probably implement it.Alessio [00:51:54]: Cool, comfy. Thanks so much for coming on. This was fun. Bye. Get full access to Latent Space at www.latent.space/subscribe

HOT NEWS! The FEC Highland Fling is here!  Yes folks, come ride with Simon and Martin in Scotland in May 2025 – we've booked an entire hotel in the heart of the Highlands as a base for three days of riding the most stunning loops around the most iconic routes in the UK. It's majestic, it's mind-blowing, it's the best riding – and the best hospitality – you'll get in 2025.  The FEC Highland Fling starts with a grand ride-in on Friday 2nd May through Glen Coe up to the hotel near Garve. After an evening of greetings and meetings, we'll spend the next three days exploring the finest roads and scenery Scotland has to offer – the north coast, west coast, and across to the Cairngorms, talking in all the Highland hits along the way. And, on the final night (Monday 5th May), Martin and Simon will host a special live episode of Front End Chatter.  To register your interest in the FC Highland Fling, please send an email to anything@frontendchatter.com titled "I'm interested in the FEC Highland Fling, please send me more info." We look forward to seeing you in Scotland in May! Meanwhile.... Hello and welcome to E206 of Front End Chatter, the UK's most Christmassy (he means 'Festive' – Ed) motorcycling podcast, brought to you gift-wrapped in last week's MCN by Simon Humbug Hargreaves and Martin Ho Ho Ho Fitz-Gibbons, supported as ever by the bike insurance baubles at Bennetts, and their multimedia minions at BikeSocial.co.uk. Get your insurance with Bennetts because their industry-wide offers and discounts will pay you back big time in 2025. Become a BikeSocial Member, take advantage, get involved, come to a discounted trackday and keep your eyes on your inbox for amazing events with which you can get involved. And on this week's FEC we have: • our fave bikes of 2024 (and a few of 2025) • more KTM woes, plus does talking about it make it worse?  • the last new bike news of 2024, Ducati's down-sized V2 Multi • plus a whole heap of nattering on topics raised by you, the FECers, sent in via email to the FEC-Sac, to anything@frontendchatter.com Please keep your thoughts and ideas and musings and fantasies coming in!  Thanks for listening, and see you in Scotland in May!  Bsky @sihbikes.bsky.social @mufga.bsky.social Insta simonhbikes mufga

Magic Mind limited offer: up to 48% off 1st subscription or 20% off one-time purchase: https://www.magicmind.com/ALANB20   Alan interviews Miguel Gatmaytan. Miguel Gatmaytan loved computer games as a youth – so he started coding. After graduating from college - he helped innovators with game apps. Today he helps inventors to develop apps and games. Make sure to subscribe to the podcast at Apple Podcasts, or wherever you get your podcasts. Website www.Gatmaytan.com  

LISTEN TO MY FULL PODCAST HERE!

Scott and Wes dive into the State of Frontend 2024 Survey, breaking down the latest trends, tools, and frameworks shaping the developer ecosystem. Tune in as they react to hot takes on frameworks, state management, hosting, and what's next for frontend devs! Show Notes 00:00 Welcome to Syntax! 00:53 Brought to you by Sentry.io. 01:15 About the survey. Follow along! State of Frontend Survey 02:10 Frameworks. 06:15 Rendering frameworks. 07:35 State management. 09:14 Other libraries. Just: Dependency-free Utilities. 13:34 Data. Syntax Episode 453. Syntax Episode 833. 16:39 Hosting. AWS Amplify. 19:51 Continuous Integration. 21:30 Micro-frontends. 23:25 Package Managers. pnpm Link Workspace Packages. Corepack. 28:35 JS Runtimes. 29:47 Typescript. 33:13 Browser Technologies. 35:05 What is app property? 38:20 Progressive Web Apps. 40:11 Styling tools. 43:17 Testing. 45:39 Code editors. 49:02 Build tools. 49:17 Linting tools. 50:26 Operating systems. 51:17 The future trends. 54:14 Sick Picks + Shameless Plugs. Sick Picks Scott: Candle Warmer. Wes: Flighty iOS App. Shameless Plugs Scott: Syntax on Bluesky 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