Just Google it. There's tons of research on this so I don't know why I need to provide a specific link when this is common knowledge.
But also here is something to think about: your body will produce more D3 than that by being in the sun for just several minutes. So if you consider such a low dose of D3 an overdose then you better steer clear of the sun!
> But also here is something to think about: your body will produce more D3 than that by being in the sun for just several minutes. So if you consider such a low dose of D3 an overdose then you better steer clear of the sun!
This is another superficial statement, that displays shallow-at-best understanding. Staying in the sun and producing via the skin, and intake via food are 2 separate pathways. You cannot just make wild assumptions about one of those pathways from stuff you know about the other pathway.
And actually: Yes, you shouldn't stay in the sun for too long without proper protection. Having the sun shine on your skin is not some inherently healthy thing. It too comes with acceptable dosage and overdose. Symptoms of overdose are commonly known as getting a sunburn.
You can find scientific papers on a lot of search engines, not only Google.
The problem with that is, that you still need to know how to interpret any results and statements within the supposedly scientific papers. If you are not a statistician, you might overlook methodology mistakes. If you are not an expert in the matter of the paper, you might not realize some side condition, that makes some statement or result of the paper irrelevant for your individual situation.
For what its worth, I had the same experience with Tailwind. I regularly see classes that don't have an meaningful outcome.
I don't think the problem is Tailwind or CSS (well, I guess Tailwind is CSS with extra steps but you get the idea) syntax (or any of the CSS preprocessors), but the fact that styling in browsers has accumulated a lot of cruft, and people who haven't "grown up" with it over the years don't fully understand it (I am more competent than most with it and there's still times I screw up).
One thing that's kinda nice about Tailwind is that it made copy-pasting components easier. So people can get something decent without fully understanding what's happening
I mean stuff like adding `display: block` on the parent and `flex: 1` on a child element. Clearly a copy-pasting leftover because someone or whatnot, but then you're debugging a layout issue and you're wondering "but why is this here"
I don't mind the dialogue, but if we're taking about the same author, some of the content gets diminished by the meandering waffling.
I realise it's a stylistic choice but there's been a few posts where I felt tired after reading their articles. And it also feels like one of those YouTube shorts sketches where one person pretends to be multiple people and it starts feeling a bit cheap/meh.
I think it would be fine if it they toned down on the interjections/interruptions
I think one of those pedagogical half-truths useful for onboarding people onto an idea across different languages or getting parts of a point across, and they cover some similar use-cases.
It's a bit like saying JavaScript's prototypes are classes even though they're technically not (even with the introduction of the `class` syntactic sugar), but for casual discussions it's probably fine to just say "JS class".
But to your point: I wouldn't really phrase the way the GP did; it makes it seem like they're on the same level of usefulness as a type class!
I think the barrier to entry with Rust is lower than C++. Like was way lower... And I've been writing C++ for way long than Rust, so I'm probably a bit biased
Var wasn't "a mistake", and there's still (albeit niche) use cases where var makes sense. But for most cases, you do want to write a let/const declaration, even though they're not "free" technically.
You're saying "force into this and that" like there's some evil omnipotent entity compelling people to write Rust against their own free will lol. What do you mean by forced? People enjoy writing Rust, so hence it's being written in other projects.
Saying LLVM is written in C++ doesn't really bring much to the discussion. It was released 25 years ago, and C++ was released 40 years ago (hey, it's older than me lol). Rust was released like 10 years ago. So, yeah... I guess it makes sense that they used C++ back then? I'd have picked C++ back then too.
I've written C++ for about 15 years, and I don't have a blind hatred for the languge, but going back to it doesn't fill me with joy either, especially after having written Rust for the past few years.
The module system is more intuitive to use than the preprocessing file concatenation. There's also a nice package manager. I know some people find this a downside though, but I prefer it to fighting autoconf or CMake.
Syntax highlighting for Rust code doesn't lag 10+ seconds.
Symbol search doesn't require three different third-party tools to work.
Documentation is built in AND nice (no doxy doesn't count as nice, not in any universe).
Testing is built in. There's a (mostly) homogeneous build system
The borrowing rules are things you think about in C++ anyway, but Rust just makes it so you don't forget them; there's some clang lints that help with this in C++ anyway.
The syntax, while sometimes a bit noisy, is nicer in the average case, but C++ has been getting better in that regard.
There's much fewer API gotchas with Rust than with C++ (from the top of my head: closures, std::optional, std::variant, iterators, {a..z}values, a managerie of constructors, SFINAE, all these things have pain in the ass built in as a core principle). I also despise function overloading.
The macro system, while I don't like it too much in Rust, makes things
The type system in Rust is so much better it's not even comparable.
But anyway, Rust has some downsides. It requires you to change how you design solution sometimes. The compilation times are crap (but the compilers also does so much).
The military isn't going to allow C++ anymore due to it being a massive security hazard. You can't get away with buffer overflows, use after frees, data races, etc. forever.
Due to an evil entity called the military industrial complex, you are going to be using Rust in the future.
At the end of the day, we're all useful idiots at some point in our lives. I'm someone who leans more on the freedom/libertarian side and dislike what's happening in the EU.
But on the other hand, I do think someone type of content shouldn't be allowed... And it gives me a bit of cognitive dissonance. Take this polish AI crap for example: I think people should be able to freely speak about these issues, and I'm not opposed to them reaching for anonymity even through AI. But on the other hand, we also don't know if this is a foreign misinformation campaign or just a politically disgruntled Pole. I'm okay with the disgruntled Pole voicing their opinion, but I'm not okay with foreign actors manipulating people's opinions.
> But on the other hand, we also don't know if this is a foreign misinformation campaign or just a politically disgruntled Pole
The videos contain at least one mistake that indicates that they were written by a native speaker of Russian (the use of the word prawilny, which is a Russian word (правильный) and doesn't exist in Polish).
It's circumstantial evidence, granted, but enough to point at a Russian origin, at least in the absence of further information.
I think they have some good points (having a deep understanding of tools you use), but I think the path they take achieve those results is misguided.
A stupid example off the top of my head: I use VSCode and often I'll use the integrated git commit feature. But if need to bisect, rebase, merge, or edit a commit, I will just use the CLI. I don't feel like using the commit GUI makes me worse at using git.
All in all, I think the author thinks that familiarity with one tool makes people worse at another similar tool, but I don't think that's the necessarily the case. At worst, memory might fade if the other tool isn't used, but that's fine, it's clearly not used often. As an analogy: if I don't speak German every day, I don't need to be fluent in German either.
Can you give the replyee some pointers, for example? Link to articles or studies that show a different view?
reply