dklsafhjskljfl
Joined 7 years ago
Joined 7 years ago
Not against a limited lifespan, but I really do like the model of a bridge device that communicates over wire or bluetooth, especially for consumer IOT - bt-based standards prevent vendor lock-in, for example.
Facebook got busted using that (security) info for marketing purposes, and the reaction was muted; but, within the security community, it was loud and angry. Within a week, they had ceased completely.
If I smoked weed, it'd be heaven.
"but you didnt"
"but you didnt"
GCP has much more modern APIs (they got to do "right" the first time around, while AWS had to learn from their "mistakes")
GCP is less mature with documentation, but still excellent (AWS is first class). I've found bugs, and others I know have run into straight up wrong docs - a quick message to support yielded the correct information and docs update within the week.
GCP is far more "opinionated" about how you should run a service. AWS is opinionated as well, but less so. What this means is that while GCP will sell you resources in traditional way, to go GCP native or from scratch really requires buying into the GCP "way" of doing things more than AWS does. Basically, K8S or go home.
We use GCP and I enjoy it quite a bit. I have extensive AWS experience as well, but no strong preference.
So, you're saying that the phone you bought you didn't use as a phone? Hmmm....
Also, this isn't a fake account. I don't think anything I've posted was intended to troll.
Anyways, I looked it up - they were also carrier locked to walmart mobile, a mvno in which the price of the phone is subsidized.
You can find small phones but they have terrible cameras, sub HD resolutions, and bargain basement SOCs.
Is the demand for a premium (or even mid range) small phone really that low?
Some games were worse, far worse. Doom used a list of 256 random numbers that it looped through.
Pokemon is another game where the RNG function is extensively mapped, and even used in combination with bugs to generate Mew events, something that should never ever happen.
You see a lot of TAS of old games, especially popular ones, that abuse the RNG generator where feasible.
In fact, it may be easier for developers to write code that runs faster with rust than C++, thanks to much error and exception handling code that you simply do not need in Rust.
Most importantly, however, is finding Rust developers who are experienced enough to write high-performance Rust. I would imagine that it's a lot easier to find C++ devs.