Automatic defrag is typically disabled by group policy.
If so, that's not by default. Someone decided to manually push out that policy. Or worse, have a policy of shutting down systems at night and preventing any maintenance overnight at all.
Unless you're running Dolphin (Wii emulation). It can use up to 3 cores, but it's mostly limited by the single-core speed on the main thread. 10% isn't much, though.
Touchpad below keyboard causes unintentional movement unless there's an easy disable button for the touchpad. Most people using it will probably not be typing much - not sure what key size is better for gaming, but key proximity is probably more important.
It's not just about speed. If you render really fast at any other point, you will have tearing - no matter how fast you can render. And honestly, I'm not sure the GPU gives you that information to schedule off of.
To me, it sounded like you were largely conflating double buffering and vsync, or implying that people came up with double buffering primarily to be able to vsync.
You didn't get that from anything I said.
If you're rendering fast enough, there would be nothing stopping you from doing vsync with a single buffer.
Scheduling. You would have to precisely schedule your drawing for the VBI period rather than whenever the CPU/GPU are free. That means putting literally everything on hold to draw a frame at a specific time rather than doing it whenever you have spare cycles.
I'm fairly sure nobody would have thought there was a point to creating such a feature as vsync without the existence of double/triple buffering when its entire purpose is to avoid tearing.
You just gave a verbose version of exactly what I said. And now you're not even refuting that fact, just jumping to some weird trolling claim.
Did you not even realize I wasn't the GP poster and not continuing their argument? I'll agree with you that they have no idea how vsync/buffering works together.
The only argument I made was that double-buffering and vsync are related because one is necessary for the other to work well (despite one coming along way before the other).
How do you "abuse" it? I said it should only happen to automated flags. If it gets flagged for human review, it could even jump to the front of the queue and go back down again very quickly. That doesn't mean you have to stay eligible for that reversal capability if you've shown a repeated failure to understand the content guidelines.
If you don't get notified when your post is taken down, then the response priority goes to the people who are paying attention and are aware that their post was flagged - a small percentage. The majority will probably stay down or the person decides they don't want to fight it.
A false positive that hasn't been seen by a human should be reversible by the poster and restored immediately. It can be added to a queue for human review in the meantime.
Facebook has so many options for getting this right.
I wouldn't say it has nothing to do with vsync. It helps ensure you have a frame ready for the next vertical sync by displaying a couple of frames behind - at the expense of screen lag (unless the game is rendering a couple frames ahead with some kind of predictive algorithm).
USB OTG (if you don't want bluetooth mouse/keyboard) + HDMI, most likely. "Could run [as] a PC" in the same way that any Android phone supporting those features have always been able to do. Doesn't sound like news at all.
Failing to implement speed restriction settings based on GPS
That would be scary. Already, my phone sometimes thinks I've jumped off the Interstate onto the adjacent frontage road (because I passed an exit while changing lanes or similar). If my car suddenly decides to restrict me to 30mph while going 65mph among other cars, that could be disastrous.
Not in the US, it's not. You cannot decrypt DVDs for personal use without violating the anti-circumvention clause of the DMCA.
The law explicitly has exceptions for what these people are doing, and the LoC has made exceptions for criticism/commentary. Personal, fair use decrypting is still prohibited under the DMCA.
And just because he's identified doesn't mean that his records are no longer involved. If they end up with his data in the end, then he still has a right to be involved.
And any 70mm print still in existence will probably be 40 years old (same for any 35mm print). The size of the flaws might be smaller relative to the overall frame size and thus look much cleaner today. It doesn't matter that both came from a 35mm original. A 1mm scratch in either will be a lot less noticeable on a 70mm print.
Slashdot Mirror
Automatic defrag is typically disabled by group policy.
If so, that's not by default. Someone decided to manually push out that policy. Or worse, have a policy of shutting down systems at night and preventing any maintenance overnight at all.
Not on Windows Vista and up.
Right way of generating more profit for them. It's a lottery and they are running the casino.
Unless you're running Dolphin (Wii emulation). It can use up to 3 cores, but it's mostly limited by the single-core speed on the main thread. 10% isn't much, though.
That's an automated service on Windows 10. Try replacing with an SSD.
Touchpad below keyboard causes unintentional movement unless there's an easy disable button for the touchpad. Most people using it will probably not be typing much - not sure what key size is better for gaming, but key proximity is probably more important.
I think your keyboard is broken.
What's there to distinguish? The lawsuit was regarding 'Linux' and not any userspace tools that may have been running on top of it.
It's not just about speed. If you render really fast at any other point, you will have tearing - no matter how fast you can render. And honestly, I'm not sure the GPU gives you that information to schedule off of.
To me, it sounded like you were largely conflating double buffering and vsync, or implying that people came up with double buffering primarily to be able to vsync.
You didn't get that from anything I said.
If you're rendering fast enough, there would be nothing stopping you from doing vsync with a single buffer.
Scheduling. You would have to precisely schedule your drawing for the VBI period rather than whenever the CPU/GPU are free. That means putting literally everything on hold to draw a frame at a specific time rather than doing it whenever you have spare cycles.
I'm fairly sure nobody would have thought there was a point to creating such a feature as vsync without the existence of double/triple buffering when its entire purpose is to avoid tearing.
You just gave a verbose version of exactly what I said. And now you're not even refuting that fact, just jumping to some weird trolling claim.
Did you not even realize I wasn't the GP poster and not continuing their argument? I'll agree with you that they have no idea how vsync/buffering works together.
The only argument I made was that double-buffering and vsync are related because one is necessary for the other to work well (despite one coming along way before the other).
How do you "abuse" it? I said it should only happen to automated flags. If it gets flagged for human review, it could even jump to the front of the queue and go back down again very quickly. That doesn't mean you have to stay eligible for that reversal capability if you've shown a repeated failure to understand the content guidelines.
If you don't get notified when your post is taken down, then the response priority goes to the people who are paying attention and are aware that their post was flagged - a small percentage. The majority will probably stay down or the person decides they don't want to fight it.
Thanks for not disagreeing and repeating me...I guess.
A false positive that hasn't been seen by a human should be reversible by the poster and restored immediately. It can be added to a queue for human review in the meantime.
Facebook has so many options for getting this right.
Bringing back a video connection that you just got rid of is also nothing to write a big press release about.
I wouldn't say it has nothing to do with vsync. It helps ensure you have a frame ready for the next vertical sync by displaying a couple of frames behind - at the expense of screen lag (unless the game is rendering a couple frames ahead with some kind of predictive algorithm).
USB OTG (if you don't want bluetooth mouse/keyboard) + HDMI, most likely. "Could run [as] a PC" in the same way that any Android phone supporting those features have always been able to do. Doesn't sound like news at all.
Failing to implement speed restriction settings based on GPS
That would be scary. Already, my phone sometimes thinks I've jumped off the Interstate onto the adjacent frontage road (because I passed an exit while changing lanes or similar). If my car suddenly decides to restrict me to 30mph while going 65mph among other cars, that could be disastrous.
Not in the US, it's not. You cannot decrypt DVDs for personal use without violating the anti-circumvention clause of the DMCA.
The law explicitly has exceptions for what these people are doing, and the LoC has made exceptions for criticism/commentary. Personal, fair use decrypting is still prohibited under the DMCA.
Intra-library loan
Caller: "The books are coming from inside the library"
An inter-library loan is a lot more useful.
No, no...certainly prep - https://en.wikipedia.org/wiki/...
libraries that don't exist and were probably stolen (or misplaced) years ago
That would be quite a feat.
None. They only care what you do with *their* money.
And just because he's identified doesn't mean that his records are no longer involved. If they end up with his data in the end, then he still has a right to be involved.
And any 70mm print still in existence will probably be 40 years old (same for any 35mm print). The size of the flaws might be smaller relative to the overall frame size and thus look much cleaner today. It doesn't matter that both came from a 35mm original. A 1mm scratch in either will be a lot less noticeable on a 70mm print.