Aruba Networks (acquired by HP in 2015, right before HP split into HP/HPE) has approximately 5% of the market for switching outside of the datacenter segment. They aren't a big player in the DC, you're right about that.
Google used to use HP (pre Aruba) switches in the DC in the early days. Not many though. Mostly for OOB access. I doubt they still do.
> Google's non-AI efficiency is not much better than Amazon or anyone else.
I don't think this is true. Google has long been a leader in efficiency. Look at the power usage effectiveness (PUE). A decade ago Google announced average PUEs around 1.12 while the industry average was closer to 2.0. From what I can tell they reported a 1.1 average fleet wide last year. They've been more transparent about this than any of the other big players.
AWS is opaque by comparison, but they report 1.2 on average. So they're close now, but that's after a decade of trying to catch up to Google.
To suggest the rest of the industry is on the same level is not at all accurate.
I'm using Kagi as my default, falling back to Google (typically via '!g' in Kagi) for some technical queries. I use ChatGPT 4o several times a day, but typically not as a 1:1 replacement for web search.
My guess after reading the same -- the bot traffic comes in bursts and targets a specific commit hash for a while. Users are unlikely to need that specific commit, and even less likely to need it at the same time a bot is bursting requests for it. There's probably a small risk of denying a real user, but there's a large reduction in traffic from the bots making it to git; a worthwhile trade.
Parent didn't say anything about complete protection? An LLC does offer some level of protection, albeit mostly liability protection (as implied by the name, Limited Liability Company), and in this case I would be more worried about the need to defend against overzealous law enforcement requests. I'm not sure an LLC really helps much in that context. It's more about being able to afford a good legal team.
For what they're referring to, there is no personal protection. You can be personally liable for neglecting to protect against illegal sexual content even through an LLC.
This is what keeps most people from hosting user content. It's very easy to do, but it opens you to massive personal liabilities.
Holy shit though, who thought this email (or Slack message or whatever) in the middle of an ongoing disaster was a good idea? This is the equivalent of asking you to make sure you file your TPS report. Honestly why do they give a shit about the knobs in the RTO portal? They can see if people are based in LA already. Benefit of the doubt, etc.
There's a separate announcement showing some support and asking everyone in LA to WFH, which isn't mentioned in the article
Also not updating the RTO portal won't cause any penalty from what I've heard, and ppl can update the WFH status anytime, e.g. marking their whole month as natural disaster WFH in advance if they really care, which no one really does
You don't. But they want to minimize avenues to get sued because people can and probably will file an wrongful termination lawsuit.
I don't know the exact laws, but given California I would not be surprised if there's a "no, you cannot fire someone who's in the hospital over a state of emergency" clause. Similar to how you can't fire an employee to avoid workman's comp.
Yes, I know, and in fact I checked before posting.
I was using “I think” as a conversational affordance to give OP a less confrontational way in to disagreeing with me, if even in an at-will state, termination for cause is better for the employer for some reason (I couldn’t find one when searching, but it’s not an area I am knowledge about).
Google used to use HP (pre Aruba) switches in the DC in the early days. Not many though. Mostly for OOB access. I doubt they still do.