Two things can be true. The data centers can be driving up electricity costs, causing pollution, planning issues, and computer hardware shortages _and_ people can be finding the tools useful.
My assumption would be, when there is a large corpus of crash reports for a certain configuration of hardware, knowing if it's a hardware failure, driver bug, or software incompatibly, is pretty hard. So it's probably easier to catch false positives and not get blamed for a faulty product, even if you aren't the cause. Drivers crash under the hood in windows all the time, even today, but once MS did a better job of just restarting the offending drivers where possible instead of BSODing, people thought windows was an unstable product. Which is technically true from the users perspective, even though it wasn't Microsoft's fault directly. You may have had a good combo that simply shouldn't have been on the list/was later patched/or your system is more stable that the average persons.
Somewhere between ~15-75+ billion USD. Higher end if you want to include the hardware R&D/etc, which is arguably core to their metaverse concept. I love the idea that they don't even have a product _called_ metaverse. Most of the VR content developer acquisitions costs by Occulus Labs are undisclosed.
When I spec'd a M1 air for my partner back in the day, even though she didn't really need it, I made sure to get the 16gb model for the longevity. Devices shouldn't be disposable toys. Apparently I had better foresight than expected...
Low cost carrier. Think Ryanair. Competition from the rest of the market and bad management put them in a bad position, with the most recent war causing unsustainable fuel issues.
Other airlines may be able to double/triple their prices in the short term. Spirit's customers may simply choose to not fly.
I honestly want to follow you around for a day. I am reserved with how I engage with technology. It needs to be making my life better, not extracting value from me. Tech for tech alone is no longer exciting to me as it once was.
The scenarios I have taken extended downtime for. When an OLTP's DB needed a serious overhaul for some reason and it was cheaper for rollout to plan operational downtime than risk loosing data or inconsistent transactions. Generational platform migration to complete system rewrites (something I am generally against, but that is its own soapbox). Migrating from on-prem to cloud infra, which required design changes. In all cases data integrity/consistency is the critical aspect. Migrating from one db technology to another (MySQL -> PostgreSQL).
In all those cases there is serious planning done before the migration, checklists, trial runs/validations, and validation procedures day off. If something isn't working, the leadership group evaluates the the issue and determines rollback vs go forward. Rollback needs to also be planned for, and your planned downtime window should be considered.
I agree with you, this wording implies they are making changes after this change. This could've been bad planning, a bad call day off, etc.
In one scenario, we _had_ to go forward while resolving several blockers on the fly. We had planned ahead of time developer rotation shifts. Pulling people off the line after 8-12hrs. At some point, you aren't thinking clearly understress. Don't know how big the team is over there is, but I hope they are pacing themselves, during what I am sure is a horrible moment of crisis to them.
My advice to them is, consider a roll back if needed/possible. Split responsibility between who is managing the process and dealing with specific problems. Focus on MVP. Don't try to _fix_ and replace at the same time, if something was broken before business wise, log it in your bug tracker and deal with it later. Pull people away if needed to get rest. Get upper management away from people doing the work, have them only talking to the group handling the process management.
Edit: I am also making a good faith assumption that this is planned and not an emergency response, either way, it doesn't change my general advice.
Thank you for the reality check. I like to assume people are coming from a certain baseline on HN, but I sometimes forget that certain topics have a passionate user base represented.
Personally switched from VZW to Google Fi. It's on TMOs network. As you can imagine, when engaging with Google's support was hilarious when there was something I needed, but overall I don't miss Verizon and pay drastically less.