4 ms·
the arguments from folks on the "architecture review boards" was that multiple connections are always bad and that developers can't be trusted. i'm willing to a
by raggi 2y ago
the arguments from folks on the "architecture review boards" was that multiple connections are always bad and that developers can't be trusted. i'm willing to accept that they did get beat up quite a bit over power at various points when at times applications were a big part of the problem. That said this is also a gross misunderstanding of the problem and overall solution space, as well as very much gatekeeping.
- blitzar 2y agoDump the entire queue to a google server (confirm receipt and shut down the connection) and then have the google server forward all the data to its destinations? Seems to me that would be the lowest power, lowest developer trust, lowest number of connections, maximum gatekeeping method.