Well, true, but tyres wouldn't make it a double distance, it's not that simple. The case isn't clear, if course, but the claim says that the odometer tried to reduce the range after it got out of the warranty period.
Not saying anything about the merit of the case, just the the claim itself sounds interesting and that if true, you can't wave it away with "you changed tyres".
Fucking hell, that site a million partners who all have "legitimate interest". I've clicked on like a third of them and then gave up. I don't need their shit.
asd
Like others here, I'll almost always do:
I'll frequently also enable Sharpen and either Filmic RGB or Shadows and Highlights, depending on the style I want.
I'll sometimes crop the images.
When I actually want to do manual editing, it'll mostly be a small tweak in the RGB levels followed by Colour balance RGB module. I'll also adjust exposure partially, via masks, and similar other tweaks.
Very rarely ill want to heal something with Retouch.
When I'm really having fun (and time), I'll just go tinker with everything else just to see what happens. It's rare that I have the time, though.
yeah, traceroute might hint at that, if this is what is going on.
I will perhaps be nitpicking, but... not exactly, not always. People get their shit hacked all the time due to poor practices. And then those hacked things can send emails and texts and other spam all they want, and it'll not be forged headers, so you still need spam filtering.
left-pad as a service.
Much better integrated refactoring support. Much better source code integration support. Much better integrated debugging support. Much better integrated assistive (but not ai) support.
Vscode can do many things IntelliJ can, but not all, and many of them require fiddling with plugins.
Usually, JB is also faster (if your dev machine can run it, but in my experience most devs have beefy machines).
I don't know what happened, but since 6.2 rolled out on Fedora a week ago, I've had several bugs. At the very day I updated, I had two outright crashes. It happened a few more times since. My keyboard shortcuts don't work any more. Window layout behaves...odd (haven't pinned it down yet).
Just all-around messy upgrade. Am I the only one with problems, though?
Yep, that was my intention. First, it's low power, so it can be always-on with only a small impact on the power bill. Second, it's only gonna serve a few things - my photography hobby and media library, and maybe a service or two will come with time. If I need other services, I put them on a Hetzner box and they're much better taken care of.
I've done my share of sysadmin work and even a bit of server-room maintenance, I don't want a full-time, or even a part time job. This is mostly gonna sit in the corner, and be quiet. If the prices matched, I would have probably just gone with QNap or Synology, but this way I get the NAS and the disks for the same price.
I think it is a bit more than that.
You point out two things:
So, now, obviously if you wrote the "fuck it", then well, you fix it. If you found the DNS library problem - find a better lib or something.
But if you take the stance "fuck it, there's always something", you don't even have a chance of finding out. If you had a test suite running 10 seconds, and suddenly it's up by 10 more, you would notice. If you had tests running for 10 minutes, you would not.
If you had a webapp or something that always opened "fast", then suddenly it gets doubly slower, you'll notice it. But if you already started slow, you won't notice (or care, or both), when it gets even worse.
I think that's the point of the article. If we all dug in and fixed a little bit, eventually we'd have fast apps or tests or whatever. If you accept that things suck, you'll make it tripply worse. It is a conscious effort to be fast.
It's 12, looks good to me.