everfrustrated
everfrustrated on Hacker News
Apache 2.0... so someone can take your code and turn it into saas again!
It's fairly well known that Bunny don't own the servers in their cdn pops so they will always be subject to the security of the people they lease etc from. If you wanted good security you gotta pay for it. Bunny are very much at the budget end of the market segment - servers cost money no way around it.
TL;DR you get what you pay for.
Oddly the industry mostly rejected googles application of SRE even as they adopted the term. I've only seen Google use it to refer to engineers maintaining / operating someone elses code.
Real DevOps is actually just Dev - in that the Devs are doing the Ops. The people called DevOps are just there to backstop the devs oncall when shit hits fan and you need someone more experienced in ops / incident management to escalate to.
There's a reason companies tend to prefer to acquire over in-house. This is part of the calculus.
They cut a key for their lock, but instead of using the 4-5 tumblers they only used 1.
While charging you can do other things - use phone, have coffee etc. Much more usable time than pumping gas.
Especially so for semi trucks too.
The French have always had a very strong submarine fleet with nuclear launch capability. Nothing new about this in the slightest. This puts them in a very select group and is what still gives them some clout on the international stage.
So stop at a supercharger once or twice a week on your way wherever. Im sure there's time in your week where you are mindlessly scrolling. Do that while charging instead of at home.
It just means the author fired an email in the second before they pressed "publish" on the article.
According to Grok thats 7-10 MW. Tiny numbers.
To put that into context, the last wave of capacity SpaceXAI added 400-450 MW.
"effective immediately" means either... he doesn't have a contract with a notice period, or he does and is willing to forfeit any benefit from it like share options, etc.
One reason might be the share price has collapsed and he has no confidence in it coming back (pretty scandalous if he's the CEO!), or Meta has offered him inducements > what he's walking away from.
Good way to burn a lot of bridges. He's never going to be hired as CEO by anybody for the rest of his career.
S3 has never been advertised as a DR strategy
>Running a highly available, durable storage system is not particularly difficult
Only someone who had never done this would say this.
This. Modern HDD should be thought of as a hybrid tape type concept. They take over 24 hours to fully write now.
Agile is dead. It presumed writing the code was the slowest part of the cycle. Now it makes more sense to only start writing code when the requirements are known as the code is quick and low cost to change if/when the requirements change later.
I think 4.6 got an xhigh after launch. The benchmarks seem to all have been against 4.6 high.
That is comparing Grok 4.6 high to Grok 4.7 xhigh tho.
I find I can just about get by with coding every day on a Cursor $60/mth sub with Grok fast mode disabled.
Doing pretty heavy coding work/requirements etc, but not much sub agents and no loops.
For me and what I’m doing that’s insanely good value.
I find grok build chews through my SuperGrok sub very quick - but I think that is due to it having the 500k context window which uses more credits. Cursor limits it to 256K (tho I see in today’s update for Grok 4.7 there’s now a toggle for context size).
Azure and GCP definitions of AZ allow a single datacenter to have multiple AZs. AWS has by far the strictest definition.
As far as I'm aware Backblaze stores data only within a single datacenter (for a given region). This likely made sense in their original business model of being "offsite" copy of data.
But it very much breaks down for B2 where they're now storing original data. I hope they rethink this model. You do get what you pay for. There's a reason they're cheap.
Depends on the rules of the company. Just because he can elect the board doesn't mean he gets to direct their every decision. They are supposed to have their own independent judgement.
Depending on the company rules it is possible they might not be easily replaced during their term in which case they could do a coup in the short term.
Atlassian is too large. Also atlassian has been doing the same growing by acquisition for a long while themselves.
Problem was tailwind had a very weak component library. I'd have been happy to pay for a more expansive set of components.
Last I looked you can't even use Akamai without signing a sales agreement ahead of using them.
>Update - primary failover briefly improved performance but did not fully mitigate, we've throttled inbound traffic and are investigating upstream Vitess issues
And now they're blaming their upstream vendor! Embarrassing stuff to be writing on a public page.
That is a different and later product with a confusingly similar name.
> We've identified an issue with a database primary and are failing over to a replica immediately
This is why it's hard to take GitHub seriously. How can a single database cause an outage for everyone? This is amateur stuff. Have they no sharding or partitioning internally? Paying customers should not be impacted in the same way as free ones are.