j@ubourg

I write JavaScript server-side & client-side @twicpics. Used to be a @jquery core member and to talk about it at conferences.

[j@ubourg @jaubourg]

Hey @AnthropicAI, chat bots are nice but I've been asking for support for 5 days for something that requires a human with absolutely zero reaction on your end.

[j@ubourg @jaubourg]

jQuery is 20 today! Will meet the old gang this weekend at Dallas. Just can't wait!

[jquery @jquery]

On January 14, 2006, 20 years ago today, @jeresig introduced a new JavaScript library that came to be known as jQuery.

[TwicPics by Frontify @TwicPics]

Announcing TwicPics Flutter Widgets! 📱

A widget library that brings the power of TwicPics to your favorite app builder. Use TwicPics Flutter Widget to get images best practices out of the box.

👉 https://t.co/puIPoXB63X

@FlutterDev #components

[j@ubourg @jaubourg]

@HowDevelop @StriftCodes @nuxt_js @meilisearch @storybookjs @vercel @TwicPics Always nice to see @TwicPics put to such good use. Congrats @StriftCodes and @meilisearch, this IS snappy!

[TwicPics by Frontify @TwicPics]

🟣 How to automate responsive image resizing with @nextjs and TwicPics?

Learn how to leverage the layout-driven pattern to control the size of your images or videos using TwicPics Components.

👉 https://t.co/3naMOVLgVW

[TwicPics by Frontify @TwicPics]

🚀 In our latest guide, we’re leveraging @reactjs's easy integration with @astrodotbuild to set up and use TwicPics Components.

👉 https://t.co/gRrdyYFhfX

[TwicPics by Frontify @TwicPics]

TwicPics won the first place in the User Experience category at the NRFrench Party organized by @businessfrance ⭐

#ecommerce #retail @NRFBigShow

[Julie Le Bolzer @JulieLeBolzer]

Dans @LesEchos, rencontre avec @SpiessHenri, le directeur général de @TwicPics, actuellement à New York pour le #NRF2023. Diplômé de l'@EPITA, cet amateur de #Kitesurf est passé par Apple, @CiscoFrance, @NTTSecurity_FR, @zscalerFR ou encore @CyberArk. https://t.co/T5sc9DoAsi

[j@ubourg @jaubourg]

@apyth @TwicPics 🎅 =)

[TwicPics by Frontify @TwicPics]

💡 #reactnative tip

Using <FlatList> and <TwicImg> you can lazy load pixel-perfect responsive variants of your images.

[TwicPics by Frontify @TwicPics]

oopsie

[TwicPics by Frontify @TwicPics]

@reactnative Psst — We have since released v0.13.1 which is compatible with the last @nuxt_js 3 release 🎉

Changelog here: https://t.co/AcJWf6iyFh

[TwicPics by Frontify @TwicPics]

Read our guide to build a @reactnative app with:

• @commercetools for products
• @contentful for blog posts
• @TwicPics for a unified image optimization API

https://t.co/MU78RuwiG0

[j@ubourg @jaubourg]

@TimVereecke @nhoizey @HenriHelvetica @jonsneyers @TwicPics @ldevernay @HTTPArchive @paulcalvano Seems like there won't be a choice if JPEG XL is not supported by the biggest browser on the market. CPU usage is part of the equation, we were eagerly waiting for JPEG XL support for the image fidelity and bandwidth gain too. Having a better technology muzzled is disheartening.

[j@ubourg @jaubourg]

@SimplyGreenIT @jonsneyers @ldevernay @HenriHelvetica @TwicPics @HTTPArchive True, but sometimes they are aligned. For instance when delivering a version of the image adapted to its actual view size on the page.

[j@ubourg @jaubourg]

@jonsneyers @SimplyGreenIT @ldevernay @HenriHelvetica @TwicPics @HTTPArchive @jonsneyers is right. It all depends on the ratio image produced / image consumed. On sites heavily relying on user content (social networks, marketplaces, etc), few images will be viewed a lot while most will be processed once and displayed a very limited amount of time.

[j@ubourg @jaubourg]

@ldevernay @HenriHelvetica @jonsneyers @TwicPics @HTTPArchive I'll see what I can have our data guy extract something from our stress tests. Sadly, they obviously contain confidential information in their current state. Happy to discuss this once I clear this up internally ;)

[j@ubourg @jaubourg]

@HenriHelvetica @jonsneyers @TwicPics @ldevernay @HTTPArchive @paulcalvano You're right. Though Google's silence on the issue is really worrying.

[j@ubourg @jaubourg]

@ldevernay @HenriHelvetica @jonsneyers @TwicPics @HTTPArchive Sadly, we don't see much research done in that department. The only data we have is the CPU effort when encoding and the compression ratio. Our internal tests suggest supporting AVIF rather than WebP requires at minimum a doubling of the infrastructure and that's conservative.

[j@ubourg @jaubourg]

@HenriHelvetica @jonsneyers @TwicPics @ldevernay @HTTPArchive @paulcalvano Except, in this instance, Chrome removing JPEG XL clearly means they intend to push AVIF even more. To continue on your analogy, the factory stopped producing hybrids and will force consumers to use sport cars. And JPEG XL produces smaller files to boot.