I wonder about the psychology. Is it like chain restaurants - the brand name and decades of experience guarantees a floor on quality, with people estimating their DIY as having a much lower floor. Plus the laziness of starting from scratch
Then when you start it's obvious sunk cost fallacy
> I think that the Brexit vote landed at a time when there was increasing general alienation within society, a general feeling of growing wealth inequality, of social injustice etc
Hmm GDP was growing well, inflation was down, real household income was on the rise, annual wage growth was on the up, it was a long time since the great financial crash, unemployment was crashing in 2013/2014, and things comparatively were quite cheap.
Though I can't recall the general sentiment at the time. Net migration did have an historic spike (part of a longer term rise) for a couple of years. Perhaps the Brexit campaigners capitalised solely on that?
Crazy to imagine that economically things were doing great, by many metrics, but so many people got duped into thinking some foreigners were going to tank everything
(Personally, it was a fantastic period. Wages were good, jobs were good, things were cheap. I know many people who bought their first house during that period)
Exactly! It's not like we have decades of evidence that the demographic which has consistent high turnout is consistently and significantly politically pandered to in many, many regards. No sir
For whom have you voted? We have almost no referenda sure, but sometimes there are strong hints in the manifestos, or things to learn from past behaviour of each party
Secure app spawning is a per-app toggle now so it doesn't reduce OS security or the security of other apps without it disabled. It only reduces security of the app with it set to disabled. If multiple apps have it disabled, they share the same ASLR bases, memory tags for memory allocated before fork and other things.
It's one of the toggles changed by the per-app exploit protection compatibility mode. If an app doesn't work, that's the first thing to try. It can then be narrowed down to a specific setting.
The more aggressive exploit protections uncovering a lot of compatibility issues are only enabled for the base OS and specific user installed apps by default. Those can be set to enabled by default for all user installed apps and then people have to deal with the per-app toggles a lot more. This applies to memory tagging, disallowing dynamic code loading via memory/storage and disallowing native debugging (ptrace).
It's because PayPal shipped an update with incorrect anti-tampering code incompatible with secure app spawning. It can be worked around with the per-app secure app spawning toggle until they fix it.
Is your comment based on the body of the article, or the title? The article explains right near the top that it was ruling on it being classed as an occupational disease:
> Sophie Lainault...sought to have her cancer recognised as an occupational disease, brought on by conditions at work.
> This has now been confirmed in a landmark court ruling...which said that cosmic radiation was one of three carcinogenic hazards arising from her profession. The other two were passive smoking and prolonged night work.
Then when you start it's obvious sunk cost fallacy
reply