Jerod, KBall & Nick discuss the latest news: Devin, Astro DB, The JavaScript Registry, Tailwind 4 & Angular merging with Wiz. Oh, and a surprise mini-game of HeadLIES!

High expectations for performance in both life and work are common, but what do you do when you get stuck and you’re not able to achieve the results you desire? In this episode, Mireille and Adam talk through the different aspects of perfectionism and ways in which is can be adaptive and helpful and other ways in which it poses additional challenges. What happens when we avoid the possibility of failure as opposed to simply having high standards for our performance? How can we begin to focus on healthy striving as opposed to reaching for perfection?

Matched from the episode's transcript 👇

This is a minimal implementation of DALL·E Mini. It has been stripped to the bare essentials necessary for doing inference, and converted to PyTorch. The only third party dependencies are torch for the torch model and flax for the flax model.

How much mini-er can it get from here? 🤔

DockerSlim promises a lot:

docker-slim will optimize and secure your containers by understanding your application and what it needs using various analysis techniques. It will throw away what you don’t need reducing the attack surface for your container. What if you need some of those extra things to debug your container? You can use dedicated debugging side-car containers for that.

Their minification examples are impressive…

Victor Zhou uses a lot of SVGs on his blog. Do you? So now he optimizes their size as part of his build process. Do you?

62 SVGs minified, reducing the total size from 459322 bytes to 208897 bytes, a reduction of 54.5%! That’s a total of 250 KB, or 4 KB per SVG. Keep in mind that all of my SVGs were already saved in the Optimized SVG format - these savings were on top of already optimized SVGs. If you haven’t thought about minifying your SVGs before, chances are you’d see much more drastic results.

Alex Russell answers the question, “If not React, then what?” Csaba Okrona identifies four core problems that create and reinforce knowledge silos, Rob Koch’s Markwhen is like Markdown for timelines, Jeff Geerling is quite impressed by Apple’s latest iteration on the Mac mini & Sylvain Kerkour took the time to draw a comparison of Amazon’s O.G. S3 service with Cloudflare’s R2 competitor.

Matt Asay thinks the open source licensing war is over, LangUI is an open source Tailwind component library for your AI chat app, Ivan Kuleshov modded a Mac mini to run via PoE, Apple joins Pixar and others in the Alliance for OpenUSD & John D. Cook says sometimes you shouldn’t pick the best tool for the job.

Asahi Linux is a project and community with the goal of porting Linux to Apple Silicon Macs, starting with the 2020 M1 Mac Mini, MacBook Air, and MacBook Pro.

Our goal is not just to make Linux run on these machines but to polish it to the point where it can be used as a daily OS. Doing this requires a tremendous amount of work, as Apple Silicon is an entirely undocumented platform. In particular, we will be reverse engineering the Apple GPU architecture and developing an open-source driver for it.

Asahi Linux is developed by a thriving community of free and open source software developers.

Yes, please!

Taco de Wolff:

This is about the fastest minifier for web formats and is written in Go. For example, it can minify JS files at about 25MB/s, which is orders of magnitude faster than existing solutions that are typically 100-300 kB/s. There is also a command line tool that can be incorporated in your setup easily.

A fun walkthrough of creating a mini data viz component in React, which teaches useful concepts like drawing with SVG and d3.js scales.

This repo contains the source code for [the Udemy course](Build 20 mini frontend projects from scratch with HTML5, CSS & JavaScript (No frameworks or libraries)) of the same name. Each mini project has its own README and live demo, too.

Adam, Jerod, and Tim get together to put a spotlight on Apple’s October 30th Mac/iPad event from a developer’s perspective. They cover the specs of the new MacBook Air and the viability of having it as a development machine, the new Mac Mini in the ever popular Space Gray, and whether or not Tim will be able to stop pulling his hair out to find an affordable, yet powerful desktop machine with it, and the gorgeous new iPad Pro.

Why use Day.js?

• 🕒 Familiar Moment.js API & patterns
• 💪 Immutable
• 🔥 Chainable
• 📦 2kb mini library
• 👫 All browsers support

