awinograd

> https://x.com/AJArabic/status/1727029106288808273

My understanding of this is that the IDF knows that israel built an underground basement level for hospital operations, not the connected tunnel system.

They did claim it was a headquarters. I agree their CGI infographic was over the top and not representative of what was actually there. I dont think we can expect that a hamas brigade HQ looks like a state of the art command facility like you'd expect from a well established military. It's impossible to know exactly what the tunnels were used for in terms of planning / coordination but you previously said there was zero hamas presence at the hospital and I dont think that's a realistic take.

> https://x.com/celinekasem/status/1734856596679778558

It looks like the photo on the left is the IDF detaining military aged men for processing in the current conflict and the right is the british army detaining german prisoners in WWII.

https://www.alamy.com/the-british-army-in-north-west-europe-...

That's at least what the source above says. I have no idea how accurate it is to be honest, but I dont think i'm following your/the original tweeter's argument on this one. If the intent was to say the picture on the right was germans rounding up jews to put them in concentration camps, I dont think that's an apt comparison as the detainees in gaza aren't about to be executed. I think I read about ~60% of the last batch (the one where the photos went viral) were released after determining who was a civilian and not.

> They have killed more than 20,000 and 11000+ children in three months. This is the largest civilian life loss in this decade, there is nothing even close to this, Ukraine is not close in TWO YEARS.

I agree the civilian death toll is high. I also am not saying the IDF's war plan is 100% in lock step with what I would have chosen but I'm also not in their shoes.

I do think it's worth trying to compare/contrast the two situtations a little more granularly though.

1. Here are stats by month that show much higher civilian casualties in the first months of the war. https://www.statista.com/statistics/1318455/ukraine-war-casu... 2. The ukrainian army isn't dressed in civilian clothing making it impossible to distinguish their casualties from civilian casualties. Best estimates I've seen is ~1/4 of the deaths reported in gaza are combatants. Still that leaves a large number of civilians, not arguing that. 3. The ukrainian army doesn't operate out of hospitals, schools, or in tunnels under the civilian population. Based on our previous back and forth, I dont think we'll fully agree on this point, but I think it's relevant here.

> they said "we are fighting human animals", this was never directed at Hamas

The huffpost article you cite says the comment was made in reference to hamas.

As I said above, I dont think my response would have been identical to what we're seeing from the IDF. I would have pushed to limit civilian deaths more (not sure exactly how) but I would still want to respond forcefully to hamas. You can't move the civilian population out of gaza b/c that's forced displacement. You can't move them fully out of the way in gaza because it's a relatively small piece of land. You can try to move the population to "safe zones" near UN buildings and then hamas fires rockets from 100m away.

https://www.nytimes.com/2023/12/08/world/middleeast/here-is-...

I'm curious what your general course of action/goals would have been in response to Oct 7. What options do you have when a hostile force _intentionally_ targets ~1k civilians and additionally brings back 150+ civilians as hostages (my counts roughly excluding soldiers they killed/captured).

Hamas bringing hostages on Oct 7th to Al Shifa: https://www.nbcnews.com/news/world/israel-video-hamas-hostag...

There is clearly a Hamas presence at the hospital based on the video. Additionally, there are tunnel shafts in the complex that lead to dozens of meters of tunnels with wiring/electricity connected to the hospital. Granted, the electricity comment is impossible to verify, but the tunnel system is clearly there. I don't have any guesses of who besides hamas would have built/used a tunnel like that.

Person with an RPG next to steps of Al Quds hospital: https://www.cnn.com/videos/world/2023/11/13/hospital-gaza-al...

Hard to tell if this person is affiliated with Hamas or some other group, but it's clearly a combatant at the hospital.

RE the school: It's kind of difficult to tell what has happened. Clearly the school was the site of fighting, but I don't see any evidence in that video showing point blank executions of anybody let alone civilians or infants as was described.

