AndrewGaspar

Granting that I think X should have stronger content policies and technological interventions to bad behavior as a matter of business, I do think that the X Safety's team position[0] is the only workable legal standard here. Any sufficiently useful AI product will _inevitably_ be usable, at minimum via subversion of their safety controls, to violate current (or future!) laws, and so I don't see how it's viable to prosecute legal violations at the level of the AI model or tool developers, especially if the platform is itself still moderating the actually illegal content. Obviously X is playing much looser with their safety controls than their competitors, but we're just debating over degrees rather than principles at that point.

[0] > Anyone using or prompting Grok to make illegal content will suffer the same consequences as if they upload illegal content.

What you want isn't really "output C++ code that is pedantically equivalent to this Fortran code but with the array indexing fixed up", it's usually more like "translate this Fortran module into something that I can offload to a GPU using CUDA/ROCm/etc. with the same high level semantics, but GPU-friendly low level optimizations", and the exact composition of those low level bits probably don't look exactly like a loop-by-loop translation.

lol yep, you're 100% right.

Yeah, I totally get that, but I suppose my argument would be is if you're going to bother writing your driver in Rust, until there are more mature Rust bindings for the OS interfaces, you might as well only write your most safety-sensitive business logic in Rust, and then write all the interfacing with the OS in C.

That doesn't bother me per-se - those all caps names are pretty much all directly from the standard C bindings, and it makes sense to preserve that naming for the sake of having that 1:1 mapping with the ground truth C definition.

The actual issue here is that this "simple driver in Rust" is having to touch those direct C bindings at all - if Microsoft is going to advertise that they have support for writing drivers in Rust, that should presumably mean an API surface that's native to the language.

And I don't know how I missed this, but attempting to use the `UNICODE_STRING` returned in `string_to_ustring` is a guaranteed use after free. If you're interested in writing Windows kernel code, this is not the place to start.

The code here looks to be essentially C with different syntax - every function marked unsafe, all resources manually managed. Sorry to be blunt, but what's the point of this?

This is kind of a weird framing. 30 days is longer period than probably acceptable, but most people get regular, lagging biweekly paychecks rather than getting their paycheck paid out continuously in infinitesimal chunks.

Given that their average post seems to only get 10s of interactions despite their account having 10 million followers, I don’t think they were getting much out of being on X anyway.

Believe it or not, a well equipped military is in fact a bipartisan issue.

Insane how many words the author uses to capture "costs are higher for US game studios because salaries are higher". There's no actual secret second thing and it's hilarious watching the author try to find a way to spin "people make more money" into a problem with capitalism.

> they're completely entitled to feel that way, if that helps them cope

This is actually not a productive way to cope and it’s good advice to tell people not to cope this way.

Headline actors are inevitably going to be (already are?) selling the rights to their voice and likeness, setting up perpetual revenue streams for their estates, and in the next few years the parameters of those rights will almost assuredly be in every contract.

I can tell you from personal experience they will not repair Apple Watches - they recycle them and charge a pretty hefty replacement fee if you do not have AppleCare+. I had a Stainless Steel Apple Watch Series 6 just outside the 1 year warranty. The display came dis-attached from the frame, either because the adhesive failed, or the battery had swollen. Like, literally I was just driving down the road and the display started hanging off the watch from its flex. The Apple Store wanted $400 to replace it - would not even evaluate a repair.