Elad Roz

In fact, after disabling prerendering, you can try to lift the "bot embargo" in CloudFlare and see what happens - as you probably in general do want your sites indexed.

I would recommend disabling Prerendering for your site (if it's on), because it's a static site. That would mean bots which don't run JS won't load it at all (while our built-in pre-renderer would attempt load all JS and run it, because its purpose is for client-side-rendered sites). >>

Hey!
I work at Netlify.
From a quick glance at mektuplar.org, it loads a pretty hefty search index file (about 7mb). If there's a lot of bot activity (we'll release tooling for that soon), this is a likely culprit. >>

How I'm coping with the situation in Israel:
building a Lego B-2 bomber as a weekend project based on a few pictures and available parts 🤷‍♂️

Getting the canopy right (yeah, I know there is no canopy in the real thing...) took about as much time as all the rest of the superstructure.

I haven't touched React in eight years and never will again, but if you use React and especially Next.js, this is a fantastic article.

Lots of alternatives available.

That's music to
@ryansolid.bsky.social's ears! ✌️

תמצא רק חתולים

We're also good friends with the Astro team, so I'd try to get to the bottom of it when I can :-)
Also noting to @mk.gg - the CPU usage for image optimization (without the adapter) is pretty intense on my local machine, perhaps there's a way to throttle that.

Great.
I also agree that if this was automatic, it would have been great, but there are pros/cons there. Some frameworks like Next.js don't *yet* have a clear adapter interface, so we detect it automatically. Having to configure things gives you much more explicit control but is more manual.

Perhaps there were some later commits that you did there?

I've deployed a fork of the current code, and everything works very quickly (it uses the Image CDN automatically, so no time is spent in the build on optimizing images at all).
(Locally if I run a usual build, I do see it takes 2.5 minutes to optimize on an Mac M2 Pro).

I'm curious how many and how big are the images in question... is the repo public?

@astrojs/netlify Learn how to use the @astrojs/netlify SSR adapter to deploy your Astro project.

Hey, if you're using the Netlify adapter (docs.astro.build/en/guides/in...), image optimization should by default be on-the-fly rather than at build time.
(I'm from Netlify)

לחיזבאללה היה one job אבל אני רואה שהבניין הזה עדיין עומד...

אין שום בעיה בכלל.

זה הכל מקנאה, אנחנו אנשים קטנים

נקודה מעניינת אחרת בקטע היא הטענה שהמאבק בשינוי האקלים נהיה פוליטי ומפלג באשמת הסמול - ולא בגלל שיש לא מעט גורמים שיש להם אינטרס כלכלי מאוד ברור להכחיש את הבעיה, וידעו להפוך את זה לפוליטי...
מוגש בחסות "בגללכם חזרתי לתמוך בביבי"

Oh it's meant to be fed to a multi-modal LLM, of course

יותר כמו 2006 🙂

זה סוג של progress bar כזה עד שהחג מגיע

ב-React Compiler זה לא היה קורה

הכרמל?

I meant Backend for Frontend 🤷
Anyway, that part now involves routing, SSR/ISR, server actions, built on image optimization, and more niche stuff like OG image generation. That's a lot of concerns.
Tying that to a specific client side framework is perhaps the issue, which Astro tries to solve for.

Depends on what you you need that backend to do, no?
The backend part of the framework is typically a BFF (Backend for Framework). Anything that has considerable domain logic would be its own service.

הייתי הראשון לזהות כשכבר ב-2006 בנות הסתירו לי את הבמה ב-rock am ring.
The struggle is real!

Merge it already blyat

@philippeserhal.com oh lookie here!

That is not even boomer. It's like ancient greeks level boomer