Come up with great interface for web apps in WASM and the world will follow. Eventually browsers can just implement your interface directly without the javascript glue.
> So at FP16 precision that's a grand total of 16 kB you're transmitting over the PCIe bus, once per token. If you multiply by, say, 20 tokens per second, then you're still only using like 0.1% of your PCIe bandwidth.
Intra GPU memory bandwidth is very important, but I‘ve seen lots of people use just a x4 lane and they didn’t complain much.
What is the difference between a secure password synced with a password manager and a cookie that doesn't expire synced with a browser or extension? I don't see much difference so why bother even having a password?
The difference is that cookies are not even encrypted and you can get all of them by `sqlite3 .dump` on `cookies.sqlite` file, while password manager likely offers more protection, since that's the point of it. :D
Also SID are ephemeral and expire, while passwords are not supposed to be.
Session IDs may be tied by the backend to a client IP address, or some such, but likely that's not done very often, and may not be that useful.
In this case the cookie would be as permanent as a password. I was just thinking if convenience is a priority why even have a password when the cookie is just as secure.
You know why housing is so expensive? It's because building a house is so expensive. If it wasn't people would be building houses left and right in the many thousands of empty lots scattered throughout the country.
Which is particularly interesting, because the quality of the buildings themselves have taken a steep nosedive since the 1940s. Something like 98% of all new builds are complete teardown crapshacks. It makes you wonder where the money is going if the materials are dogshit and the labor is incompetent.
Yes. Suppose you ask me what the sqrt(4) is and I tell you 2. Accurate and correct, right?
Does it matter if I answer every question with either 1 or 2 and flip a coin each time to decide which?
Deterministic means that if it is accurate/correct once, it will continue to be in future runs (unless the correct answer changes; a stopped clock is deterministic).
I think the analogy breaks down here. The elided bit "time indicator" implied at the end makes that statement is false. A stopped clock is not a deterministic time indicator.
If the correct answer changes, a (correct and accurate) deterministic model either gets new input and changes the answer accordingly, or is not correct to begin with.
Determinism is unrelated to correctness. Deterministic means the output depends only on the state you consider to be relevant, and not other factors. A stopped clock is deterministic: no matter what you do, it gives you the same output. A working, accurate clock is deterministic if you consider the current time to be a relevant piece of state, but not if you don't. Consider how "deterministic builds" need to avoid timestamping their build products, because determinism in that context is assumed to mean that you can run it at a different time and get the same result.
LLMs can be deterministic if you run them with a temperature of 0 or a fixed random seed, and your kernel is built to be deterministic, but they're not typically used that way, and will produce different output for identical input.
I never said it is. That's why I qualified my example with the word correct.
> no matter what you do, it gives you the same output
This is not deterministic. This is determined. I think this is the confusion I was pointing out.
>> Deterministic means that if it is accurate/correct once, it will continue to be in future runs (unless the correct answer changes; a stopped clock is deterministic).
The bit in the parenthesis, I am trying to argue, is nonsense. If the correct answer changes, the system is not accurate or correct to begin with so the point is moot. Correcting the system will make it accurate. A stopped clock is not deterministic, it's determined. As a time indicator, a stopped clock is not a correct, accurate or deterministic model at all under any possible interpretation.
You pretty clearly think determinism and correctness are related, otherwise why wouldn't a stopped clock be deterministic?
Determinism is about the behavior of a system. Correctness is also about the purpose of a system. A system can have deterministic behavior while being completely unfit for its purpose. And depending on its purpose, it can be fit for purpose while being nondeterministic.
You still seem to see correctness as a prerequisite for determinstic. I’m open to that idea but I really don’t think it’s the case.
I build a box. It has an LCD display. It has a button labeled “what time is it”. You push the button and it always shows “10:43am”. This is a deterministic system.
reply