I doubt it, c-suite will never approve the spike capital expenditure for buying hardware now they're under a nice smooth subscription curve which doesn't harm their profits as dramatically.
Gift cards are their golden goose so they don't want to undermine confidence in them. They deliver the most profitable use of floor space per square metre in a supermarket.
Australia has a population less than Texas where one supermarket chain, HEB, dominates. Coles & Woolies split a market smaller than one state in the US.
> That's not really a memory safety bug, due to the fact that it panics rather than doing something unsafe.
The ? operator can be nicer to read then all those .unwraps() as an alternative and doesn't panic.
I guess the concern with panics is you're not forced to think about how you want to handle them like you do when you get a `Result` or `Option` returned.
As a result it could be used as a DDOS against your app if it's network accessible.
Rust does VERY limited breaking changes, the largest one probably being the `!` type inference change that was very carefully vetted, deemed a necessity and saw contributions to fix the issue in all crates in the official registry
They do break backwards compatibility at edition boundaries, but if they do that too much without a good enough reason they could end up with a python2->python3 situation, with low uptake.
Applying the ? operator to an Option<_> doesn't work inside a function returning io::Result<_>, for example, and turning the None from an out-of-bounds vector access into some io::Result::Err usually wouldn't make sense.
I would go so far as to say that an out-of-bounds index is always a logic error (to be handled by panicking), not an input error (to be handled with Result). And if the out-of-bounds access was caused by invalid input, then logic error consists of not checking the input before indexing.
The former issue arises from post-hoc thinking. Of course it's hard to retrofit into the language, but I see no reason why there shouldn't be facilities for the ? operator to turn a None into an appropriate error type.
The latter is a subjective matter. There are reasons to never want a panic (hello there, Linux kernel) and reasons to do more sophisticated stuff (core dump, cleanup or notifications) before crashing. And maybe one thread shouldn't lead to process death. I think most of these decisions should be kept to the user's discretion.
>Learn all about and generate SPF, DKIM, and DMARC records but still regularly get sent to the spam folder or IP blacklists if your recipient has a big-provider email?
This is my biggest complaint when self hosting. You do everything right and they still send your mail to junk or just silently discard it while telling you 250-Ok for "reasons".
Although I recently had a legit Microsoft email also end up in the junk folder so I feel better that they can't even get it right themselves.
Microsoft have also recently kicked out self hosters from their "Smart Network Data Services" portal by only allowing the ASN owner (ie. your cloud provider) to access it.
I've had Samsung order confirmations land in Gmail's spam folder. I don't understand how purchase-related emails from the largest seller of Android aren't globally whitelisted by Gmail.
I wouldn't even trust this is the high level of their pricing with the way they just casually doubled Gemini Omni pricing in 1.2 while trying to spin that it was somehow "cheaper"
It's frustrating they can't be transparent that they're even doing it, let alone why they're doing it.
They still charge you full price and don't offer any quota resets even though you're getting less value for money while you're working with a nerfed model.
You also have full control of downtime and recovery rather the refreshing the MSFT status page.
reply