It depends on the person, as a sample size of one I was on 5,000IU and my levels were still on the low end (almost still deficient), and my calcium levels were still safely on the low side as well. Ultimately people should be getting their levels checked before and after to see exactly what the effect on them is
As others have mentioned there already is the ".home.arpa" TLD but I definitely think ".internal" is a step up in terms of clarity. That said, for my internal network I just put things under a subdomain of a domain I own so I can use HTTPS with a proper SSL cert
>Isn’t there a word for when a lot of math and complexity and specific numbers with names imbue an article with some extra sense of being true or having authority?
My problem with shower thoughts is often I have too many and it's a struggle to hold on to them all until the end of the shower so I can actually write them down
Generally yes, although I definitely wish the initial load was speedier the better looks and "flow" are worth it imo.
I usually browse Reddit using Relay and look at my saved posts on desktop, which has benefited a lot from the redesign since I can just do stuff in a single tab instead of middle-clicking a bunch of posts.
There are definite a lot of advantages to building with web technologies, it's just that Electron is an excessively heavy way of enabling it since it basically just gives you a webapp with a whole browser bundled in. PWAs are a much better alternative since you can just use the one browser instead of having one running for every Electron app.
I've found myself preferring type guards for checking action type, since it avoids you having to have keep one big `Actions` union around that takes X amount of lines and really doesn't serve any other purpose.
I was surprised at just how comically angry people were over this. I can kind of understand their arguments against a trend of being too change-happy and over-correcting, but these things really should be considered case-by-case, not on whether it's part of a trend. It's an opportunity to use more descriptive terms, with being less insensitive as a bonus, and neither of these warrants the level of hate that's been coming out.
Really, "master" and "slave" are pretty overused in tech for situations where it only kind of makes sense if you squint. There are a couple of examples of this. For databases, "master" and "slave" doesn't accurately describe the relationship, its more like "original" and "copy". For git, "master" as a name doesn't really make sense either since it implies it's master of something, when "main" or "primary" is closer to the truth.
I also remember seeing "dom" and "sub" being suggested somewhere, and even if it was a joke I'm all for it.
Inbox has got to be the single most useful productivity tool for me. Pinning, bundling, and snoozing just make managing emails so quick and efficient since you can easily triage and get rid of what doesn't matter, and Gmail as it currently stands just can't compete.
If bundling and pinning aren't brought over to Gmail like snooze, Gmail is basically dead to me from an efficiency perspective since manually selecting what you want to remove takes significantly longer than pinning and sweeping in Inbox.
Worse still, there's the opposite problem if we wanted to build an Inbox successor on top of Gmail since while bundling and pinning would be easily implemented by the client, snooze is still not part of the Gmail API[1] so there would need to be a completely separate layer of snoozing in the client.
Honestly, if a competitor were to rise and implement Inbox's feature set, my money is on the table.
Phyles primarily based on shared values honestly seem more sensible than nation-states primarily based on geography (although of course these may overlap). The latter often seems to lead to the 51% being the decision makers which leaves the 49% unhappy.