That's still ridiculously slow.
I'd expect them to have hundreds of Microservices. Each one of those should be able to handle a random restart at any point in time so they should absolutely be able to restart 100s of servers concurrently without major disruptions.
Hell on Facebook scale a whole-Datacenter going down should not cause service disruptions.
It's absolutely fantastic. I feel disabled coding without it in my spare time. Imagine a pair programming session with someone that can read your mind and knows the entire codebase. I don't know how much I'm allowed to talk about so I'll leave it at that.
I don't have access to copilot so I can't compare but I'd wager it works a lot better for Google internally because the training data is customized to Google.
Interesting, I didn't find it that impressive when I tried it a couple months ago and fairly quickly went back to regular old-fashioned autocomplete. What language(s) were you working with out of curiosity?
I'm at Google and am not entirely sure what you are referring to, but I'd love to try it. Could you provide an internal codename I could search for? Or is it integrated somewhere in Cider (the name is public knowledge so I'm not leaking anything by using this) that you could guide me to (i.e. X dropdown -> 3rd option) while preserving ambiguity?
I’m fascinated that of two people working at the same company, one raves about how an internal tool is a complete game changer and indispensable while another isn’t even aware it exists.
I'm fascinated that at a 175k employee company, two employees I know nothing about, in business areas or positions I know nothing about, could possibly use different tooling for their day to day duties.
*Surely* at your place of work, the cleaning staff is familiar with the CTO's dearest tools and vice versa?
That’s an unnecessarily snarky answer given the two people above are clearly both in similar roles. The parent comment was asking where to find the option in the tooling they both shared.
Snarky replies comparing CTO to cleaning staff don’t even begin to apply.
It's a conversation that isn't relevant to anyone outside the company. One commenter, who may or may not work in Google, is asking for an internal codename.
You're the downvoter here so why does my comment bother _you_ so much?
I had the exact same reaction. Saw the massive list of new features and decided to wait for .1 or .2 releases to shake out the bugs. Seems like patience is paying off as always.
Having commuted 55 minutes each way into Munich for more than a year, I'd say my average daily delay is about 15 minutes with >30 minutes delay happening at least once a week.
That's a level of regular delay that makes early morning meetings impractical because I'll be late more likely than not.
anecdotal, but my experience a year ago when i travelled international was: 2/2 delays by OEBB that made me miss connections (and absolutely rude and inconsiderate customer service reps in Vienna HBF on top of that), 1/1 on time trains by DB ICE
This is not saying anything about being open. This is talking about federation and stable protocols.
Both absolutly do hamper fast evolution of a product because they require a LOT of coordination and consensus, both of which are incredibly expensive and time consuming.
With a non-federated and unstable protocol, they are free to update and deprecated whatever they like and on a fast timescale. That is impossible with a federated stable protocol.
This has nothing to do with FOSS.
XMPP is a good example of a protocol that got fragmented to death by many many different and incompatible extensions, ultimately making it too fragmented and too slow to adopt to new requirements.
That's not actually true. The conditions for the formation of coal and oil may likely never happen again because the bacteria to break decompose trees did not exist then but exist now, making oil formation impossible because trees decompose now. Unless they all die out, we won't get any new oil ever.
I'm curious about this. We certainly won't get any more coal, but a whole lot of carbon gets subducted into the mantle regularly. Some gets turned into diamonds. Some gets blown out of volcanoes. Is the oil we pump out of the ground produced directly in the continental crust or is it generated from some of this carbon subducted with oceanic crust that has been transformed by some process and then made its way back into continental crust?
I'm lazy, so I'm hoping some geologist will stop by and educate me.
In order to predict how bad the long tail will be though we should ideally look at the graphs broken down by network type. Does the increase just represent a switch from people using their residential ISP connection for everything to people using their cell connection more, or does it actually reflect residential connections moving from v4 to v6?
The only way to break the long tail is regulation or forced updates. If you're at 95% rollout, it's fairly likely the last 5% of holdouts won't do it willingly, so they need the stick.
I would definitely support regulation here, especially regulation forcing ISPs to provide v6. That would at least take care of one large part of the problem.
Been using hetzner storage boxes for borg backup for >5 years. Works without issue for multiple TB of backups.
Every maintenance downtime so far has been announced in advance.
The main reason I’ve avoided Hetzner storage box is because they don’t accept loading money into the account as a prepaid credit for a longer period. It’s always a month-by-month payment. Ok, so they do allow it, but only through a bank transfer, which is either not easy or possible for those outside the EU. If they allowed this through credit/debit cards or PayPal or some other mechanism, I’d surely try it. Hetzner in general seems to be very conservative in handling (and avoiding) risks.
I’d like to prepay for a year or longer for critical services so that in case something goes wrong (card expired, didn’t notice reminder emails, temporarily off the grid, temporarily incapacitated), things just don’t go poof.
