Omin

They are not on the fence about Rust. They are on the fence about JPEG-XL when it entails a major increase in attack surface due to the current implementation being in C++.

Human civilization is very north biased. Almost 90% of all people live in the northern hemisphere.

Another aspect is that there is a large span in the amount of water you can let the rice absorb. A 1:1 ratio of water to rice (not accounting for evaporation) is all you need to cook rice no matter if it's short grain or long grain, but a lot of rice will also happily absorb more, like 2x its weight, if you give it enough water and time. It sounds like you are using long grain rice given the large cooking time and high water ratio.

The fixed ratio doesn't scale all that well, because some of the water is absorbed by the rice and some just evaporates. Even with a lid on water still evaporates. The evaporation portion depends on the type of pot, how long you cook and how much heat you put in.

So, if you only vary amount of rice, you really need some_factor * amount_of_rice + constant_amount and the knuckle rule has that characteristic.

There are knobs on the f and j key so you can find the home row without looking. Similarly, physical buttons in a car can be shaped in such a way that they allow for feeling your position.

There are so many behaviors that fit that description that few would count as addiction. For example eating sweets or junk food, procrastinating, not drinking enough.

I have some experience with a German shorthand style (DEK) and it is more important to write clearly. Shorthand removes most of the redundant information that is present in regular alphabets and words. With regular writing, a small error somewhere can be error corrected using the surrounding context. When I wasn't being careful, I could often read the text shortly after I wrote it, but after a few hours or days it became illegible to me.

There are multiple levels of shorthand, the faster ones drop more and more information from each word if it can be inferred from the context (for someone familiar with the topic, i.e. yourself mainly).

Shorthand never really stuck for me. Learning to write and read it wasn't that difficult actually, but I couldn't quickly scan shorthand notes like I could with regular writing. I suppose that's a matter of practice and I wasn't ready to sink hundreds of hours into just that. One thing I learned from the experience was how frustrating of an experience it is if you're not good at reading. I have always been an above average reader and I couldn't understand how people struggled so much with it. Reading shorthand was effortful and slow, especially at the very beginning for me and that gave me some perspective of how some of my classmates must have felt.

You could make the argument that with strong headwind you should drive slower to optimize for efficiency.

It looks like the author is trying to set up a reverse pleb filter. "Only plebs would like this".

It's supposed to be royalty free, but there are patents for the techniques used in it which are used defensively. If someone has a patent to a technique used in AV1, then they could still demand royalties and some patent trolls have been trying. Wikipedia has a section on it.

https://en.wikipedia.org/wiki/AV1#Patent_Claims

The author himself doesn't seem like a scam artist but he looks like he falls for them. He said he heard about this technique from Michael Neill who he calls "a personal development coach, a really good guy". This "good guy" has a bunch of books and videos on youtube offering the answers to everything: Finding happiness, overcoming shyness, anxiety, being effortlessly successful with just these three easy tricks in 3 months yada yada.

And Win Wenger, who the author says this technique originally comes from, is the author of "The Einstein Factor" which is a book with similarly grandiose claims about improving your mental abilities.

The problem with residential solar is not the panels, it's the installation, connection to the electric network which differs from house to house and having to work with the homeowners.

There are some related studies on the effect of wind turbines on storms and how wind turbines could protect against hurricanes by sapping a portion of their energy. While the answer is that they could, the amount of turbines required for that is enormous.

This one for example mentions in the abstract that by using an amount of turbines collectively making up 300 GW of capacity, it could severely reduce wind speeds of a hurricane: https://www.nature.com/articles/nclimate2120

300 GW is 2/3 of the power consumption of the entire US and you would need all of those in a small-ish area just to dampen, not fully absorb, a catastrophic storm's energy. Even after those wind speed reductions, there is very strong wind.

If you scatter those turbines in a larger area, you can imagine that the effect will be much more diluted. There is so much energy in the atmosphere that we won't put much of a dent in it with our current energy consumption.

1,000,000,000ng is 1kg, so that'd would be as much plastic as solvent by mass.

Light is only the visible part of the electromagnetic spectrum.

Mail them where? To do so, the company needs to provide an address where they would accept such correspondence and they may not do so.

I think op goes too far by including trailing slashes, but being liberal in what you accept (Postel's law) is a bad idea as the last few decades of the web have shown. Once you accept things, you are locked into supporting them forever lest you break compatibility. When there are multiple different implementations of a standard, they grow incompatible over time.

No, because it requires an &Vec<_> and that doesn't implement Default and for good reason. Just ask yourself, where would the default empty vec live so that you could create a reference to it.

When using unwrap_or(&vec![]), it lives in the enclosing stack. Without the reference, you could use unwrap_or_default().

It's not an assumption, √x is defined to be the positive square root (the principal square root). The negative one is -√x.

It's not inadequate. Brightness diminishes for two reasons. One is absorption from cosmic dust (not that big of a factor), the other is that the object appears smaller, but the brightness per unit solid angle from the object does not diminish. If there were just more stars behind that you could see, the sky would have to be much brighter.

It's also cheaper if you don't. It's by far cheaper if you do.

That definition of what is valid or not depends on the type of checker. When you're talking about Rust's borrow checker, then you can take any property that it checks for, such as "there are no aliasing mutable references" or "any variable that is read from has been initialized" and build an example for it that would be correct, but is rejected by the borrow checker.

Here is an example where a variable is definitely initialized, but it will be rejected.

  fn main() {
      let foo;
      if true {
          foo = 1;
      }
    
      println!("{}", foo);
  }

What is the drawing software used at e.g. 3:50 in the video? https://youtu.be/_7vPNcnYWQ4?t=230

This selection effect cannot explain Rust's standing relative to other new languages and neither can it explain why Rust's popularity (as measured by "most loved") increases over time as more and more companies are using it. Here's the history of Rust's "most loved" percentage going back to 2015

  Year - Most Loved Pct. - Rank
  2015 - 73.8%           - 3
  2016 - 79.1%           - 1
  2017 - 73.1%           - 1  
  2018 - 78.9%           - 1
  2019 - 83.5%           - 1
  2020 - 86.1%           - 1
  2021 - 86.98%          - 1

When we kill them, we're shedding more of our blood than theirs.

[...] which will use the local cache instance for the source

I don't understand why browsers aren't always doing this. They already have the image, why redownload it?

I can't reasonably start using such functionality until the PC with the oldest software that I still use has updated or I will have to deal with 2 ways of doing things all the time.

Currently, that's an ubuntu 18.04 machine at work and that doesn't have `git restore`, yet.

This information shouldn't be hidden in some document, it should be one of the first things they tell you about in their README and through their versioning (0.1 and 0.2 instead of 1.0 and 2.0).

The README.md isn't part of the rust code, so it's not checked by this unless you use tools to generate your README from doc comments like https://github.com/livioribeiro/cargo-readme.

restrict is so rarely used that clang has had open code generation bugs for years. Rust would like to use its non-aliasing guarantees to generate better code, but clang is unable to reliably generate correct code.

So even if you manage to reason correctly around `restrict` in C, you can't count on the compiler to translate your code correctly.

GCC also had bugs around restrict, but I don't know about their current status.