The body will develop a tolerance (or the reverse, a sensitization reaction) to just about any substance that's taken regularly due to homeostasis. However, so long as you're taking a dose that nudges some physiologic signal/need in the right direction, your body's response to the substance will be minimal.
I'd be surprised if you can find anything this isn't true for.
A lack of studies on what the tolerance looks like for a particular substance does not imply that tolerance does not form.
In the case of melatonin: It's almost universally true that your sleep quality is worse than it was before once you stop taking it (for a few days at least). That's an indication that your body's equilibrium has changed from habitual use.
You're right! Edited the post...thanks for pointing this out was actually a mistake on my part the article was about incorrect dosage which was the point I wanted to make.
Probably synthetic benchmarks that don't represent actual bottlenecks in application usage. How much of what you are doing is actually CPU bound? Your machine still has to do I/O, and even though that's "very fast" these days, it's not happening inside your CPU, so you'll only see the actual improvements when running workloads that benefit from the performance improvements (i.e., complex calculations that can live in the CPU and its cache).
I’ve been thinking about this a lot lately. Kinda like the adult equivalent of learning that Santa isn’t real or finding out your parents are getting a divorce. I believe that we put too much faith in our “bedrock institutions” because we were taught to. Now, the facade is gone, and we’re left to figure things out as best we can. I don’t have a clue where the future will take us (nobody does). But, there’s usually some good that comes with the bad, and I do have the feeling that we’re living through history, much more so than I ever thought we’d get to. If we are truly witnessing the downfall of the United States, well… it’s going to be very interesting to say the least.
It's certainly not like it was perfect here in the past or that the mythology reflected reality, but it felt like there was a fairly long arc of 'getting better in fits and starts' The cold war was over and we stopped supporting heinous dictators. Everyone could vote. Gay people got the right to marry. Things weren't perfect, but we had the means to work hard to make them better.
Yeah, it felt like the U.S. was stumbling towards a more just and equitable future, and media and popular culture perpetuated a narrative that we were MUCH further along as a country and culture than we actually were. To the point of just representing a false reality. Then, all of the sudden, reality came crashing down, and it became pretty evident that a huge chunk of the country doesn't give a damn about any of that stuff, nor can they be bothered to waste a minute worrying about the consequences of re-electing a felon, etc. They just want cheap eggs, which they're still not getting, but they are getting an entirely new type of governance, which looks pretty darn authoritarian, but who am I to say...?
The dollar has really taken a beating though. It has fallen ~11% this year and is predicted to fall another 10% next year. If you're in cash, you're basically betting the market is going to fall over 20% between the beginning of 2025 and the end of 2026.
You can hedge with PUTS, move into precious metals, put your money in CHF, etc. There are all kinds of ways of maneuvering financial turmoil (albeit, sometimes with non-productive assets), but it really depends on your risk outlook, and as we all know, we're bad at predicting the future.
Alas can't - employer prohibits any use of derivatives.
Plus my last adventure down that lane didn't go great. (Some big wins, some big losses and a realisation that I better leave things I don't fully understand alone - like the options greeks).
Of course you have to do whatever makes sense for you, but nothing is stopping you (or anyone) from spinning up a Fidelity account and hedging against whatever is driving your 401k, etc. Portfolios don't have to exist as monoliths.
Some are so vastly better that it's worth whatever small inconvenience comes with getting them installed. I know the classic tools very well, but I'll prefer fd and ripgrep every time.
For my part, the day I was confused why "grep" couldn't find some files that were obviously there, only to realize that "ripgrep" is ignoring files in the gitignore, that was the day I removed "ripgrep" of my system.
I never asked for such behaviour, and I have no time for pretty "modern" opinions in a base software.
Often, when I read "modern", I read "immature".
I am not ready to replace my stable base utilities for some immature ones having behaviour changes.
You did ask for it though. Because ripgrep prominently advertises this default behavior. And it also documents that it isn't a POSIX compatible grep. Which is quite intentional. That's not immature. That's just different design decisions. Maybe it isn't the software you're using that's immature, but your vetting process for installing new tools on your machine that is immature.
Because hey guess what: you can still use grep! So I built something different.
Sounds like the problem you have here is that `grep` is aliased to `ripgrep`. ripgrep isn't intended to be a drop-in replacement for POSIX grep, and the subjectively easier usage of ripgrep can never replace grep's matureness and adoption.
Note: if you want to make ripgrep not do .gitignore filtering, set `RIPGREP_CONFIG_PATH` to point to a config file that contains `-uu`.
The very first paragraph in ripgrep's README makes that behaviour very clear:
> ripgrep is a line-oriented search tool that recursively searches the current directory for a regex pattern. By default, ripgrep will respect gitignore rules and automatically skip hidden files/directories and binary files. (To disable all automatic filtering by default, use rg -uuu.)
It's odd how, with every new tool that emerges, some people fixate solely on whether it’s an exact clone of what they already know. They overlook the broader differences and trade-offs, treating anything less than a complete replica down to its quirks as unworthy of anyone's attention. While insults like "immature" are rarely thrown around right away, it's a frustratingly narrow perspective.
Regarding ripgrep: if it's not bug-for-bug compatible with grep, it’s deemed useless. Yet, if it is identical, then why bother using it at all? What kind of logic is that?
Same here, we have a lot of noise in our area. I have a LectroFan, and it's invaluable. It's simplicity is what makes it so great. We don't need apps for everything. In fact, I prefer to avoid them when possible.
Batching in general is slept upon. So many queue systems support batch injection, and I have seen countless cases where a poorly performing system is “fixed” simply by moving away from incremental injection. This stuff is usually on page two of the docs, which explains why it’s so overlooked…
My guess is that this is because our default way of expressing code execution is the procedure call, meaning the default unit of code that we can later is the procedure, which needs to execute synchronously. That's what our programming languages support directly, and that's just how "things are done".
Everything else both feels weird and also truly is awkward to express because our programming languages don't really allow us to express it well. And usually by the time we figure out that we need a more reified, batch-oriented mechanism. (the one on page 2) it is too late, the procedural assumptions have been deeply baked into the code we've written so far.
See Can programmers escape the gentle tyranny of call/return? by yours truly.
This analysis makes sense to me, but at the same time: we’re already switching between procedural and declarative when switching from [mainstream language] to SQL. This impedance mismatch (or awkwardness) is already there, might as well embrace it.
We are switching...but how and at what cost? We put SQL programs as strings into our other programs, often dynamically constructing them using procedure calls and then dispatching them using yet more procedure calls.
If that weren't yikes enough, SQL injection bugs used to be the #1 exploited security vulnerabilities. It's gotten a little better, partly because of greater usr of ORMs.
Ah, yes, you must be comparing NPR to all of the fair and balanced “clear eyed” right wing media we’ve come to know and love. No extremism or bias there whatsoever… /s
PBS and other stations represented the center for a long while. The Overton window just keeps moving. Nowadays basic stuff like getting vaccinated has been politicized along with a zillion other things that used to be considered “normal”. Makes sense if your main mission is to expand attack surfaces but sucks for the rest of us.
Most pasta labels specify what seems like a ridiculous water to pasta ratio. Something like 4-6 quarts of water for a pound of pasta. Does anyone know if there's a good reason for this? I never use that much.
It’s what you’d use in a restaurant where you are cooking pasta in the water all day and therefore built up a lot of starch in the water. At least according to Kenji Lopez.
I guess that means you don’t want the first pasta order of the day.
