this post was submitted on 04 Jan 2025
352 points (97.1% liked)
Technology
60572 readers
3663 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
So Bioshock….
Well, it's just scientists, so Sealab 2021.
Eventually, the techbros will make a cheaper version and add the pod to the end though.
as long as they don’t use a logitech controller i’m sure it’ll be fine
The logitech controller was fine, although it was questionable to be using a bluetooth one.
The F710 isn't Bluetooth; it uses its own dongle.
Still.
I now wonder if part of the reason that all happened is because the controller battery died, so they couldn't ascend.
Nah, the shell cracked, pretty much instant death. Dodgy tech works until it doesn't, only the first critical failure matters
Well duh? I've read the reports. I mean that maybe they went too deep because the controller died. Eg, dude holds button that tells controllers to go deeper. Controller dies... Sub just takes last input and keeps going deeper until it hits the catastrophic depth.
Guy was an idiot for sure, I just wonder if the controller played ANY role at all.
The plan was to go to the Titanic, which is on the bottom of the sea. Controller malfunction or not, the hull was the issue.
It seems unlikely... The vessel wasn't up to the challenge of anywhere near that depth, and they intended to go that deep from the get go.
I mean, it could be, but Bluetooth shouldn't work like that - it's a digital signal with a bunch of failure modes in the spec. You'd have to code it particularly stupidly to have that kind of problem - it's a very time-synched protocol, even a sudden disconnect with no disconnect signal is something a coder would have to confront explicitly if they were using off the shelf components
I'm not one to bet against bad code, but the decompression seemed to be pretty much instant and within the planned trip, it just seems like it doesn't survive oscams razor
Pod 6? I hate Pod 6!
Total suck pod.
Would you kindly...