You cannot build a CSAM generator, period. CSAM means Child Sexual Abuse Material -- material created through the sexual abuse of children. If it came out of a generator, it is not, by definition, Child Sexual Abuse Material.
This is an easy fix. Ditch the HOV element and make the lane toll-only. Tolls already encourage carpooling -- more people in the car means less toll per occupant.
> given the incredible preservation that Dolphin provides for their original versions.
Does cemu not provide comparable preservation for the HD versions? I played through both WW:HD and TP:HD on my Steam Deck using cemu and found it a great experience.
Trump will certainly consider this provocation, so perhaps the news here is that Amazon considered this worth it, even given the inevitable retaliation.
The strike emphasizes the importance of automation. We should be prioritizing the investments that will allow us to fire as many of them as possible as soon as possible.
I'm a little confused about when I'd use this, if I'm quickly iterating on code as I develop it, probably I also want to know whether it type checks, right?
The article makes it sound like the system was using eval (probably on a per-request basis, not just on start-up), and also like ceasing to use eval was pretty trivial once they realized eval was the problem. I'd be curious why they were using eval and what they were able to do instead.
Submission title mentions NDA but the article also mentions a non disparagement agreement. "You can't give away our trade secrets" is one thing but it sounds like they're being told they can't say anything critical of the company at all.
Coming at this from a naive outsider perspective, the central problem described in the post (commits to PostgreSQL frequently have serious defects which must be addressed in follow-up commits) seems like one that would ideally be addressed with automated testing and CI tooling. What kind of testing does the Postgres project have? Are there tests which must pass before a commit can be integrated in the main branch? Are there tests that are only run nightly? Is most core functionality covered by quick-running unit tests, or are there significant pieces which can only be tested by hours-long integration tests? How expensive is it, in machine-hours, to run the full test suite, and how often is this done? What kinds of requirements are in place for including new tests with new code?
I actually prefer to add a passing test asserting the bug exists in one commit, then fix the bug and reverse the sense of the test in a second commit. The second commit is now more or less self documenting -- this case used to produce this buggy behavior but now produces correct behavior -- and the fact that the test originally passed provides proof that the test is capable of detecting a regression.