Is there something like the opposite of this account, featuring games and devs that are explicitly *not* using AI?

First, looks cool! Nice job! Now, the constructive feedback
- Font inconsistency on the resume PDF
- The percentage meters, what do they mean? You know 95% of all Java knowledge? If you are using this mainly for professional development, I'd put your skills in a summary and defend with project cards

Basically, keep as much in the "light" dom as you can and avoid the shadow dom, but if you need some really specific "chrome" for your component, shadow dom it and expose it via parts and/or "custom properties" (aka --variables)

Using "chrome" in the design sense, not Google.

I mostly agree. Components should expose what is needed to do everything you need with it: no more, no less. In some cases, where a component is a wrapper with some functionality, shadow dom is probably overkill. But for others, with built-in "chrome", parts and variables do well. Slots can help too

> It works well for cerein use cases that not everyone has

Exactly! It doesn't need to be used all the time, but it does provide a functionality that doesn't exist elsewhere (specifically, making custom components that should be used and treated similarly to native elements) which is fairly rare

I think the reality here is that both situations kinda suck: using shadow dom makes it horrible to try and style custom component. Not using it breaks the encapsulation meaning your styles now target internal implementation details of the element.

Imo the right way is shadow dom with ::part styles.

Honestly. No one know shit about fuck

tem art always makes me happy :)

Bottom also is usually better on mobile because it's easier to reach actions or dismiss.

Horizontal flex-end, usually bottom, for desktop views. Once the toast takes up like 75% of the vw, it is nicer for it to grow to the full width of the page (usually a small tablet/large phone breakpoint)

Interesting! I didn't use toasts except for in more complex administrative UIs where I know pretty much every person who will be accessing it. But, considering the issues and the alternatives, I'll avoid them in the future! The banner/message for confirmations is a great idea. No temporal element!

Firefox's tooltips for validation errors kinda suck and sometimes aren't informative enough about the issue; I prefer the fields be highlighted with a clear error message presented below the field.