We shouldn't take any statements from either side of the conflict at face value, but it's not realistic to deny any evidence that arises just because of who produced it. Here's what I think is a pretty reasonable take on that[1].

Here is CNN reporting on a video that shows a guy with an RPG walking around the hospital[2].

FWIW, I agree that the IDF soldiers in the linked tweet should be punished for destroying civilian property/aid without any military purpose. It's good to criticize anybody when they do something wrong, regardless of which side of the conflict you lean towards.

[1] https://youtu.be/4qL6oM12CU8?t=417 [2] https://www.cnn.com/videos/world/2023/11/13/hospital-gaza-al...

The parent comment is discussing a different hospital, Al-Ahli on Oct 17th, vs Al-Shifa on Nov 10th which is the article you're linking to from NYT.

Civilians being injured in a hospital is clearly a tragedy. That's why hospitals normally have protected status during a war and targeting them would be a war crime. However, hospitals (and other protected sites like schools) lose their protected status when they're used for military purposes[1]. That doesn't make the situation less tragic for the civilians. But there's a difference between striking a random hospital because you want to kill civilians and killing civilians while striking hostile forces in the same vicinity that may be actively shooting at you.

[1] https://www.icrc.org/en/document/protection-hospitals-during...

Outweighed substantially is doing a lot of handwaving. Turns out that difference matters[1] when it comes to injury.

Maybe an analogous question would be: would you rather be stepped on by a horse or an elephant? Both substantially outweigh you but I bet you'll pick the horse.

[1] https://www.nber.org/digest/nov11/vehicle-weight-and-automot....

Oui Health | Typescript, React Native, Frontend or Backend | Remote | Senior Engineer | Full-Time

Oui's goal is to help those at risk of suicide. We build digital interventions rooted in real clinical data and in collaboration with leading experts in suicide therapies. We're already working with some of the US's largest health plans / providers (e.g. CVS, Aetna, and others)[1].

We primarily work with Typescript & React Native and are looking for talented developers across the stack to:

* Work on an important problem, help improve people's lives

* Have large impact & ownership on the direction of the tech

If any of the above interested you, contact leng<at>ouitherapeutics.com to learn more about the role and mention you came from HN!

https://cvshealth.com/news-and-insights/articles/aetna-and-o...

Oui Health | Typescript, React Native, Frontend or Backend | Remote | Senior Engineer | Full-Time

Oui's goal is to help those at risk of suicide. We build digital interventions rooted in real clinical data and in collaboration with leading experts in suicide therapies. We're already working with some of the US's largest health plans / providers (e.g. CVS, Aetna, and others)[1].

We primarily work with Typescript & React Native and are looking for talented developers across the stack to:

* Work on an important problem, help improve people's lives

* Have large impact & ownership on the direction of the tech

If any of the above interested you, contact leng<at>ouitherapeutics.com to learn more about the role and mention you came from HN!

https://cvshealth.com/news-and-insights/articles/aetna-and-o...

> We recognize that our tech writing staff drive a great deal of value to MDN users, as do partner contributions to the content. So we are working on a plan to keep the content up to date. We are continuing our planned platform improvements, including a GitHub-based submission system for contributors.

Looks like they won't write new content themselves, but will have a system for keeping content up to date

This is most likely due to their acquisition of AppSheet which will likely become the "replacement"

https://blog.appsheet.com/appsheet-acquired-by-google-cloud

Thanks! I've been working on this for about ~6 months now and it's been exciting to see how I can enable non-developers to make some apps!

