I wonder if anyone who's switched to an ergonomic setup has found that it stops working as well over time. Because I have long suspected that the real problems (in many cases) come down to weak muscles. But these ergonomic setups are likely to weaken them even more over a long enough period of time given that they try to avoid all of the strain.
You don't have to be a fan of the game to see the trailer and think it looks bad. I'm certainly not a Deus Ex fan. I played it just once, years and years ago. Yet when they showed the trailer during State of Play I was shocked at how bad it was. It's clearly just some texture upscaling and an update to the lighting. The original looks ugly and this remaster manages to look uglier.
An example of a remaster done right was Halo 1 (which is actually quite an old remaster at this point). They threw a new graphics engine on top but also remodeled and retextured everything. That's what I expect out of a proper remaster.
Oh yeah that's really bad to not have any hints that there's more info. I suspect many people are going to hit that page and think there's nothing useful to see. (It's also partly the fault of browsers for not showing scroll bars, but that's the default so you need to design for it)
That's... exactly my point? They put up the defense because they are "thin skinned". It only looks all strong and macho on the surface when they continue to argue back.
The AI automod can't even tag images correctly. I've seen perfectly innocent drawings get marked as adult or graphic. If it can't figure those out, there's no way it understands enough about what's going on in the images to automatically provide alt-text. At least not well enough that anyone should rely on it when they can just enter proper alt-text themselves.
They might act like it's a macho thing to argue against you, but let's be real, it can be painfully embarrassing to admit you're wrong, especially if you were really dug in already. Since it's about avoiding pain, it's the weak route to take to continue to defend a position you know is wrong.
This might be why I'm finding a lot of these comments so confusing. Because what you're saying here is how I've always operated.
If the first time your reviewer sees what decisions you've made is when the review happens, then of course it will be overwhelming if the merge request is large.
If you keep your reviewer in the loop, and have bounced implementation ideas off of them, then the review basically just becomes a sanity check.
As a reviewer, I don't care how you got to the end result. I want to see the final code. If you settled on something in your code that was unintuitive, because you tried simpler ideas that didn't work, then note that in a comment. Comments provide the info inline and don't require someone reviewing the code now or working on the code 15 years later to read your "commit story" to understand it.
It's not even about sleep anymore. That was what f.lux's intent was back when the research first came out, but now it's been morphed by people trying to sell these glasses into "blue light is harmful". They talk about it like your eyes are getting damaged by blue light. Or that it's defending against eye strain caused by blue light rather than just overall luminance.
> To successfully make a parody case in regards to trademark the parody itself must make it obvious that the defendant is not in anyway connected to the owner of the trademarked thing. The Morgan and Morgan ad doesn't do that; without the disclaimer at the beginning it wouldn't be obvious that the ad wasn't a animation created by Disney.
This is what I was wondering about. Do those disclaimers make it okay? Because without that context it certainly feels like this ad could be officially endorsed by Disney. And that seems to be exactly the kind of thing trademark law is meant to deal with: avoiding trust problems from people being misled about who is selling them what.
The problem is that the write buffer turns copy progress into a complete lie. The last time I put a large file on a removable drive from Linux, the copy finished suspiciously fast. But I thought that surely Linux wouldn't be using a write buffer when Windows hasn't used that on removable devices for 20 years, so I went on my way and shut down the computer... which led to me just sitting at a gray screen. I had to just wait there with no indication of progress or even that it was doing anything at all.
If I wasn't aware of what was happening here I likely would have just force shut down the computer after a minute of waiting. And I suspect if I had done that and checked the drive it would have appeared like the file was there, while actually missing part of the data.
The C# compiler is looking at that code. It sees that the lambda is being passed into a function which accepts an Expression as a parameter, so it compiles the lambda as an expression tree rather than behaving like it's a normal delegate.
You definitely want to ensure buffers are flushed. Because very, very annoyingly it's not default behavior on Linux distros for removable devices to be mounted with write caching disabled. I don't even know of an easy option to make Linux do that. I think you'd need to write some custom udev rule
Seriously, it's bizarre to see this argument from people that Apple isn't caring about what people want in terms of battery life. Apple in their keynote called out that they made the Pro models slightly thicker for the sake of a larger battery! Like, why ignore the standard models of iPhone and only focus on the Air when making complaints?
I'm not saying they're engineering the batteries. But they did have to engineer the whole phone to fit in a very small space without making serious spec compromises. And my statement about their engineers isn't comparative to other companies. They can all have excellent engineering teams at the same time.
I think it's funny how expectation defying the Air is. Most people were assuming that being so thin would mean it's super easy to bend by hand. Zack certainly isn't a weak man and he was unable to easily bend it by hand. People have also been assuming the battery must be terribly small, but its capacity is larger than the iPhone 15 battery was and only 100 mAh smaller than the iPhone 16 battery was.
Apple has seriously good engineers to be able to make that happen in a device that's so thin.
A few years back I fumbled my iPhone so badly that when I tried to catch it I knocked it further up in the air. It flew up dropped all the way down to the concrete subway platform I was on, landing face down. It was loud and worrisome, but the phone was perfectly fine outside of some scratches on the lip of aluminum around the screen.
So it seems like the screens are not easily broken anymore. Though that event did lead to me using a case on my next phone just to avoid chancing cosmetic damage on it.
How do you propose making a device that people wouldn't feel the need to put a case on? You could make the whole thing out of rubber but that's still going to take cosmetic damage that people want to protect the device from. You could make it easy to replace that rubber... but at what point is that not just functionally the same as a case?
Interesting! I'd certainly say that's worth something. Definitely didn't expect it though given how poorly some people have reacted to Rust being introduced as an optional part of the Linux kernel.
Does anyone with insight into Git development know if we should care about this? Is this just a proposal out of nowhere from some rando or is this an idea that a good portion of Git contributors have wanted?
Yeah I'm really not sure why people take doing things that their employers don't want them doing as a challenge. Like how about the challenge instead be working within the restrictions? Or communicating with their boss what they need to get their job done?
They have no clue what legal requirements are imposed on the company that led to those restrictions. They could easily land themselves or the entire business in hot water by not complying. It doesn't matter how easy the controls are to bypass. Like, it's easy to pick or cut a LOTO lock, but that doesn't mean it's fine to do that.
You say that like it has an understanding. If I could have forked the conversation after it gave a unicorn I would have, but I was able to start my own and ask for ASCII art of a parrot. On the first try it gave me a sitting penguin (probably Tux art from the training data)
When I then asked it if the image was really a parrot it told me that it was "more of a generic 'ASCII bird' (often used as a generic owl/parrot placeholder), not a true parrot."
A sitting penguin is certainly not a generic bird.
I'm not sure why it seems you have downvotes for saying that. Premium users by their very nature need to be logged in. YouTube has all of the watch stats for logged in users without needing the view to hit an extra analytics endpoint. They can and should just use that.
Memory training taking minutes on AMD systems isn't unusual. On my desktop with a 7800X3D and 64 GB of RAM, I get scared whenever the system needs to do the training again. Because it just sits there at a black screen for a couple minutes while it does the training. I have to just wait and hope that it's doing something and not that my system is dead.