They have small print after each of their emails that says that GDPR allows them to email me because they believe I might be legitimately interested in purchasing their services.
1,612 karma · joined October 15, 2013
They have small print after each of their emails that says that GDPR allows them to email me because they believe I might be legitimately interested in purchasing their services.
It also happens to align them with people who are in the business of selling or renting Macs, sure. But the point is not to screw AWS or MacStadium's competitors. The point is to sell Macs.
If you look at older/used networking gear, 40G QSFP+ might look like the next step, but to me that’s starting to look a bit like an evolutionary dead end at this point.
Low-end 25G routers/switches are relatively cheap, as are 25G SFP28 optics (including bi-directional ones, which get a bit marginal at speeds above 25G).
The traffic volumes these devices are intended for are truly mind-boggling to me (as someone currently building a small 25Gbit network with sub-$1k parts).
At this revenue run rate, a standalone Mac company would be in the Fortune 100, next to companies like Nike and Coca-Cola.
Things like the five times faster ARC retain/release cycle or the dedicated objc_msgSend branch predictor are a big deal when your software stack hits these hotspots constantly. The SPEC sample workloads won't.
Of course, you can also get these savings with an online service like Wasabi or Backblaze B2. I just feel that using S3 as your only storage is fine, but once you move to the budget options you need an external backup. So we are using Minio and backing up to Wasabi, and still saving a lot.
- WDC 65C02S @ 8 MHz
- 40-pin DIP package
So if the Starlink launches happen twice a month, the carbon footprint from the fuel would be at least an order of magnitude smaller than that of a single long haul route of an airline.
Building the satellites and the rocket (including the expendable second stage) is obviously pretty carbon intensive too, but fuel is probably what you were thinking about when posing this question.
Each Lambda invocation gets a dedicated VM for the duration of the request. It is a great match for synchronous code.
Luckily for me, vi defaulted to Enigma encryption back then…
What matters is the return on investment, and as you state, one of the great things about cost optimization is that its returns come largely risk free. By my math the optimizations described here return $100k a year. On a risk-adjusted basis, what task could this developer have performed that would have returned more?
- They mention that the initial savings of $1500/mo from omitting unnecessary headers was 12% of their egress cost (so the total before this was $12500)
- Then they got an additional 8% of savings by increasing the ALB idle connection timeout to 10 minutes (down to $10120)
- Finally they said they saved $200 per day by switching to a lighter TLS certificate chain ($6000/mo, so down to $4120)
None of those steps seem to have required any meaningful amount of development work. Let's say this took a developer one week? The return on that effort would be $100k a year, or $2500/hour for the first year alone.
Two things that have changed since then are 1) Cloudflare’s Privacy Pass browser extension and 2) their significant network expansion, both of which would be likely to affect the experience described.
One thing that has not changed, however, is how many (typically unsophisticated) web site operators actively search their logs for signs of suspicious / bot activity and then institute manual blocks in the hope of catching all of them. This is often done with very blunt instruments, such as whole-country blocks.
In contrast, people who are confident about their infrastructure can deal with the background noise of the Internet appropriately—by doing nothing.
Of course, some people will want to taste dead cows similarly to how exotic meats have an audience today. But McDonald’s would not be the venue for something like that.
I saw this document linked on Twitter yesterday and it's just amazing. I always knew that Larry Ellison's mug was in the dictionary next to the definition of "customer hostility", but man, it's another thing altogether to read the top 60 ways Oracle will screw you.
My favorite is how you can't use Oracle Technology Network (OTN DEV) licenses for testing. They're only for development, which is something you do without testing.
It would sidestep a lot of the issues around banning a specific (powerful) advertiser.
Those I'd expect to slowly but steadily creep up in billings since Cloudflare introduces new products all the time, they tend to be very easy and desirable for existing customers to adopt, and they tend to be upsells over the base enterprise plan.