It’s worth noting that the author doesn’t claim 100% API compatibility with Moment.js, but they say it’s close enough that “If you use Moment.js, you already know how to use Day.js.”

If your app targets modern browsers and is currently packing Moment.js’ 16.4kb in its JS bundle, maybe you can get by with Day.js’ 2kb instead…

Layout Land is a new YouTube channel from Mozilla and Jen Simmons focused on helping you learn about the new layout possibilities in web design.

If you’re looking to use CSS Grid but you need to support IE users, then you should check out this video and the rest of the series when you’re done. New videos every Tuesday and Thursday.

People always ask, “How can I dare to use this new CSS, when I need to support IE users?” It is very important to make sure every user can do what they came to your website to do, whether or not their browser supports the hot, new CSS you want to use. CSS Grid shipped in March 2017, and is already supported by the vast majority of web browsers in use. But there is a significant portion of users who do not have support for CSS Grid — not just IE, but also UC, Samsung Internet, Opera mini, QQ, and more. So can we use CSS Grid? How do we support these old browsers and use CSS Grid?

Tablesaw is a group of plugins by Zach Leatherman of Filament Group that help you build responsive HTML tables. It's always nice to see solid solutions to problems all web developers share.

Here's a gif of their "stack" table in action:

Check the README for more table modes, IE8 support, and even a mini map!

From the project homepage:

Sass Media Queries is a collection of useful media queries mixins (including iOS devices like iPhones and iPads) for Sass 3.2.0+

TL;DR

Sass Media Queries adds support for @media query Sass mixins (including iOS devices like iPhones and iPads) for Sass 3.2.0+, and is also Compass and Bourbon safe.

Requirements:
  Sass 3.2.0+

Version:
  2.1                                     // developed on 16/02/2013

Variables:
  $units: 1px;                            // default units for 'screen' mixins - it must include a digit!

Mixins:
  @include min-screen(width)              // shortcut for @media screen and (min-width ...)
  @include max-screen(width)              // shortcut for @media screen and (max-width ...)
  @include screen(min-width, max-width)   // shortcut for @media screen and (min-width ...) and (max-width ...)
  ---
  @include iphone3                        // only iPhone (2, 3G, 3GS) landscape & portrait
  @include iphone3-landscape              // only iPhone (2, 3G, 3GS) only landscape
  @include iphone3-portrait               // only iPhone (2, 3G, 3GS) only portrait
  ---
  @include iphone4                        // only iPhone (4, 4S) landscape & portrait
  @include iphone4-landscape              // only iPhone (4, 4S) only landscape
  @include iphone4-portrait               // only iPhone (4, 4S) only portrait
  ---
  @include iphone5                        // only iPhone (5) landscape & portrait
  @include iphone5-landscape              // only iPhone (5) only landscape
  @include iphone5-portrait               // only iPhone (5) only portrait
  ---
  @include ipad                           // only iPad (1, 2, Mini) landscape & portrait
  @include ipad-landscape                 // only iPad (1, 2, Mini) only landscape
  @include ipad-portrait                  // only iPad (1, 2, Mini) only portrait
  ---
  @include ipad-retina                    // only iPad (3, 4) landscape & portrait
  @include ipad-retina-landscape          // only iPad (3, 4) only landscape
  @include ipad-retina-portrait           // only iPad (3, 4) only portrait
  ---
  @include retina                         // devices with retina

Now it’s easy to do stuff like:

@include min-screen(320)  { ... }
@include max-screen(1024) { ... }
@include screen(320, 640) { ... }

And get back this when compiled to CSS:

@media screen and ( min-width: 320px) ) { ... }
@media screen and ( max-width: 1024px ) { ... }
@media screen and ( min-width: 320px ) and ( max-width: 640px ) { ... }

Check out the project from Rafal Bromirski on GitHub and also the simple, yet neat “resize me” demo.

Discuss on Hacker News if you must.

