dahfizz

47 ms·

601.
by dahfizz 4y ago
I don't know of any technical reason why #2 is hard. Its just a matter of getting the power company to do it and setting up incentives so that EV owners will use it.
602.
by dahfizz 4y ago
Clinical trials gets a drug approved for use. It proves that the drug meets certain safety requirements. Just because a drug is approved doesn't mean you should take it indiscriminately. It is "safe" to drink NyQuil every nig
603.
by dahfizz 4y ago
> At the moment, there is no clear evidence to support giving a second booster dose to people below 60 years of age who are not at higher risk of severe disease.[1] The booster is an approved and safe procedure, but it confers no benefit
604.
by dahfizz 4y ago
However, "don't recommend" is very different from "mandate", which is what is happening in the US. If this was literally any other medical procedure, the "trust the experts" crowd would be protesting the U
605.
by dahfizz 4y ago
> you have to massage your code enough that you are ~95% away from just running it on the GPU anyway Depends on your usecase, I guess. Having AVX-512 on the CPU allows you to just re-implement one critical function to be faster, and let
606.
by dahfizz 4y ago
Another weird property about C arrays is that &arr == arr. The reference of an array is the pointer to the first element, which is what `arr` itself decays to. If arr was a pointer, &arr != arr.
607.
by dahfizz 4y ago
You can also put function pointers in a struct, which is sometimes useful. The syntax is ugly, but you can do a lot of OO stuff that way too.
608.
by dahfizz 4y ago
> The sizes of arrays are not known in any useful way to C. When I declare a variable of type int[5] in a function, I don’t get a value of type int[5]; I get an int* value which has 5 ints allocated at it. Since this is just a pointer, t
609.
by dahfizz 4y ago
Yeah malloc is user space code, but it will do a syscall like sbrk to actually get memory from the kernel. The default malloc in glibc does not pad the values given to sbrk, so you have to do a syscall for every 4k chunk of memory (the page
610.
by dahfizz 4y ago
> Probably some smart SIMD lowercase function could help here but I don't think any language is going to offer that out of the box. No, but at least you have direct access to the intrinsics in C. To get vectorization in Go, you have
611.
by dahfizz 4y ago
I mean, Go is closer to C than Python is. But Go is still a garbage collected language with a runtime. It's not going to come close to the limits of performance that C offers
612.
by dahfizz 4y ago
Not really, no. Allocation involves reading/writing to memory, but that's not why it's slow. It's slow because allocation involves a context switch into the kernel. And an allocation algorithm itself isn't trivial.
613.
by dahfizz 4y ago
This is the only thing they have done in the past ~8 years, right? It's definitely a different business model than big studios. I do appreciate the depth of care this game has gotten, but it doesn't come for free.
614.
by dahfizz 4y ago
The API is massive. Just the number build parameters and boot parameters is very high. There is also a ton of things you can tune at runtime in /sys/proc . Not to mention all the syscalls and the subtle ways they all interact with
615.
by dahfizz 4y ago
They are an EV company that sells more EVs than everyone else combined. How is that not success?
616.
by dahfizz 4y ago
That's not true at all. Tesla's have objectively better hardware than any other available EV in terms of performance, efficiency, and range.
617.
by dahfizz 4y ago
The web was a much better place 10 years ago.
618.
by dahfizz 4y ago
> then reverting to bows and arrows ... would bring us less extensive conflicts. Most of the article is dubious, but this is flat out wrong. The Mongols, with just their bows and arrows, killed tens of millions of Chinese, Middle Eastern
619.
by dahfizz 4y ago
Yes, you definitely have to brew your coffee correctly. Honestly, I've found regular cheap coffee makers are acceptably good and consistent. They are designed to drip water that is the right temp. Where you have to be careful is when b
620.
by dahfizz 4y ago
Not really. The articles point is that even a v4 UUID (the random one) doesn't have enough randomness as other options, and it has a much less compact representation. UUIDs are not designed to be secrets, so they are a poor choice. The
621.
by dahfizz 4y ago
I got gifted a coffee subscription recently, and I was actually surprised how different each coffee was. I think almost anyone could tell the difference between different coffees side by side. I just don't think people are super focuse
622.
by dahfizz 4y ago
Buy from a smaller local farm. The meat is higher quality anyway
623.
by dahfizz 4y ago
Sure, but bumping the minimum version of a compiler is a way different thing than taking in a new version of a language. Rust will involve a lot of the later, which is bad for the kernel IMO.
624.
by dahfizz 4y ago
The kernel absolutely does not do this "every few years". Linux was written from day 1 in "ANSI C", which is C89 (Edit - it was actually C89 with GNU extensions. Thanks for the corrections). Only now, after 30 years of d
625.
by dahfizz 4y ago
I feel like you agree with me. All these things that the kernel needs from rust will slowly be stabilized over the next few years. The features will land in future editions of rust. Upgrading to those new editions will involve breaking chan
626.
by dahfizz 4y ago
Yes; you are pedantically correct, and missing the point entirely.
627.
by dahfizz 4y ago
Maybe I should have been more specific. Yes, you can stay on an old edition forever and not experience any of the breaking changes. But there are features that the kernel needs that rust does not support yet, such as a fallible allocation A
628.
by dahfizz 4y ago
This is absurd, frankly. "The US government collects taxes on US citizens, why not let China collect taxes on US citizens? Its the same." "The US government throws US citizens in jail, why not let Chine throw US citizens in j
629.
by dahfizz 4y ago
I am excited for the future of rust, but I am worried about where the language is today. It is simply a young, unstable language. There are lots of features you need the nightly compiler for, and there are large breaking changes with every
630.
by dahfizz 4y ago
Yeah, that's what makes me so concerned! By the time the EU actually got around to making the laws they intended, the USB standards had completely evolved. This process has taken well over a decade. It wasn't so bad last time arou

More ›