Yes, I wanted to mention WASM but honestly even talking about it is doing more of a disservice to modern .NET than not given the preconceptions about Mono.
Mono as a runtime hasn't been relevant in almost a decade now (since the advent of .NET Core). "I can go into the compilers to find bugs" -> yeah, that's what Roslyn is. C# lets you control GC, marshalling, safety, calling convention, inlining, etc. for very fast hand-rolled managed or unmanaged code if you need it.
I read very fast (English and code, and my native language), and I have a very vivid visual (as well as auditory) imagination. Wonder what I traded off in this setup.
The confidence interval comment still applies for any production or client environment I've ever deployed code to.
Unless you actually expect your environment to spend more than 5% of its time on average getting suspended and resumed. Maybe you work on some tooling that is scheduled to run right around migration time (for servers) or sleep/resume time (for clients).
Why so? Zero-order effects are not unheard of in biology. Example: the elimination rate of ethyl alcohol is dose-independent because any practically noticeable concentration of ethyl alcohol will saturate available alcohol dehydrogenases.
Why are you ruling out the possibility that training on the material may confer an advantage when the data is presented, even if the advantage may not be strong enough to pass the test without the data present in the context window?
1. Your original wording, "getting a response _for_ n tokens", does not parse as "getting a response containing n tokens" to me.
2. Clearly, _you_ don't know the API, as you can get output up to the total context length of any of the GPT-4 32k models. I've received output up to 16k tokens from gpt-4-32k-0613.
3. I am currently violating my own principle of avoiding correcting stupid people on the Internet, which is a Sisyphean task. At least make the best of what I am communicating to you here.
"Insecure mode" sounds a lot better than "default mode". If I didn't know what any of the options meant, I'd feel safe using BlockCipherMode.Default, but I wouldn't feel safe using BlockCipherMode.Insecure.
You are just describing a (good) recommendation algorithm. TikTok's is infamously good at figuring out your niches and catering to your taste by looking at your minute interactions with the content it shows you. My TikTok "for you" page has absolutely 0 mainstream politics, rage bait, or any other "normie" topics. It's mostly technically fascinating stuff and good absurd humor that caters to my absurd taste.
Optimizing for engagement is not inherently bad, nor does it necessarily result in socially suboptimal outcomes. My TikTok feed is very engaging without having to resort to triggering my anger.
A recommendation algorithm that only sticks to a handful of given topics (rage bait and furry porn?) is not a very good one.
> I'm not very interested in this "right to repair" stuff - it revolves around demanding modular parts for quick and easy replacement. People who are actually close to the metal, who actually get their hands dirty are repairing those devices since ever.
It also involves demanding access to proprietary ICs and information like schematics. A component level repair might become impossible if you don't have access to a vendor-specific replacement for some burnt battery charging IC. You can't really fix up a silicon die like you can a dead pixel.