Nodefront from Karthik Viswanathan aims to make a front-end developer’s life easier. Built in Node.js, Nodefront bundles a local web server for serving up HTML, CSS, and JavaScript assets and supports live reloading via web sockets. Additionally it ships with a command line interface:

• nodefront compile - Compiles Jade and Stylus files to HTML and CSS. Can compile upon modification, serve files on localhost, and even automatically refresh the browser/styles when files are changed.

• nodefront fetch - Automatically fetches CSS/JS libraries for use in your project. Provides an interactive mode to add new libraries.

• nodefront insert - Inserts CSS/JS libraries directly into your HTML or Jade files.

• nodefront minify - Minifies CSS and JS files. Can also optimize JPG and PNG images.

Karthik has put together a twenty minute screencast for a full demonstration.

Check out the project web site or source on GitHub for more.

Caolan McMahon, the creator of Async, has released a new project called Jam. After using this project for a short while, I can say this project has huge potential. It is a package management tool that allows you to install, use and compile (minify) JavaScript libraries. Jam is a browser-focused project that uses RequireJS (AMD Modules) to load your website’s requirements.

Installation is simple:

npm install -g jamjs

Likewise, installing libraries is easy:

jam install jquery

Finally, you use the RequireJS to include the libraries:

<script src="jam/require.js"></script>
<script>
  require(['query'], function($){
    console.log("jQuery loaded!");
  });
</script>

One of the coolest features is the compilation, which will package all (optionally a specific set) of your libraries with RequireJS and allow you to load the optimized library as one optimized file.

jam compile jam/compiled.min.js

Then include compiled.min.js instead of require.js, the rest works like before:

<script src="jam/compiled.min.js"></script>
<script>
  require(['query'], function($){
    console.log("optimized jQuery loaded!");
  });
</script>

If you have a library you would like added as a package, feel free to fork the project and add it in. If, in the process, you run into conflicts or issues with NPM’s package.json, Caolan wants to hear about it!

Head on over to the project page or browse the source on GitHub.

Grunt is a project that allows you to use JavaScript to configure and run command line tasks. It is installed as an npm module, and very simple to get started with. If you have Node.js and npm installed, simply run:

npm install -g grunt

Some of the common tasks include: JavaScript Lint, QUnit,
minify, JSHint and file concatenation.

Any project that has grunt.js in it’s root (or subdirectories) can use grunt tasks. An example configuration to use grunt lint:

module.exports = function(grunt){
  grunt.initConfig({
    lint: {
      all: ['grunt.js', 'lib/**/*.js''test/**/*.js']
    }
  });
};

Whenever you run grunt lint in this project, the array of files (grunt.js, every JavaScript file in lib/ and every JavaScript file in test/) will be run through JavaScript Lint.

For some extra grunts and giggles, you can checkout grunt’s own gruntfile. They showcase some common uses and are very self explanatory.

As a disclaimer, grunt is currently in beta, and could possibly (will probably) change before 1.0. The good news is the changes will be based on your feedback. Head on over to GitHub to browse the source code and help get this project to it’s final release!

After 15 beta releases, Sprockets has finally released the big 2.0.

Why’s this a big deal? Well, Sprockets is the gem that’s powering the new asset pipeline in Rails 3.1. It can automatically process, minify, combine, and serve all of your assets in a variety of formats.

If you’re using Rails, I’d recommend upgrading your application to Rails 3.1. Even though it’s still just an RC release, the final is about to come very soon. Then, sprockets is all set up for you. If you’re not on Rails, then you should check out this awesome blog post by Envy Labs. It’ll get you going. Of course, you don’t need to use the Git URL now that version 2 is out.

Check out the source on GitHub and the readme for more details.

Thanks to work by Google and Yahoo, we’re all better informed about how to speed up our web pages. For those on Apache, Google has made it easier to implement these ideas at the Apache Module level. For those running on Ruby web frameworks, Julio Cesar offers up the same goodness as Rack middleware.

Rack Pagespeed offers some HTML output filters to help you implement page optimization best practices with minimal effort. To get started, install the gem:

gem install rack-pagespeed

