C++ [](){} looks nice.
solrize
joined 2 years ago
"I believe in term limits and do not think Congress should be a lifelong career or an assisted living facility." Woah lol, shots fired.
Aren't there already tons of these already? Piwik has been around for a quite a while, plus there are others mentioned in the comments.
While all controllers should eventually be disbursed their back pay (Government Employee Fair Treatment Act of 2019)
Does that not constitute a government debt then? I thought the shutdown was due to hitting a debt limit. If there was a relief mechanism to create more debt for special situations like this anyway, why not just pay the ATC's immediately through that same mechanism?
ORCHARD PARK, N.Y. — Police executed a search warrant at the home of a University at Buffalo student after he allegedly threatened to “shoot up the school,” prompting an investigation.
Not to mention Star Trek.
Rust has exceptions? Is that new?
“What’s the thing that fundamentally moves the needle on what’s out there already today?” he said. “The only thing, in my opinion, is rapid reuse. And once you get it, the economics are so powerful that nothing else matters. That’s the thing I couldn’t get out of my head. That’s the only problem I wanted to work on, and so we started a company in order to work on it.”
Web search shows max CPU power for that unit is 65W. I was thinking of something more power hungry.
This is great. Soon military organizations all over the world will be recruiting poets to compose their cyberattack prompts.
It looks like they ran the test case and triggered the crash. Therefore the issue is not confabulated.
Also, I'm unconvinced that use of ffmpeg inside of Google services is relevant to this. Google services can sandbox executables as much as they like, and given the amount of transcoding they do (say for youtube), it would surprise me if they're not using gpu or hardware transcoders instead of ffmpeg anyway. Instead, they may care more about ffmpeg as used in browsers, TV boxes, and that sort of thing. That puts them in the same position as the Amazon person who said the ffmpeg devs could kill 3 major [Amazon] product lines by sending an email.
If a zillion cable boxes get pwned because of a 0-day in ffmpeg, well that's unfortunate but at least they did their due diligence. But if they get pwned because the vendor knew about the vulnerability and decided to deploy anyway, that potentially puts the vendor on the hook for a ton more liability. That's what "ffmpeg can kill 3 major product lines" means. So "send the email" (i.e. temporarily flag that codec as vulnerable and withdraw it from the default build), seems like a perfectly good response from ffmpeg.
The Big Sleep article is really good, I read it a week or so ago, sometime after this thread had died down.