In Django, how do you create components well and handle user interactions?

It's been a long time (we've gone all React), but I remember doing reusable components with templatetags.

I think that's where htmx comes in

I use django-components.

re:componenets Just use jinja templates.

Yes, it looks like it did add a kasrah to the word ظهري

Yep, and فمِنا too, this is not just OCR, it made some post-processing corrections or "enhancements". That could be good, but it could also be trouble the 1% chance it makes a mistake in critical documents.

He means the space between the wāw (و) and the word

I added a pic to the original comment, sorry for not being clear!

Thats erroring 429 too many requests

You would use anything that passes through Israel's blockade

I don't know about power and food since I have friends in the North who still don't have access.

How far is Israel expected to deliver the food? Right to everyone's door?

A seige means the borders are closed. The current situation, for at least 6 months now is that Israel is letting food trucks through the border, more and more every day.

A problem exists for that last mile inside Gaza where no one wants to distribute it because militants will straight up beat truck drivers with sticks to steal the trucks and the food.

You'd think the UN would step in and do something but so far they mostly just sit on their hands bleating.

So to summarize: there are huge piles of food just inside the Gaza border that are not being distributed efficiently/at all.

I also want to point out that it's not in Israel's best interest for there to be food shortages inside Gaza. The first people who will be starved are the hostages, so Israel wants to flood the strip with so much food that some trickles down to her citizens held there against their will.

>Right to everyone's door?

There are not much of them doors left anyway.

>A seige means the borders are closed.

Yes, practically for close to two decades now. Sea, Air and Land.

Drone and bomb attacks are delivered to doors without a problem, so... Yes.

I don't think Israel cares that much about the hostages (the constant indiscriminate bombing might give a hint). But if that's true and the hostages are in the hands of Hamas, then Israel would provide food and supplies to Hamas, right?

Where are your sources about "huge piles of food just inside the Gaza border?"

Anyway, there are a lot of reasons, one is this :

> Aid groups say coordinating their movements with the Israeli military inside Gaza remains a complicated and time-consuming process, sometimes requiring hours to coordinate safe access to the Gaza side of the Kerem Shalom border. And despite these efforts, Israeli airstrikes have hit aid workers on multiple occasions.

I haven't found anything on the investigation that is supposedly investigating the WCK workers murder. Unless the people who did that receives exemplary punishment, what sort of NGOs could distribute that aid? And ITF forces are still on the ground, and air.

Let's say a medium Nextjs v10 side project. The goal is to update it as quickly as possible. It's just me.

What is it for? Why do you want to upgrade? What are the constraints? Do you need to maintain 100% feafure parity?

10 to modern Next is a pretty big leap, especially if you're also going to move to the app router. The code mods might help a bit but not completely. Do you have older React code (class components etc.) or libs (old redux) and huge state trees?

If so it might be easier to rewrite the whole thing.

I've had to do a few rewrites like that and would typically do an exploratory investigation of each approach for a day or two, trying to better estimate the difficulty of each by partially starting a migration and partially starting a rewrite. Along the way I'd come up with a list of must haves vs nice to haves vs nice to get rid of, and use that to make a final decision.

But realistically, IMO a rewrite is inevitably cleaner (maybe with some functions manually ported over) and more maintainable over the long term.

Partial migrations for something like this means a lot of technical debt in the future. Next and React move too fast to keep up with piecemeal migrations like this cleanly. It's a very unstable ecosystem.

I'd probably end up extracting out the parts into modular components wherever possible, separating the business logic from the Next stuff (routing and caching and building) and the state stuff (meaning keeping components as pure as possible so state can be easily provided via whatever framework is popular that year)

OC replaced the real domain with example.com. Could have used int.google.com.