One of the choke points of all modern video codecs that focus on potential high compression ratios is the arithmetic entropy coding. CABAC for h264 and h265, 16-symbol arithmetic coding for AV1. There is no way to parallelize that AFAIK: the next symbol depends on the previous one. All you can do is a bit of speculative decoding but that doesn’t go very deep. Even when implemented in hardware, the arithmetic decoding is hard to parallelize.
This is especially a choke point when you use these codecs for high quality settings. The prediction and filtering steps later in the decoding pipeline are relatively easy to parallelize.
High throughput CODECs like ProRes don’t use arithmetic coding but a much simpler, table based, coding scheme.
FFv1's range coder has higher complexity than CABAC.
The issue is serialization. Mainstream codecs require that the a block depends on previously decoded blocks. Tiles exist, but they're so much larger, and so rarely used, that they may as well not exist.
Pulling a percentage out of my ass that can't be terribly inaccurate, 99% of police encounters with guns drawn the police are under 21 ft away, at which distance a knife is as dangerous as a gun.
If someone is less than 21 ft from you and they are going to be using a knifes against you, then you should still draw a gun just as often as if they had a gun. So at <21 ft you think guns should be drawn less because they have knives you should also be thinking guns drawn the ~exact amount less no matter which of the 2 weapon they had.
I don't dispute that. But in most those 'other countries' literally anyone could be hiding a knife as easily as someone in US could be hiding a gun. So it appears in the vast majority of the cases where people are already right next to each other where both a knife or gun could kill someone, whether it is a knife or a gun is almost a moot point. It's only at a distance that you can treat a knife as a less lethal threat. Therefore the problem lies with the police, by vast majority.
A knife is not equivalent to a gun. One is a kitchen appliance that can be used as a rather ineffective weapon, the other is a tool literally designed for eliminating life as efficiently as possible
Disarming someone who poses a threat with a knife (especially via the use of modern equipment) is absolutely possible and can be performed in most cases with training, even with just one officer. Meanwhile, disarming someone with a gun is a much more complex task, often requiring a coordinated effort from multiple officers
>a knife (especially via the use of modern equipment) is absolutely possible and can be performed in most cases with training
I want to see you attempt that in real life when someone is within 21 feet. If you watched enough training videos and the literal flood of body camera videos that show even tasers are more often than not infective you would not speak so conveniently about a split second life or death situation.
> I want to see you attempt that in real life when someone is within 21 feet
Sadly I did not film it, but you could have been! I have attended multiple classes during which I had to disarm people with knives and other weird objects. It is absolutely possible with the right circumstances and training, but it's a completely different story when it comes to guns - the element of luck is much more meaningful, as a instructor who was shot quite a few times in their career has pointed out
> You can but you absolutely should not try just because you can in training
For incapable civilians like me - absolutely. But I expect more from police officers than from myself when it comes to non-lethal disarming capabilities
>But I expect more from police officers than from myself when it comes to non-lethal disarming capabilities
It's asinine to expect someone to put there life in danger for little to no benefit just because they are trained for it and there is a chance it might go well instead of certain death.
If someone comes at someone with a knife (which is deadly force), they should expect to be met with equal or more force, this isn't some game with retries. Others don't have to go along your stupid games just because you drag them into them. Play stupid games win stupid prices.
> It's asinine to expect someone to put there life in danger for little to no benefit just because they are trained for it and there is a chance it might go well instead of certain death.
Whether it's asinine or not depends on context. Where I live, it is expected for police officers to protect you with their lives from a lethal threat if necessary, both legally and socially, and failure to commit to that means that you shouldn't be a cop
For the US, I think that the Uvalde shooting revealed a lot about what people actually expect from cops in life threatening situations, never mind what they are legally obligated to do
I'm glad you're making this point. It's something that only people trained in combat would know, and it's very non-intuitive. But it has to do with reaction times, how quickly the person wielding the gun can pull the trigger, and how quickly the person wielding the knife can move. That 21 feet can close blindingly fast.
> under 21 ft away, at which distance a knife is as dangerous as a gun.
No, it is not as dangerous.
To use gun from 7 meters away, you have throw it, which takes way more movement hand movement and time. While you should not rely on it, it is very feasible to just move out of the way of the thrown knife.
Other possibility getting closer to you. Running will take 2 seconds. (Not a lot, but definitely not as dangerous as a handgun)
The statistic isn't related to thrown weapons. It's how quickly you can close the space between you and your adversary, as well as how much bearing drift you can create as you do so.
Then you shouldn't be a police officer. We can't have a society where police shoot first and ask questions later just because they want to make sure there is zero risk to them.
> Basically if someone has physical access to device, its game over.
It took more than a decade to exploit this vulnerability and even then there are fairly trivial countermeasures that could have been used to prevent it (and that are implemented in other platforms.)
Nothing is unhackable, but it requires a very peculiar definition of "game over".
(And as others have pointed out: only early versions of this Xbos One where vulnerable to this attack.)
The incentives to hack the XOne were few. Easy sideloading. No exclusives. Not a great performance per dollar ratio either. It is the opposite of Nintendo consoles if you think about it, and nintendo consoles are notorious for having a really quick homebrew scene.
Every time a console gets hacked, the checklist of SOC security architects grows a little longer. Boot ROMs are written in formally verifiable language, there are hardware glitch detectors, CPUs running in lockstep to guard against glitches, checks against out of order completion of security phases, random delay insertion, and so forth.
When it comes to SOC security, the past is not a good predictor of the present. The previous Nintendo SOC was designed 15 years ago. A lot has been learned since. It's become increasingly harder to bypass these mechanisms.
The fact that it took 13 years to hack the Xbox One is not because it's not an attractive platform: because of its high profile, it has been a popular subject for security research grad students from the moment it was released. And if anything, the complexity of the current hack shows how much SOC security has progressed over the years.
> The 4% improvement doesn't seem like it's worth the effort.
I've spent the past few months improving the performance of some work thing by ~8% and the fun I've been having reminds me of the nineties, when I tried to squeeze every last % of performance out of the 3D graphics engine that I wrote as a hobby.
FWIW, the 4% rule is for safe withdrawals for around 30 years of retirement, as in, you retire at 65 and you hope to live until 95, and even then it has a non-zero chance of running out of money. It's not a percentage you should use if you want to retire at 40.
4% is the standard number that's quoted by pretty much any financial planner. It's based on backtesting and assume that there's be large downswings along the way.
You have a lot more flexibility around those downswings at 40 than you do at 80. For example you could retire but continue doing work that brings you joy and also happens to make money. A lot of people in this situation start lifestyle businesses or do consulting work, for example.
At $4mm in a market account (not 401k), you also have the option to take out margin loans at shockingly low interest. This gives you untaxed cashflow without touching your principal. 160k untaxed is a lot more cashflow than the same number in salary or retirement distributions.
I'm sick and tired of the "No..., no ..., (just) ..." LLM construction. It's everywhere now, you can't open a social media platform and get bombarded by it. This article is full of it.
I get it, I should focus just on the content and whether or not an LLM was used to write it, but the reaction to it is visceral now.
Option B: use Amazon Prime Video to watch shows. Share your viewing habits with Amazon.
reply