TehPers

I'm not the one recommending it lol.

If I had to guess, it's to improve page performance by prerendering as much as possible, but I find it overkill and prefer to just prerender as much of the page as I can at build time and do CSR for the rest, though this doesn't work if you have dynamic routes or some kind of server-side logic (good for blogs and such though).

I think their point was that CSR-only sites would be unaffected, which should be true. Exploiting it on a static site, for example, couldn't be RCE because the untrusted code is only being executed on the client side (and therefore is not remote).

Now, most people use, or at least are recommended to use, SSR/RSC these days. Many frameworks make SSR enabled by default. But using raw React with no Next.js, react-router, etc. to create a client-side only site does likely protect you from this vulnerability.

I think it also doesn't help that only 4XX (client error) and 5XX (server error) are defined as error status codes, and 4XX errors don't even necessarily indicate that anything happened that shouldn't happen (need to reauth, need to wait a bit, post no longer exists, etc).

Trying to think of what 6XX would stand for, and we already have "Service Unavailable" and "Bad Gateway"/"Gateway Timeout", so I guess 6XX would be "incompetence errors". 600 is "Bad Implementation", 601 is "Service Hosted On Azure", 602 is "Inference Failure" (for AI stuff), and I guess 666 is "Cloudflare Outage".

It's a republic, not a democracy.

(Or whatever people say these days to justify how the legislative and electoral systems are complete trash)

No, and your hostility is out of place. Do you have something against GN?

There are induced comas, but they're terrible for you and only really used a last resort. Also, the quality of sleep is awful, from what I've heard.

This is the actual answer with respect to Cloudflare. Their config system was fucked in November. It's still fucked in December. React's massive CVE just forced them to use it again.

More generally, the issue is a matter of companies forcefully accelerating feature development at the cost of stability, likely due to AI. This is how the company I'm at is like anyway.

That's why your what wasn't working?

He also publishes written articles, but not for all videos, and not usually at the same time as the video.

Edit: also, there's more to the video than reading from a script. You'd know this if you, uh, watched the video.

The year before that wasn't without controversy as well. Not surprised to see NL on the list of countries noping out this year.

30 is assuming you write code for all 30 days. In practice, it's closer to 20, so 75 tests per day. It's doable on some days for sure (if we include parameterized tests), but I don't strictly write code everyday either.

Still, I agree with them that you generally want to write a lot of tests, but volume is less important than quality and thoroughness. The author using the volume alone as a meaningful metric is nonsense.

If it were a systemic issue and they had massive control over my life, I would wish them only the worst. Speaking from experience, of course.

After moving out, once they were out of my life for the most part, that dulled into indifference.