Aleksandr Hovhannisyan

I discovered this CSS oddity while trying to figure out why my plan to use (negative) margins to create a new "effective" content box wasn't working with percent units (but worked with other units). The best explanation seems to be in the middle of this article: https://www.aleksandrhovhannisyan.com/blog/css-aspect-ratio/#why-it-wo…

What about the font-size: = 62.5% trick? html { font-size: 62.5%; } https://www.aleksandrhovhannisyan.com/blog/62-5-percent-font-size-tric… Has it gone by the wayside? Is it no longer a best practice?

Instead of loading in the page, and then accessing that image, disable the loading entirely by using e.g. `data-src` instead of `src` in the HTML. You then fetch() the URL in that data attribute in your Javascript. Here's a straightforward tutorial covering that: https://trezy.com/blog/loading-images-with-web-workers [0] Note that this does mean the images will be delayed from loading, and will cause a layout shift when they're finally inserted. It's best to inline the image's height & width into the HTML if you know them in advance (or use `aspect-ratio`): https://www.aleksandrhovhannisyan.com/blog/setting-width-and-height-on… [0] Just as a note, the tutorial says "<img> tags actually block your application load," which is very wrong.

Follow this: https://cbea.ms/git-commit/ and this: https://www.aleksandrhovhannisyan.com/blog/atomic-git-commits/ That way your "large change" becomes a collection of small, easy to reason about and well explained changes.

> "So maybe 'rems for body text, px for headings' is the way to go." what's probably a little more useful is that headings scale up slower than body text, using different clamp() functions, e.g., https://www.aleksandrhovhannisyan.com/blog/fluid-type-scale-with-css-c…

This is from January, there's other articles around mentioning this trend Here's another angle: It's Killing Brands https://www.aleksandrhovhannisyan.com/blog/blue-people-illustrations/

> The browser might default to 16px font size, but users can pick something else. So if somebody had poor vision and increased their default font size; or if they had a small laptop screen and decreased their default font size, 1em * 62.5% != 10px, everything the designer set in ems was a different size than they intended, and a lot of their page layouts disintegrated into an unholy mess. Howdy, author of the article you're responding to (but not the person who originally discovered/pioneered this trick). This is not true, and my article explains why. The 62.5% trick is rarely used on its own, but people often cite it this way, leading to confusion. In practice, you set the root font size to 62.5% (of the user agent font size) and then also scale all body text back up to 1.6rem so it's not stuck at 10px. From here on out, all font sizes remain proportional no matter what, even if a user changes their preferred root font size in browser settings. Play around with the math if you doubt it (the article offers examples). > everything the designer set in ems was a different size than they intended That's working as intended—your design will scale up or down, according to the user's preferred font size. If you don't like this, your only option is to set font sizes in pixels, which [you shouldn't be doing anyway](https://www.aleksandrhovhannisyan.com/blog/use-rems-for-font-size/) (disclaimer: also written by me).

DuckDuckGo search results for "cli, extract frame 13s into video" (no quotes): • https://stackoverflow.com/questions/10957412/fastest-way-to-extract-fr… • https://superuser.com/questions/984850/linux-how-to-extract-frames-fro… • https://www.aleksandrhovhannisyan.com/notes/video-cli-cheat-sheet/ • https://www.baeldung.com/linux/ffmpeg-extract-video-frames • https://ottverse.com/extract-frames-using-ffmpeg-a-comprehensive-guide… Search engines have been able to translate "vague natural language queries" into search results for a decade, now. This pre-existing infrastructure accounts for the vast majority of ChatGPT's apparent ability to find answers.