That goes all the way back to at least to Stein's Paradox in 1955, sadly too few people get educated about Statistics and keep thinking specialized models will necessarily be better. If you want to estimate the batting averages of 3 MLB baseball players from samples, you are better off building a model to predict all of their batting averages than computing the mean from a sample of each one separately.
Reduces the list to another list three times as long.
It's a reduction in the sense of a transformation (also often seen in complexity theory), not in the "this makes this smaller" everyday usage that I think about first.
I wonder if someone just got super annoyed at having to ask legal to share their documentation with a cooperation partner for export control clearance, that they decided getting it open sourced would be less of a hassle.
This is 100% a valid workflow in DoD/ITAR fields. Suffer once through review, benefit eternally. It's especially important to get one good reviewed spec / presentation out, then all later reviews can be staged w.r.t. that one and are much easier to baseline and pass.
That'll be $1000 consulting fee on ITAR compliance.
The lower is your state of charge, the more you are willing to reach the destination with your remanining capacity :) The time spend riding slower is usually not so different than when you drive normally, and it reduces the inconvenience of looking for a charger almost at the goal.
I mean I never drove Wolfsburg -> Poznań -> Vienna, and I would probably get a bit better milage if I drove an average of 70. However, even when my usage gets close to that, I still don't get down to the optimistic 17kWh/100km i put down.
> ordinary cars can get to 13kWh/100km
Unfortunately I don't have such a car. :)
> which ain't that far from 7.5 you mention
I'd say that needing a 30kWh battery for 400km range vs 52kWh is a significant difference, but that'd be opinionated hair-splitting. 13 is much better and much closer to 7.5 than what my car can do.
I wonder what counts as a complex theme? Surely that is a euphemism for something, but I can't figure out what it would be and certainly don't trust TikTok to do a good job of deciding what is too complex for the youth's minds.
Whenever I see a list like this, I wonder to myself: "Who gets to decide the list?" Why are we letting companies just decide on their own what's appropriate for "minors?"
You could have, at least back when Trust and Safety roles weren't getting crushed by the AI stick.
Theres tons of research which can be brought to bear, genuine problems and challenges that require deep, thoughtful work, and some of the greatest people you will work with.
It is also absolute madness. There are so many insane, broken things about how safety is provided in the world, that you will feel like you are in a Elizabethan slaughter house, just at species scale. This is all excluding the world of child safety. Adding that to the mix gets you to existential nihilism quite rapidly.
> Prior to this change most Rust developers would never have cause to ever use `!` for any reason.
As a type.
"!" is in the most basic example nearly every rust developer has seen:
println!("Hello, World!");
Unless you specifically watched a presentation or read a blog post about the never type, you probably haven't seen it as a type.
If the average (and nearly all new) rust developers encounters "fn bla(blub: i64) -> !" I suspect they will mostly go "huh??" (or wonder what kind of weird macro that is) until it becomes common to encounter early and gets it's own early entry in the rust book.
Compared to reading "fn blub(bla: &str) -> Never", which seems rather straight forward imo. However, "Never" might be the name of some actual Struct or Enum in various codebases.
Until yesterday I used openrouter mostly as a portal to the big providers: google, anthropic, openai, without having to maintain keys and accounts and credits for all of them separately.
Yesterday I wanted to do a bit of benchmarking a prompt across multiple models. Small requests. Outside the big providers, the experience became awful. This explains that experience.
Seems like a very popular use for AI, I work on a version for Korean. (A very diffrent feature set, more exercise generation, maybe someday I'll get to live conversation, which would be a great thing.)
However, for voicing sentences I use murf.ai, which seemed very nice for korean.
I tried to talk to the openai version in (my bad) korean, and it responded in japanese :D
reply