I did that with the deck I received last October because the battery was broken and wouldn’t perform under load. I’ve always treated my systems mobile and desktop as simply computers I can tinker with so personally I’m not bothered with using a different than stock os.
Comment on Stuck on Verifying Installation after most recent Beta update...basically bricked my deck
TheDarkKnight@lemmy.world 11 months agoMore likely to RMA than go that route. Valve should’ve QA’d their updates so should cost em some money if they’re gonna push untested stuff to prod. If you gotta wipe and start over, best to do it with a fresh deck.
wonderfulvoltaire@lemmy.world 11 months ago
TheDarkKnight@lemmy.world 11 months ago
Yeah I don’t mind tinkering, work in dev so get extra annoyed when things like this happen in production, no way soft bricking should even be in the realm of acceptable possibilities for an update. Shit happens though I guess 🤷
habanhero@lemmy.ca 11 months ago
Question for you since you work in dev. How annoyed do you get when users confuse beta with prod?
TheDarkKnight@lemmy.world 11 months ago
Do you think a beta update channel for a consumer device should not be treated with the same care as prod, do you think it is in a hardware manufacturer best interest to even allow the possibility of a mass RMA event with an untested update? And seeing as how this ALSO affected the main production release as well, it seems as though yes their SDET practices aren’t the best and probably should be revamped. This also isn’t the first time this has happened.
Beta is not for experimentation for a hardware company and no business is going to pushing a public beta channel with a bricking update on released hardware.
But yeah, talk to me about your opinion of beta and we can see if my entire career’s experience at fortune 100 company in software engineering can be invalidated simply because har har beta doesn’t mean prod trust me bro.
stefenauris@pawb.social 11 months ago
…beta is not prod lol