1,125 karma · joined April 15, 2018
Also I think in earlier days the argument to build was so you can optimize the application for the specific capabilities of your system like the supported SIMD instruction set or similar. I think nowadays that is much less of a factor. Instead it would probably be better to do things like that on a package or distribution level (i.e. have one binary distribution package prebuilt by the distribution for different CPU capabilities).
Those are generally solved using SSL, no need for centralized storage.
I don't know what you mean. My current laptop (Lenovo L13) has a cellular modem that I don't need. And I am certainly a cost conscious buyer. It's also not the first time that this happened as well.
Don't leave me hanging! How to do it?
I think evolutionary speaking, it is neither that humans are by nature strictly monogamous nor polyamorous. I think what people are confused about is that evolution often benefits from conflicts of interest between individuals. It also can both benefit from societal norms and from deviations from them. It can benefit from honesty and from deception. It can benefit from people doing their best to figure out and live by what their personal nature is and by people trying to overcome their nature to become something they think is better than that.
Yes, it is not "local" as I will have to use the internet when not at home. But it will also not drain the battery very quickly when using it, which I suspect would happen to a Macbook Pro running such models. Also 70B models are out of reach of my setup, but I think they are painfully slow on Mac hardware.
If browsers had the functionality to only preserve cookies that are needed to stay logged in across sessions, that would be quite powerful. That is all the cookies I need.
Even if you start coercing people to have kids: that will be much harder than enforcing the one-child policy. And it will have a slow effect either way, because it is starting from such a low base.
1. char 8 bit
2. short 16 bit
3. int 32 bit
4. long long 64 bit
5. arithmetic is 2s complement
6. IEEE floating point (float is 32, double is 64 bit)
Along with other stuff like little endian, etc.
Some people just mistakenly think they can't rely on such stuff, because it isn't in the standard. But they forget that having an ISO standard comes on top of what most other languages have, which rely solely on the documentation.