Raymond is a developer evangelist for Adobe. He focuses on APIs, AI, the web platform, and enterprise cat demos.
A week or so ago, I was doing some tests on Google Colab and noticed something interesting. The notebook I was using was one that took one to two minutes to process. Before I'd start the process, the favicon looked like so:
Last week I had the pleasure of presenting at the Mid-Michigan ColdFusion Users Group on the topic of Intl, the web platforms internationalization spec. I gave this presentation again this week at connect.tech as well. I greatly enjoyed working on this deck as I've been using Intl for a while, but had not had the opportunity to look into every nook and cranny.
Yesterday, I gave my presentation on Intl, the browser's built-in support for internationalization. I've been using this for a while now, but while researching the spec for my presentation, I ran into multiple cool aspects of it I wasn't aware of. One feature I thought was particularly interesting was the Segementer object. MDN's description is nice and succinct:
Please take what follows with a Titanic-sized grain of salt and do your best not to do what I did, but despite that, I thought this little hack was interesting and I figured I'd share it anyway. I typically use Reveal.js for my presentations, especially when talking about the web platform, as it makes it easy to do slides and demos, all in my browser.
The last seven days have been... difficult. I don't think I need to go into why (even for my non-American readers), but I am doing my best, as are a lot of people, to take things day by day. Honestly, as a white hetero man, I'm not so much worried for myself, but I'm deeply concerned about my family and friends who are LGBTQ+ and other minorities. I don't talk a lot about my children here as I want to ensure their privacy is maintained, but seven of my kids are adopted and Asian and my usual worry for them has risen quite a bit.
A few days ago, I blogged about using Chrome's built-in generative AI features (which are still super duper too early to even consider for production) to add on-device translation capabilities to a web app. It got me thinking, what if we could do translation automatically via a web component? If for some reason it failed, that would be fine as the original text would still be there, but in cases where it could work, it would be automatic. Here's what I built.
og:description and og:image were using name instead of property. This seemed to work ok in most situations, but wasn't proper. So, I've updated the code here, and the GitHub repo for the workflow, to use that. Thanks to @toothless-666 for helping me debug and @benmillett for pointing out various things as well. You can see the full discussion in the comments below.Want more posts? You can peruse a complete list of my content, or pop over to my search page to find what you're looking for.