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.
Sounds nice. I've personally spoken on the phone with a police officer who told me he'd involve CPS if he saw my daughter walking (two blocks!) to school again.
This was my experience. There's this narrative that you move away from your parents and you have the freedom and independence they were previously denying you, and I'm sure that's very much the case for many people but it's not as though my parents were ever trying to keep me from going places and seeing people, the built environment where I grew up (suburb of Los Angeles) did that.
I'm strongly in favor of expanding the US social safety net, but I don't want to neglect other obvious factors here. Dutch children are able to walk or bike outside unsupervised. In the US they'd risk either being killed by a driver, or stopped by an overzealous neighbor or police officer. I think this kind of freedom of movement has a big effect on happiness, it certainly did for me.
ETA again: I glibly mentioned "being killed by a driver" but of course navigating the typical US built environment if you're under 16 or otherwise unable to drive is a miserable experience in a number of ways even if you survive it. Highways make pedestrian paths unnecessarily roundabout. Parking lots make everything further from everything else. Crossing major roads requires getting drivers to notice and stop for you (harder when you're short!), or waiting through interminable signal cycles, etc.
I would never recommend this methodology to a friend or a family member. Drivers are vindictive, violent people and the risk is too high to be worth it.
The author refers to no metrics at all other than their invented one (the hot water rectangle) and then makes no attempt to motivate it by connecting it with something someone living in the home might care about. Does a smaller hot water rectangle mean less energy consumed? Faster hot water at the tap? Hotter water at the tap in steady state? Would other interventions (insulation on the pipes, say) improve these metrics at lower cost? We don't know.
The article keeps saying that Apple has responded or that Apple has clarified and then linking other Wired articles. Is there an Apple press release somewhere? If so, I'd rather read that.
ETA: looks like they directly provide documents from Apple at the bottom of the article
Clojure's great for this too, I've never seen a Clojure programmer generating HTML with string templates and that's not because Clojure programmers are more disciplined, it's because Clojure's syntax is flexible/simple enough to make generating HTML in a structured way the natural solution.