Would be cool to see "no-code" as one of the flavors here. I'm betting on it being possible to empower non-engineers to make apps in a startup I'm working on AppsCanvas (https://appscanvas.com) which is a platform for building out apps with integrated an API / backend. Basically a whole app building & deployment system wrapped up for non-technical people.

I've been putting a lot of thought into low-code, and what the right escape hatches are to allow developers to use a tool like mine without feeling constrained. That's proving to be tough to balance though!

This project is using React Native which is slightly different from ReactDOM (commonly referred to as just React/ReactJS).

In the past, ReactJS and ReactDOM were completely interchangeable. However, some time ago now React split the DOM specific parts of the library into ReactDOM which allowed the non-DOM specific parts of the library to be shared more easily across different rendering targets. Some examples:

  * android (via react-native)
  * ios (via react-native)
  * canvas https://github.com/Flipboard/react-canvas

Since the release of React Native there have been a couple of interesting projects that allow developers to use the same APIs as React Native, but rendering to the DOM instead of android/ios native views.

https://github.com/necolas/react-native-web is a great production ready lib but requires a bit of setup to get it working with a react-native project.

https://github.com/vincentriemer/react-native-dom is an extremely cool experimental idea to bring react native projects more seamlessly onto the web. It's still in early stages and has some significant tradeoffs compared to react-native-web. For one, it includes a webassembly implementation of Yoga (https://yogalayout.com/) which makes layout much more consistent among ios/android/web but at the cost of delivering more JS upfront to the browser.

The async rendering rendering stuff Dan is showing in his talk (https://www.youtube.com/watch?v=_c7ajDXb4qw) looks great, but I disagree that this is a redux killer.

redux is useful for a lot more than just async fetching & loading. I think these new features will just reduce the scope of what redux is used heavily for.

Probably some sort of live reload functionality for development

Not limited at all! You can install react@next from npm and use fiber today. It's just not released as a production ready version.

> To understand how, read this post by the author of the CAP Theorem and Google Vice President of Infrastructure, Eric Brewer.

Seems like they might know a lot :)

Thanks zalmoxis for a great extension!

Just switched our devtooling over to it (from shipping devtools in our bundles) and it's both easier to setup (no need to worry about shipping extra code in prod) and handle multiple stores.

Really excited for persisting state in the extension and Immutable import/export!

Possible applications that come to mind are image recognition, note classification (e.g. recipe, web tutorial, news), text search, and text recognition in things like PDFs

I think it has to do with distance electricity has to travel. If a chip is physically bigger, it takes longer to move bits inside of it. Sort of similar to why you can't have an L1 cache the same size as main memory.

Just my best guess from a single processor architecture class so definitely not positive that's the answer.

I definitely agree with the premise that cookies are inherently insecure. With sessionStorage it's unclear to me if there's a clean way to send the secret with every http request. Does that mean binding to every link / button click event?

Also you mentioned this, but disappearing on tab-close makes it less of a drop-in replacement for cookies since that breaks existing behavior.

Interesting idea though! Enjoyed the read.

This is a ridiculous claim. The government doesn't have the resources to monitor the entirety of the Internet.

Yep--according to their TOS credits expire after one year unless stated otherwise.

From https://www.digitalocean.com/legal/terms/

5.8 As of March 6, 2015, redemption of promotional credit is limited to 12 months from the date of issue (unless otherwise stated), at which time the credit will expire. Upon redemption, promotional credit expires after 12 months unless otherwise defined in the terms of the promotion. For instances where promotional credit was issued or redeemed prior to March 6, 2015, that credit will expire on March 6, 2016.

My understanding of the docs is you cannot do that level of fine grained access control for a given gce instance. You can only give it a gcs scope of read, write, or both

This definitely seems like an improvement over the existing permissions system, but still seems to lack the granularity in resources to do things like per-bucket permissions in GCS.

It's a little silly to have to give a machine full read access to GCS if it just needs to download some packages/binaries but doesn't need access to things like database backups.

Thanks for glide! We're using it at Quizlet for our go builds and are fans. In conjunction with vendoring, makes it easy to have reproducible builds over time.

Also, there's some good discussion of other approaches to dependency management on the go forum: https://forum.golangbridge.org/t/the-best-dependency-manager...

This a pretty worthless blog post without any sort of analytics/measurements except for the author claiming the site needed 40 servers for Rails and 2 for Go.