The problem with LLMs is that they require immense compute power.
To train. But you can run a relatively simple one like phi-3 on quite modest hardware.
The problem with LLMs is that they require immense compute power.
To train. But you can run a relatively simple one like phi-3 on quite modest hardware.
It is my understanding that this driver had not been (re) certified by Microsoft, though. So in that case, I stand by my statement.
If it had been, I'd agree with that blame.
^ Mocks people for using the default, then proceeds to not give alternatives they deem better.
Fortunately, the 2 people they are suing have been identified.
One of them actively drove their car into them, and tried to pin it on the waymo, and the other goes around slashing tires (and is claimed to have mental issues, which does make it more sucky if true).
My answer might surprise you, but no. Your source code, your binary, your responsibility. Not that of the platform, the compiler, or the company that supplies it.
I fully agree with you on that front, but ads have nothing to do with kernel access, so how is that relevant to their legal requirements?
I disagree. As someone else in this thread said: if you compile a buggy Linux driver that crashes the system, it's still the fault of the driver.
Personally, I don't see the issue. Microsoft shouldn't be responsible for when a third party creates a buggy kernel module.
And when you, as a company, decide to effectively install a low-level rootkit on all your machines in hopes that it will protect you against whatever, you accept the potential side effects. Last week, those side effects occurred.
128k token context is pretty sweet. Mistral nemo also just launched with a similar context. Good times.