For Sinatra, Rack, or Padrino apps, configure Rack Pagespeed in your config.ru Rackup file:

require 'rack/pagespeed'
require 'myapp'
use Rack::PageSpeed, :public => "/app/public/dir" do
  store :disk => Dir.tmpdir # require 'tmpdir'
  inline_javascript :max_size => 4000
  inline_css
  combine_javascripts
end
run Sinatra::Application

For those Rails, create a rack_pagespeed.rb initializer with:

require 'rack/pagespeed' # somewhere
class Application < Rails::Application
  config.middleware.use Rack::PageSpeed, :public => Rails.public_path do
    store :disk => Dir.tmpdir # require 'tmpdir'
    inline_javascript :max_size => 4000
    inline_css
    combine_javascripts
  end
  # ...

Filters

Out of the box, Rack Pagespeed supports filters to:

• Inline JavaScript under 2kb
• Inline CSS under 2kb
• Bundle JavaScript files
• Minify JavaScript files
• Bundle CSS files
• Inline images using data-uri

You can even roll your own filters.

Storage

Rack Pagespeed currently supports two storage options: disk and memcached. See the well designed docs for advanced options.

[Source on GitHub] [Web site]

We sit down with Scott Hanselman at Microsoft Build 2025 to discuss open sourcing all the things, cool stuff Windows can do, where we want (and don’t want) AI to fit into our lives, building arcade cabinets, and so much more.

Matched from the episode's transcript 👇

Drew Wilson is back! It’s been more than a decade since Adam and Drew have spoken and wow, Drew has been busy. He built Plasso and got acquired by GoDaddy. He built a bank called Letter which didn’t work out…and now he’s Head of Design at Clerk and back to chasing that next big thing.

Matched from the episode's transcript 👇

Daniel Kokotajlo and the AI Futures Project lays out a potential scenario of superhuman AI’s impact, Liam ERD generates beautiful, interactive ER diagrams from your database, Mozilla takes on Gmail with “Thundermail”, algernon explains why grepping remains terrible & Vitor M. de Sousa Pereira rans on the insanity of being a software engineer.

Matched from the episode's transcript 👇

Beyang Liu, the CTO & Co-founder of Sourcegraph is back on the pod. Adam and Beyang go deep on the idea of “industrializing software development” using AI agents, using AI in general, using code generation. So much is happening in and around AI and Sourcegraph continues to innovate again and again. From their editor assistant called Cody, to Code Search, to AI agents, to Batch Changes, they’re really helping software teams to industrialize the process, the inner and the outer loop, of being a software developer on high performance teams with large codebases.

Matched from the episode's transcript 👇

Antirez has returned to Redis! Yes, Salvatore Sanfilippo (aka Antirez), the creator of Redis has returned to Redis and he joined us to share the backstory on Redis, what’s going on with the tech and the company, the possible (likely) move back to open source via the AGPL license, the new possibilities of AI and vector embeddings in Redis, and some good ’ol LLM inference discussions.

Matched from the episode's transcript 👇

It’s Kaizen 18! Can you believe it? We discuss the recent Fly.io outage, some little features we’ve added since our last Kaizen, our new video-first production, and of course, catch up on all things Pipely! Oh, and Gerhard surprises us (once again). BAM!

Matched from the episode's transcript 👇

Jerod and Adam use Chris Kiehl’s post on development topics he’s changed his mind on (over the last 10 years) as a proxy for discussion on dev things they HAVE and HAVE NOT changed their minds on.

Matched from the episode's transcript 👇

Techno Tim joins Adam to catch up on the state of Homelab for 2025, the state of AI at home and on-prem (AI Homelab) and where that’s heading, building a creator PC, choosing the parts for your build, GPU availability, Windows being user hostile, and why Tim is happy to be using Windows, Mac AND Linux.

Matched from the episode's transcript 👇

Jerod & Adam discuss Nvidia’s recently announced personal AI supercomputer, Waymo’s latest infinite loop, what’s involved in getting a “modern” terminal setup, and whether or not AI has gone mainstream… warts & all!

Matched from the episode's transcript 👇