xthexder

That's definitely a non-trivial amount of data. Storage fast enough to read/write that isn't cheap either, so it makes perfect sense you'd want to process it and narrow it down to a smaller subset of data ASAP. The physics of it is way over my head, but I at least understand the challenge of dealing with that much data.

Thanks for the read!

Neat, thanks for sharing. Reminds me of old mainframe computers where students and researchers had to apply for processing time. Large data analysis definitely makes sense for C++, and it's pretty low risk. Presumably you'd be able to go back and reprocess stuff if something went wrong? Or is more of a live-feed that's not practical to store?

It really depends what you're doing. The last big project I did with C++ templates was using them to make a lot of compile-time guarantees about concurrency locks so they don't need to be checked at runtime (thus trading my development time for faster performance). I was able to hide the majority of the templates from users of the library, and spent extra time writing custom static_assert messages.

C++ templates are in fact a compile-time turing complete language, as crazy as that sounds.

Yep, sadly I've been exposed to a few such codebases before. I certainly learned a lot about how NOT to design a project.

You've been at it longer than I have, but I've already had coworkers look at me like I'm a wizard for decoding their error message. You do get a feel for where the important parts of the error actually are over time. So much scrolling though...

I thought StarLink had inter-satelite laser links? Theoretically it should be faster than a VPN out of the country because light travels faster in a vacuum. But maybe this was another one of Elon's "full self driving next year!" features.

Yep, I learned about this exact case when I got my engineering degree.

I guess you've never seen some of the 10-page template errors C++ compilers will generate. I don't think anything prepares you for that.

I'm not sure how I feel about someone controlling an X-ray machine with C++ when they haven't used the language before... At least it's not for use on humans.

I understand what you mean. Water vapour (i.e. clouds, fog, the visible part of what comes from boiling water which any normal person would call steam) vs Gaseous water (i.e. most of the atmosphere, and the non-visible part of boiling water also called steam steam).

Vapes work by boiling PG/VG which starts as a liquid (i.e. the juice), and generates both vapourized and gaseous PG/VG. If it was water, any normal person would consider this steam. This isn't a chemistry or physics class.

I don't think there's a need to so pedantic here. Water vapor is the visible part of steam, and for the purposes of this discussion, we're talking about boiling liquids, so I don't think there was any miscommunication by using the word "steam"

Our data suggest that the flavorings used in e-juices can trigger an inflammatory response in monocytes, mediated by ROS production, providing insights into potential pulmonary toxicity and tissue damage in e-cigarette users.

Well, I guess that's a point against flavored vapes. I really wish there were more studies, because presumably not all flavorings would have the same effect. A comparison with unflavored e-juice would have been great.

Yeah, this is just me tacking on extra features I'd like. My security-minded programmer brain can't help but think of all the edge-cases. It's something that is suddenly possible with distributed social media that never was before.