Sorry, I just discovered it as well. But it stands to reason that you put the CDN between your clients and imgproxy to benefit from the caching of the resized images.

Happy New Year to you too, Eleftheria Batsou . What shall I wish you?

Thanks my friend! 🤗

You're right... in theory. And then, as I mentioned, sometimes, you don't want to spend time and money implementing the perfect solution: you just want to see if there's traction and interested.

Mani Gopal Your argument about the number of programming language is irrelevant. I guess you're not using Malboge or Brainfuck, are you? Because Carbon is labeled Google, you became interested. Fine. But on the opposite side, because I understand that It's all about context, I'm not. Carbon has its use-case, inside of Google. Outside, it doesn't mean squat. Engineering is the art of choosing the right tool in one's toolbox according to the context. Choosing the most popular tool, or the one that somebody else uses just because of that, is not engineering: it's CV-driven programming (the post dates back to 2009). Nothing new under the sun, but still disappointing to see the sad state of our industry.

Google designed Carbon to handle its own issues: be able to better manage its gazillions of lines of C code. But because it's Google, everybody and their neighbors think it's the next best thing since sliced bread... I mean until the next craze. Engineering doesn't deserve its name. It's all about shiny experimental things and not about reliable but boring ones.

Thanks a lot for your kind words!

Thanks a lot!

Thanks for your kind words!

How does GraalVM impact the build time? Is it noticeable? GraalVM proper is just a JDK. But the native-image part impacts it a lot : you need to wait for minutes and it consumes a lot of RAM (a couple of Gb)