| • Discussion on State of HTML survey | |
| • Next.js dominates static site generators with 39% usage | |
| • Other popular static site generators include Astro, Nuxt, Gatsby, and Jekyll | |
| • Legacy site generators like Hugo and Jekyll still in use despite rise of JS-based tools | |
| • Jekyll's history and popularity due to Tom Preston-Werner's "Blogging like a hacker" post | |
| • Static site generators' benefits in avoiding the Slashdot effect and server rendering issues | |
| • The 11ty community hosted a virtual event that went well | |
| • AI tools are being widely used by developers to help with code generation | |
| • ChatGPT is the most popular AI tool, used by 52% of respondents | |
| • Other AI tools mentioned include Copilot and Gemini (formerly Bard) | |
| • 62% of developers in the survey use some form of AI tool for code generation | |
| • Discussion about the challenges of debugging JavaScript arrays | |
| • Kevin Ball shared an experience using ChatGPT to solve a complex issue | |
| • Jerod Santo discussed writing a Node server using modern Node features | |
| • The effectiveness of AI-based code generators is highlighted, especially for one-off tasks | |
| • Changelog News' email template design issues and MJML as a solution | |
| • Node 22 release: requiring ESModules, built-in WebSocket client, V8 updates, and experimental process-based permissions | |
| • React compiler open-sourced for optimizing React apps at build time | |
| • Comparison of React's new tooling to Svelte, Angular, and Qwik's approaches | |
| • Different distributions of React compiler require manual compilation | |
| • React 19 is in beta as of April 25th and includes new features such as production-ready Server Components | |
| • New concepts introduced include actions, transitions, and the useOptimistic hook to handle state transitions | |
| • Use method introduced for smoother developer experience around Suspend | |
| • Discussion on whether the beta stage means the software is ready for adoption | |
| • The React 19 beta release is not suitable for regular developers and should be used only by libraries to prepare for React 19. | |
| • The npm package management ecosystem has a "whack a mole problem" with supply chain security vulnerabilities. | |
| • A new package management system called Vault, backed by investors including JS Party folks and other notable JavaScript community members, aims to create a secure and verifiable ecosystem. | |
| • This may lead to competing registries or packaging solutions, including one from the creator of Node and another from the original npm creator. | |
| • Gulp, a task runner, has released a developer survey and is still relevant despite being largely outdated. | |
| • Evolution of build systems: WebPack and Vite | |
| • History of task runners: Grunt, Gulp, and their differences (file-based vs streaming approach) | |
| • Gulp's current state: still widely used, with over 1 million downloads per week, and an ongoing survey to understand its community needs | |
| • The challenge of understanding how people are using a tool, especially when it's being used in many different ways by a large user base | |
| • Importance of hearing from all users, not just power users or those who report issues on GitHub | |
| • Boring technology that lasts: examples include WordPress, jQuery, and React | |
| • Discussion of Redka, a reimplementation of Redis with a SQLite backend | |
| • Comparison of Node.js to Deno and Bun, and evaluation of their reliability | |
| • Use of AI in projects, including potential benefits and risks | |
| • Importance of validating output from AI tools due to potential inaccuracies | |
| • Introduction to Kevin Ball's work on AI coaching tools at Mento |