You could look into running a Tor bridge (not a normal relay). It generally uses little CPU so there's little concern about carbon emissions. You can also limit the amount of bandwidth the bridge uses.
There's a couple interesting hypotheses in that article I wouldn't have thought of. However, I think they left out an obvious culprit, the lockdown meant that kids were home all day, which means less physical activity, and possibly a worse diet eating at home as well. One kid I know, used to be slim and running around all the time. I didn't see him for over a year after the pandemic began, gained 30 lbs and just played video games all day. His mom let him eat whatever he wanted, which was mostly junk food, and plenty of it.
Many children likely have a predisposition to developing diabetes, but they don't due to good diet and exercise. Take that away, and you'll see a significant rise in childhood diabetes. I'm not saying this is the sole cause of all these cases, but it also seems like a glaringly obvious omission.
I believe you are confusing Type I diabetes and Type II diabetes.
Type I diabetes your immune system destroys your insulin producing cells. You need to provided all of your insulin via injection/pump.
Type II diabetes is more akin to insulin resistance / inability to produce the correct amount of insulin. (It is more subtle then this in reality). Type II diabetes is tied to levels of activity and food (esp high sugar) intake.
In Type I diabetes, there is usually a genetic component as well as an environment event which causes the unfortunate autoimmune response. This article is talking specifically about a significant uptick in Type I diabetes cases.
No need to re-encode the video. Just split the video at a keyframe and inject an ad at that point, no re-encoding required. Most video files have keyframes every few seconds or so. The proper term is I-frames, though they're commonly known as keyframes as well.
I used D for a while several years ago. The language was always a huge mess. The compiler and standard library were riddled with bugs. D was the only language I ever used where it could actually be a compiler bug. D was a mess of features that didn't play well together; things were added with little thought or care given to they'll fit with existing language features. I speak in past-tense because I haven't paid close attention to D's development in several years, but it seems like every time D pops up in some news feed, it's never good. Seeing posts like this, it seems like things haven't improved much. I've seen a few posts like this over the years complaining about minor releases introducing breaking changes.
I understand building a language and compiler is hard. However, D is over 20 years old at this point. It's had plenty of time to mature despite being a small community project. There are much younger languages which are far more stable. Minor releases should not be introducing so many breaking changes, breaking backwards compatibility. D is actually a pretty nice language, has a lot of great features, but I would never recommend it to anybody.
Exactly. Even if the software is never updated with any new features or changes, it still requires constant maintenance to fix bugs, patch security vulnerabilities, support new hardware, and OS updates. It costs money to maintain software, and a lifetime license isn't going to pay for a lifetime of updates.
They provided links to the benchmarks so you can try running them yourself. I feel like a prerecorded video would add little value to this announcement.
Exactly my attitude. Not just for Edge, I use Microsoft products and services as little as possible. Even if they might be technically superior, I will go with the solution that isn't being shoved down my throat.
> James Lovelock argued that we could save the rain forests from the ravages of man by burying nuclear waste in them.
Interesting thought, but would be a horrible thing to do to the indigenous peoples of the rain forests.