The classical example is 4/4 不是. Which goes bùshì -> búshì.
Or 3/3 that becomes 2/3. E.g. 你好 nǐhǎo becoming níhǎo.
The 1/4 -> 2/4 transformation I think is specific to one. 一个 yīgè becomes yígè.
7,934 karma · joined September 1, 2017
The classical example is 4/4 不是. Which goes bùshì -> búshì.
Or 3/3 that becomes 2/3. E.g. 你好 nǐhǎo becoming níhǎo.
The 1/4 -> 2/4 transformation I think is specific to one. 一个 yīgè becomes yígè.
There's a simple trick to avoid that, use `.clone()` more and use fewer references.
In C++ you would be probably copying around even more data unnecessarily before optimization. In Rust everything is move by default. A few clones here and there can obviate the need to think about lifetimes everywhere and put you roughly on par with normal C++.
You can still optimize later when you solved the problem.
After Win11 Microsoft really did all they could to get us there this year.
// Create an LRU cache with a capacity of 100 entries
let mut cache = LRUKCache::new(2);
Why 100? Why not 2?I know very fit people that still fall well in the BMI 20-25 range. Most around 23. You have to be very focused on natural bodybuilding for years if you want to become an outlier on BMI.
Or some combination with being super short or super tall. But this again affects a tiny minority.
Additionally the fatter you are the more calories you use at rest. So there's a point where if you consistently eat too much you'll stop gaining weight.
The biggest source of error here will be the calories in the garbage bin though. I wouldn't be surprised if a lot of this is stored in the waste disposal, not the waist disposal.
The food producers need to be sanctioned. It's unsustainable for a whole nation to be on these expensive drugs.
If you think an outside perspective is irrelevant I'm also not sure why you don't just move on and not comment.
I was wondering how you could get such a high impact overall. But it seems one in 6 households are on GLP-1 drugs in the US.
In my friend circle in Germany I don't even know one single person on this stuff.
It's insane to me that so many people need these to get off the processed foods killing them in the US.
Now I'm wondering if I'm prompting wrong. I usually get one answer. Maybe a few options but rarely the whole picture.
I do like the super search engine view though. I often know what I want, but e.g. work with a language or library I'm not super familiar with. So then I ask how do I do x in this setting. It's really great for getting an initial idea here.
Then it gives me maybe one or two options, but they're verbose or add unneeded complexity. Then I start probing asking if this could be done another way, or if there's a simpler solution to this.
Then I ask what are the trade-offs between solutions. Etc.
It's maybe a mix of search engine and rubber ducking.
Agents are, like for OP, a complete failure for me though. Still can't get them to not run off into a completely strange direction, leaving a minefield of subtle coding errors and spaghetti behind.
Then there's the really open source Rancilio PID Clever coffee project:
https://github.com/rancilio-pid/clevercoffee
Different machine, similar approach, a bit more DIY since you can't buy a kit.
I think it's more of a supply and demand thing. People spend a lot on their hobby. And it's not as much mass produced as some other items.
I think that's the bigger issue in Java. `int` can't be used in generics, so now you use the boxed type `Integer` which needs to be checked on each use, which depending on the usage is a lot of work.
If Java had proper generics without this workaround, we wouldn't have nearly as many issues.
>I personally don't find the logarithmic experience theory convincing.
I think this tracks though. When you do art or other things you can explore different things. Doing the same thing for 40-60h per week is just not such a varied experience.
If I go to Zürich I get a burger for 30Fr that I can get in Southern Germany for 15€ and in Berlin for 8€. That is with roughly the same quality.
I'd say past productivity leads to network effects and investments in one area that boost local salaries and decouples them quite strongly from current productivity.
My previous company had a per-dollar extremely unproductive location in silicon valley. The people there weren't at fault. You don't magically become more productive because you live next to SF.
For Switzerland does this account for the almost double salaries or only absolute spending?
If you spend 1€ in Switzerland I imagine you get much less work output than for 1€ in Germany.
Evolutionarily the best survival strategy.
There's a certain overlap here. It's not completely orthogonal. Having worked on safety critical systems before a lot of effort is put into detecting hardware errors in the software. E.g. random bit flips, ALU hardware issues, RAM writability issues, hash check of the loaded software being ok, plausibility check with (partually) redundant sensors.
You can detect a lot of hardware/QC issues on the software level. While it's still a hardware issue, better software can sometimes at least detect it
To me the answer is quite simple for any of these. Treat repeated small infractions like bigger and bigger infractions. E.g. double the cost every iteration if it happens within a specific time frame.
Ok, you speed once? $100. Twice $200. Thrice $400. And so on. We only reset if you don’t reoffend for any speeding in 5 years. If you want to speed 20 times in 5 years, ok, go ahead. You pay $52,428,800.
Bonus points for making it start at something relative to your salary. People will stop at some point out of self-preservation.
If you don’t believe high fines work, drive from Switzerland to Germany. In Germany the Swiss have no problem speeding, because the fines are laughable. While south of the border they behave very nicely on the street.
You could extend this to other crimes. Google and Microsoft happily pay fines, since it’s cheaper than what they make from breaking anti-trust regulations. If you doubled it on each infraction they would at some time start feeling the pain.
Isn't it written in this super scaling language that everybody says scales super well?
What is the problem with it?