Trump is not unique. You can find similar parties and figures in most of Europe. Usually the would-be autocrat populist is even more popular than in the US in two party systems. Multi party systems dilute it which just leads to paralysis until eventually >40% of your population is ok with abandoning democracy because the impacts of paralysis are stacking up (France).
When a bridge fails, it is the professional engineer that signed off on that part. If you want someone to sign off on software or IT you will need to pay them quite a lot.
Yes, I would expect compensation to increase proportionally with accountability. What makes no sense is compensation that increases irrespective of accountability.
Being the CEO of a company that handles risky, sensitive things should be risky for the CEO, personally. And their compensation can reflect that.
That could be outlawed as well as it probably wouldn’t be too difficult to show that person wasn’t actually making any of the decisions. Not that I expect any of this will ever happen.
I wouldn't describe software as most people experience it as more complex.
And civil engineering projects are constantly fixing unforeseen design problems either during construction or afterwards.
I would distinguish the failure modes as different though eg analog vs digital. Real world engineering can absorb an awful lot of minor mistakes through safety factors etc. Failure can be gradual or just a matter of degree or even just interpretation of standards. Software failures are often more digital or only matter when "under attack"
Too late now, but is the requirement for shared mutable state inherent in the problem space? Or is it just because we still thought OOP was cool when we started on the DOM design?
Yes. It is required for W3C's DOM APIs, which give access to parent nodes and allow all kinds of mutations whenever you want.
Event handlers + closures also create potentially complex situations you can't control, and you'll need a cycle-breaking GC to avoid leaking like IE6 did.
You can make a more restricted tree if you design your own APIs with immutability/ownership/locking, but that won't work for existing JS codebases.
But it matters for detection time, because there's a lot more "normal" use of any given piece of code than intentional attempts to break it. If a bug can't be triggered unintentionally it'll never get detected through normal use, which can lead to it staying hidden for longer.
Swift is very slow relative to rust or c though. You can also cause seg faults in swift with a few lines. I Don't find any of these languages particularly difficult to read, so I'm not sure why this is listed as a discriminator between them.
You can make a fully safe segfault the same way you can in go. Swapping a base reference between two child types. The data pointer and vft pointer aren't updated atomically, so a thread safety issue becomes a memory safety one.
When did that happen? Or is it something I have to turn on? I had Claude write a swift version of the go version a few months ago and it segfaulted.
Edit: Ah, the global variable I used had a warning that it isn't concurrency safe I didn't notice. So you can compile it, but if you treat warnings as errors you'd be fine.
I don't think it is meant to read left to right but top to bottom. Chicken and broccoli are top center, and that is the standard weight lifter meal plan. That said, human dietary needs vary individually by far more than any lobbied leaders will ever communicate.
The website is animated, so there's no question of which direction to read in, the left side literally pops up first lol. I can't lie, I miss websites that stood still, this could've just been a PDF.
BTW, you say "lobbied leaders" -- if you're talking about the scientists who have their names on this report, you'd be very correct. The "conflicting interests" section has loads of references to the cattle and dairy industries.
Authoritarian regimes very rarely get reverted if they aren't external powers ruling a separate group. Can you give some examples where it happened? I don't know of any that lasted very long.
I am a dsp expert. I still find it's explanations delightful and useful perspectives. Also very good for new team members who are better at code than dsp, which is most of them.
reply