Yes, more TomTom that openstreetmap, that was clearly show by the dataquality. Much less walk and vike information. If you don't drive a car all my sampling say OSM is way better.
The "tivoisation clause" also in many cases makes it against the law to use GPLv3 software in some consumer products, or parts of the products.
For example much embedded software that comes under radio transmission laws, much software in safety critical applications such as rail, or automotive use, software that have environmental impact at leat in the automotive industry. At leat in the way that automotive legislator reads the laws at the moment.
ECU is usually an Electronic Control Unit. Some OME's name one of there ECU's, Engine Control Unit to make stuff more complex. Not app manufacturers have Engine Control Unit or a Body Control Module. The electronic architecture of a Volkwagen, GM, Volvo or Tesla is very different. Hardly any of the ECU's have the same name.
Or PCM (powertrain control module, since the transmission and engine typically work as one unit) which has been used by Ford (and Mazda) since ODB-2 was standardized in the 90s.
Not really, there always is and been some kind of separations between the phones when they send data.
Most 2G systems used TDMA, so the phones inside a cell spitted the time between them. e.g. one phone could send almost all the time but 10 phones sent 1/10:th of the time each.
3G and laster used WCDMA (as some US system used even in 2G) for the radio. Where encryption of the data over a wide frequency span makes the signals mix in the air. But at the same time lowering the needed effect to get the signal across. With WCDMA you can send on an effect below the background noise and still get the signal across.
Lowering the effect of the radio is a big goal as it drains battery to send radio signals. An effect you can see it you travels in areas with bad receptions your phone battery drains significantly quicker. The best way to lower the radio exposure is to have loots of radio towers close to people. The alarmists scaring for cell-networks have made some problems in building enough towers, and by there fear of cell-radio transmission they increase the energy transmitted by the phones in there area.
Most, almost all animals are mostly water. About 2GHz you have a frequency that resonates with water, it's gets stopped by water, including rain. E.g. it's energy goes into the water, this is how the microwave operates.
For this reason it's traditionally considers useless as radio transmission. And turned into a global free frequency span. Making this radio space used by all kinds of devices that you have at home. Wifi, Bluetooth, etc. There is tons of research of how radio and other waves effect the human body.
To handle deploys and especially rollbacks you need a working CI, or rather CD chain. Where eveything is automated. In there are dependencied in your architecture, all of that needs to be part of the same deploy so you can redo the deploy before that one. With a monolith, you get a simple deploy of all dependencies, as they are baked into one thing.
There are down sides of everything baked into one thing. Having all your "micoro" servies deplyed as one package, would make the dependency you have act as before the monolith change.
Seeing this kinds of dependency imho even in a monolith are an architechture problem, that in the monolith shows up at code changed and fixes can't be handles by localized fixes, but changed have to go into large parts of the code base.
