MISRA is just a set of regulations. C++ can be fine for safety critical systems, if it's done correctly. You just have to do it right and enforce the standards.
And MISRA doesn't have much intersection with safety; it mainly enforces archaic usage patterns. But there is not just one MISRA; it evolves, and might be getting more useful. But very, very slowly.
Historically wolf culling has been more about protecting livestock and pets than people. It's also helpful for hunters to make sure they're not competing for deer.
You still have to deal with the residuals from desalination. About 1/3 of the salt water is useable. The other 2/3s is a brine that can not be used. Not to mention what are you going to do with all of that salt and biological material you just pulled out? You aren't going to be able to sell it.
The water distribution on Earth is 97.5% salt water and 2.5% fresh water [0]. Out of those 2.5%, more than 2/3 of the water is trapped in glaciers and ice caps. So overall we have about 0.8% of the Earth's water available for consumption.
So our actual consumption is far below even those 0.8%. But our problem with fresh water isn't necessarily that it's not enough but that it's very unevenly distributed and we tend to be very wasteful.
This being said how much desalination do we have to do until the brine (now 30% more saline than regular salt water) is significantly affecting the overall salinity of the oceans? Desalinating 0.2% of the ocean's water would give humans a 25% more fresh fresh water and the increase in salinity would be marginal.
Does anyone know if an increase that looks as minute as this (0.1% increase is salinity?) is actually a real danger to ocean life and/or currents?
I think the problem with brine salinity is that it’s dumped in concentrated areas which might be teeming with sea life. If they evaporated it and dumped huge salt blocks in ocean deserts it could have less impact on marine life.
I imagine this isn't a hard problem to solve, there are no major technical limitations to doing something like this and might not even drive the cost up that much.
There are other aspects of desalination that seem far more critical, like the ones related to efficiency and the scale of the required infrastructure.
My impression is that it's easier to attack than to defend or detect. That would make the country who doesn't attack a sucker. So treating it as an act of war isn't viable.
>I agree, nobody in their right mind would audit every such expense.
I'll bite. Our money counters aren't in their right minds, because I submitted a small breakfast tab (at most $10) from work travel for reimbursement, only to learn it was unacceptable to not include a receipt. My other meals had receipts, but I had forgotten to ask for one this time. The accountant then said I had to call the cafe for a receipt. Luckily, the place had a website with contact info, and there was a helpful employee who emailed me the receipt.
But I spent at least an hour talking with the accountant and getting the receipt. The accountant spent probably 30 minutes with this problem. It was a net loss.
An ideal platform would use a foss compatible framework. It would allow the user to configure which server to use to push notifications(one server for all apps, since that is needed for battery reasons). Notifications would be encrypted with the apps key.
Often times even having configuration options creates surface for security issues.
A good example of this is that there were scams that involved having people paste some script into their chrome devtools and steal data. This worked fairly effectively. Facebook ended up doing some magic to show a warning message in the devtools console to tell people that no, you really shouldn't paste random stuff here, it will do bad things.
Configurability does come with a cost. And "the ability to reroute all push notifications through an arbitrary MITM" is a security cost that I expect wouldn't be worth it.
But I actually think you are mis-portraying the situation is because I don't think the average adult has the ability to comprehend these things. It's not the difference between adults and children, but adults and expert adults.
Here are some analogies to other parts of society that we don't have a problem with:
Seat belt laws
Hard hat required construction area
Safety guideline in Handling of hazardous materials
We basically said society doesn't trust you to decide for yourself about your safety - you just have to follow the rule.
>It's not the difference between adults and children, but adults and expert adults.
Part of me wants to challenge the existing groupings of adults and children where all that matter is if you have been around the sun 18 times or not. This is but one weakness in the existing grouping that furthers my questions, such as why do we allow the non-expert adults a vote over laws, but deny a 17 year old the same?
I think if you take the groups of children, adults, and expert adults you will find upon reducing them to only two groups based on similarity that you are left with experts and non-experts.
Except a large portion of society thinks seat belt and hard hat laws are bullshit and shouldn't even be legal to enforce. Hazardous materials handling is completely different though.
The impulse to protect people from themselves is a dangerous one. In the article itself we see that in practice it is used to push inescapable spyware.
"But our spyware is better than their spyware!"
Google says they will protect you. But the truth is they are just concern trolling to shut down marginally worse competitors.
For kids and elderly that can't make decisions on their own it could be default -locked to some entity contractually bound to good ior. Locked with an administrator password. That would be a reasonable compromise.
No the truth tends to be more banal - making everything replacable in configurable means more (paid) engineering work for Google engineers for what's, essentially, building infrastructure for competition. What would be the compelling business case for Google to do more work to enable removal of their own product?
This is possible to build on Android right now and something I've thought about myself. There is nothing stopping you or me from implementing it, and I've always thought that Amazon should have done it to make it easier to port applications into their ecosystem.
I like that its going mainstream in the sense of quality control and regulated dispenseries and hitting cartels in the wallet but I don't really like seeing it going mainstream in the sense that it's allowed to be advertised. If people want to do weed let them, but it shouldn't be encouraged.
