“Thank you very much for sharing your insights. Over the past year and a half, I’ve been diligently coding and creating my own components from scratch. This methodical approach has helped me gain a solid understanding of the underlying principles. Now, I feel confident discussing the topics you’ve covered, and it’s incredibly satisfying. The instructional video you provided played a crucial role in advancing my expertise. I’m truly grateful for this valuable learning resource, and I’m excited to explore more complex subjects. Once again, thank you for helping me progress on my learning journey.” 😊

Beef with hamburger is a bar

What? How can u fit more then 1 (even that) text link in a mobile nav app bar when logo is mostly taking 50% of space? Unless u put it under the app bar , but that's designer choice.

IDK what's wrong with me, but I prefer to watch my podcasts. IDK how long y'all've been doing this, but I like it.

Fantastic! Loving all the new stuff! Excited for the Firefox platform

Hah, I work with Opera people now and I've heard that story as well!

This was great I really enjoyed how Andrew broke things down. Im like 8 or 9 months in my Rust journey and it really is a great language. The learning curve is honestly not that bad if you already have a language and some programming exp under your belt. Totally worth taking the time to learn for anyone considering it.

ADHD is real. Scott can't stand still for a ms. Great episode though 👍

This guy hasn’t worked with many is or cultures.

Man you’ve really messed me up. I have my entire family’s life in Bitwarden. And unrelated I was searching for a way to manage env variables when I used another mac temporarily and didn’t find anything simple and consumer rather than enterprise. And now he casually mentions something I spent a whole day trying to find in vain and now I have to deliberate switching to 1pass

I appreciate the take here to try an establish a definition for what constitutes a 'design system'. I think I would interpret it even more generically: A design system is in essence a governance mechanism which describes how some scope of products are communicated to its audience. Design systems are documented to provide the guidance. Many find this most convenient to document within Figma, given how valuable it can be to express that guidance through visualizations. Figma/Sketch/XD and similar apps typically build out features to help design teams keep a consistent reference of these concepts that can be instantiated to make a design team's workflow more flexible and resilient to change. Similarly, a component library is just a tool to help templatize the expression of that system in a manner where that communication medium is in some digitally interactive format (web/native apps). Ultimately, the implementation of the system is a challenge that a team or organization will have to figure out how to best maintain and scale.

It's жщ

You’ve convinced me to use the env cli today. I’ve meant to mess with it for like a year at this point and today I have a need lol

ok

Making the text smaller would be horrible for accessibility. So while you hate it, I’m actually thankful that people “are lazy” and don’t do that.

No matter what everyone said … the correct pronunciation is ZSH

this is a great video.

I built a tailwind theming package that creates a custom tailwind plugin. You pass any css color, including hex, and converts it to oklch so you can use alpha values with tailwind. It’s great because with the Tailwind Intellisense extension, you get autocomplete for your custom colors. Also provides helpers for shadcn theming. Currently working on a new one specifically for theming shadcn.

Why not zoom out then? That's what I do in such situations and the problem goes away

Thank you so much for the great content. I am actually following along, as a non-programmer. I am setting all this up on my spare laptop, and my isp requires me to user certain ports, which means that I can't use the standard ports for HTTP and https. This means it's not as easy to get the auto https unfortunately. But looks like it's still possible

Wat een verrassing, nooit gedacht dat jij Nederlands bent 😮 (What a nice surprise, never thought you were Dutch.)

Zush 4L

you commenting about the magic link annoyance triggered me. I tried to login to Slack. Slack sent a magic link to my gmail. For my gmail to login I had to go to another tablet device + open the youtube app + have gmail pop open the security check there I go find tablet I barely use. I fail login to the tablet a few too many times due to fat fingering. It's a google tablet so google sent me a text to my phone verify. Text comes, I type code. Go into tablet. Open youtube on the tablet to get gmail verification magic popup and accept I am indeed me, go back to computer and get into Gmail. Get magic link. Get into Slack. FORGET WHAT THE HECK I AM DOING BECAUSE THAT DID NOT FEEL LIKE MAGIC IT FELT LIKE PAIN.

Mobile users are the majority at 60%. Mobile first is more relevant than ever. A UI made for desktop is unlikely to work on mobile, but a mobile UI, while not optimal, will probably make for a usable website on desktop.

I think web component based core ui components (toasts, switches, etc) feels like the way to go. Really looking forward to web awesome.

Worse are the ones that only serve burgers - at all widths. 🚫🍔

Laziness, but also if you get a set design to adhere to, and then told a specific number of items that have to display horizontally in a desktop menu... Then you kind of don't have a choice. But it's also a UX thing. I shudder to think of some of those huge megamenus overflowing a small viewport width. Building for the in-between sizes is a real challenge. I like some of the patterns like an overflow menu, but it's hard to make something usable AND aesthetically pleasing. Would like to see a follow up of some good examples/patterns

Wes dishes 🥩 on those 🍔 menus!! 🫳🏻

I feel attacked

Guys how do i implement email functionality with Coolify?

Scott & Wes Thanks so much guys... God bless 🙏🏽

As a blind software engineer who uses a screen reader (and a backer of the accessibility-focused Web Awesome Kickstarter!), I want to emphasize the importance of accessible components. Popular options often fall short, forcing me to build custom carousels, datepickers, and navs. Would love to hear your thoughts on this and how we can make components more inclusive for everyone.

Loved this episode. I'm building my personal starter project with my preferred stack right now and this felt super relevant. This is the second episode that you've put out that I've thought "Wow, I was just thinking about that". The last one was the React Native episode. Good stuff!

'patch-package' is a lifesaver to have bug fixes before they're released

I write all of these things myself every time but it's growing old. I've started a Storybook project for myself to catalog the things I've designed and developed that are "different" enough from each other that I can borrow from.

I think there was a point missed on the email link sign-in stuff. The thing that frustrates me about that and also email validation or reset password links is that the links always open a new browser window/tab. Now you have 2 (or more) tabs open to the same website which is unnecessary and possibly could be confusing if you don't remember which tab you were on.

Wanted to echo Scott's suggestion. I started building out my own common component library for personal projects and it's been great for improving my ability to make extensible and composable interfaces, and really thoroughly consider theming and responsive design upfront in my projects. Btw, my new fave feature of the show is those joke intro cards for Scott and Wes. Whoever is writing those is cracking me up!

Excellent episode (as usual). I love the camera angles; it really makes it feel like I’m just peeking into your conversation. Also, +1 on that Coolify episode. Got me! Look ma, I’m self-hosting now!

Ok

Really enjoyed the process, thank you! I rented a VPS just for fun and i don't regret.

I'm a Z-S-H guy myself. Good to know we won 🤣

What provider are you using for your VPS? I've always been overwhelmed trying to choose

Zeeshan

Speed, simplicity, size - don't forget that a 5 also looks like an S for more synergy

would be good if you showed some code snippets, sometimes the concepts flow over the heads if we don't see them applied in a use case.

have done someting like that last week to have a progress bar. To resume you juste need to pass a function in your promise that will be called during the stream(progress)

Great insights! like how this shows information about potential real problems we can face while doing web/native apps.

Sounds like a good use of observables, like when you subscribe to RxJS observables you can pass both a handler for each message and a handler for when the observable closes/completes

Hah, I've been using p-queue today after Wes mentioned it in a previous episode, wonderful lil' nugget by Sindre Sorhus.

Oh, snap! promise resolved, but my callback crashed... turns out to be a Syntax error 😂