4 ms·

So they did the same thing as Chromebooks - made it dependent on Google software.

by benatkin 4y ago

Waterluvian 4y ago
What might another solution be that isn’t inferior in terms of latency?
- benatkin 4y ago
  To support both. To not build the tech equivalent of fast fashion.
  - Waterluvian 4y ago
    That isn’t sensible from a product perspective. Engineering stuff for a peripheral “in case our company fails.”
    - benatkin 4y ago
      That's like creating clothes to only be worn a few times because you're targeting people who buy lots of clothes. A controller is an input device similar to a mouse and keyboard and ought to support standards so it can work with different devices. This "product perspective" seems to be that of IKEA and McDonald's.
    - TechBro8615 4y ago
      And yet they managed to add the feature after the product failed.
      - lolinder 4y ago
        Yes, because now they know customers actually will need it.
        sangnoir 4y ago
        All customer purchases were refunded - including the hardware. This is a goodwill gesture, and the people at Stadia have my gratitude.
        lolinder 4y ago
        Also true! My point was just that it wasn't malicious of them to not initially build a feature they didn't intend to use.
  - surajrmal 4y ago
    You are assuming there was room on the device to support both at the same time. The amount of RAM/storage to support a Bluetooth stack may seem small but it's not for tiny devices. I'm sure they devoted resources to the WiFi path that the product was designed for instead.
- deleted 4y ago
  [deleted]
PhasmaFelis 4y ago
From the other comments, it always had fully unlocked wired-USB support. And they did build Bluetooth support into the controller, and released software to enable that Bluetooth as Stadia was going under. Still seems really weird not to enable it from the beginning--what would they lose?--but the made the right decisions during design and at the very end, at least.
dmix 4y ago
The architecture makes sense if you understand how the cloud gaming system is set up though. There's no general protocol for on board contoller wifi/SOC->cloud gaming services (yet). It's inherently a proprietary design. It also didn't need a bluetooth chip but they added one anyway. It wasn't sold as a general controller so I don't really see the big deal. This is a nice good will gesture.
- IshKebab 4y ago
  Right, the direct wifi connection makes sense when using it with Stadia, but why did they not let you also use it as a standard Bluetooth controller?
  - sergers 4y ago
    Cause they were selling stadia. It didn't need to support general purpose, they were not looking to sell the controller for general use (google terrible at hardware support). People buying it knew it only worked with stadia. For stadia use, it made sense and connectivity over Bluetooth would have increased latency and complexity to the cloud service. Moot point now, but atleast they opening it up so you don't have to throw the hardware in the trash
    - bombolo 4y ago
      > Mute point now *moot
      - sergers 4y ago
        Thanks fixed, autocorrect
  - dmix 4y ago
    Having the engineers focus on doing one thing really well is good enough for me.
- duskwuff 4y ago
  > It also didn't need a bluetooth chip but they added one anyway. It uses the same IC for both functions -- BCM43458.

So they did the same thing as Chromebooks - made it dependent on Google software.

Waterluvian 4y ago

What might another solution be that isn’t inferior in terms of latency?

benatkin 4y ago
To support both. To not build the tech equivalent of fast fashion.
- Waterluvian 4y ago
  That isn’t sensible from a product perspective. Engineering stuff for a peripheral “in case our company fails.”
  - benatkin 4y ago
    That's like creating clothes to only be worn a few times because you're targeting people who buy lots of clothes. A controller is an input device similar to a mouse and keyboard and ought to support standards so it can work with different devices. This "product perspective" seems to be that of IKEA and McDonald's.
  - TechBro8615 4y ago
    And yet they managed to add the feature after the product failed.
    - lolinder 4y ago
      Yes, because now they know customers actually will need it.
      - sangnoir 4y ago
        All customer purchases were refunded - including the hardware. This is a goodwill gesture, and the people at Stadia have my gratitude.
        lolinder 4y ago
        Also true! My point was just that it wasn't malicious of them to not initially build a feature they didn't intend to use.
- surajrmal 4y ago
  You are assuming there was room on the device to support both at the same time. The amount of RAM/storage to support a Bluetooth stack may seem small but it's not for tiny devices. I'm sure they devoted resources to the WiFi path that the product was designed for instead.
deleted 4y ago
[deleted]

PhasmaFelis 4y ago

From the other comments, it always had fully unlocked wired-USB support. And they did build Bluetooth support into the controller, and released software to enable that Bluetooth as Stadia was going under. Still seems really weird not to enable it from the beginning--what would they lose?--but the made the right decisions during design and at the very end, at least.

dmix 4y ago

The architecture makes sense if you understand how the cloud gaming system is set up though. There's no general protocol for on board contoller wifi/SOC->cloud gaming services (yet). It's inherently a proprietary design. It also didn't need a bluetooth chip but they added one anyway. It wasn't sold as a general controller so I don't really see the big deal. This is a nice good will gesture.

IshKebab 4y ago
Right, the direct wifi connection makes sense when using it with Stadia, but why did they not let you also use it as a standard Bluetooth controller?
- sergers 4y ago
  Cause they were selling stadia. It didn't need to support general purpose, they were not looking to sell the controller for general use (google terrible at hardware support). People buying it knew it only worked with stadia. For stadia use, it made sense and connectivity over Bluetooth would have increased latency and complexity to the cloud service. Moot point now, but atleast they opening it up so you don't have to throw the hardware in the trash
  - bombolo 4y ago
    > Mute point now *moot
    - sergers 4y ago
      Thanks fixed, autocorrect
- dmix 4y ago
  Having the engineers focus on doing one thing really well is good enough for me.
duskwuff 4y ago
> It also didn't need a bluetooth chip but they added one anyway. It uses the same IC for both functions -- BCM43458.