2 ms·
I'm not convinced this policy is wise or helpful. In the past couple of years, we've had major upgrades pushed out to three types of mobile device here. Moving
by Silhouette 13y ago
I'm not convinced this policy is wise or helpful.
In the past couple of years, we've had major upgrades pushed out to three types of mobile device here. Moving to iOS6 infamously broke things like maps. The Android update from Samsung lost numerous settings and required more than an hour just to reconfigure things back to roughly how they were, in exchange for exactly no useful change in functionality for us. And the Windows Phone one... Well, I can't tell you what it did, because it was pushed within a day of connecting the new phone to the network, completely bricked the device, and resulted in the whole thing going back and being replaced by something completely different.
Move fast and break things rarely seems to work out well for users in practice, but it's a particularly dumb idea for the core functionality of a critical piece of equipment. Modern mobile devices are very much in that category for the individuals using them.
As an added potential issue here, there is a question of how much integration with/control of the underlying transmit/receive functions the Firefox OS code would have and whether that underlying code would be affected at all by this kind of update. I would hope the answer is that the key hardware control functions are completely isolated, but if the design is poorly engineered then you also have a real risk of a bad mass update literally bringing down a national network for everyone. When these devices are how people call 911 or the local equivalent, that is obviously not a good idea.
- synchronise 13y agoFrom what Mozilla mentioned before, it'll just be userspace updates that'll follow this rapid release cycle. The underlying OS will only receive updates every major point i.e. the next one will be 2.0
- medde 13y agoHow long have you been using Firefox OS? Also, which major software company doesn't upgrade often?
- Silhouette 13y agoAlso, which major software company doesn't upgrade often? If you're talking about core infrastructure (operating systems, servers, etc.) used by serious businesses then the answer is pretty much all of them are much slower-paced. Look at how often Microsoft releases a service pack or new version of Windows, or Debian changes stable, or Postgres bumps the minor version. These things happen every year or two, not every month or two. Even Android, to the extent that it has any meaningful version numbering or naming at all, only tends to push out a major release or two per year, and in practice people's mobile devices don't get updated that often by their networks and many phones never get a major update within their normal lifetime. Of course many developers issue point releases with security patches and important bug fixes more frequently, but changing functionality every few weeks in infrastructure software just seems crazy to me. It doesn't work well in Firefox-the-browser, so why would we expect it to work any better in Firefox-the-operating-system?