Readit NewsWhen I read the comment I was immediately flabbergasted: no, someone else fucked up. It's not my fault someone wrote software that sets up undocumented traps for me to fall into. Or provided three ways to do something and two of them are not recommended OOTB. Or is primarily documented by third parties.
Its a little hard to make blanket statements that weapons/warfare are bad. There are good times to use weapons.
An obvious one was at the time of WWII. If the clever people had refused to work on weapons, things would have finished up potentially a lot worse for mankind generally.
And perhaps in our medium term future, as climate change becomes more and more real, a critical mass of people will decry the continued burning of fossil fuels. And if retrograde nations continue to poison our common resource, then maybe some global police force will need weapons to stop them.
I acknowledge some warfare may be legitimate (having been bombed myself), but arms companies don't stop at selling to your personal favorite army which you consider morally right, they keep looking for more business abroad.
I don't want to be the one realizing I'm sitting in a cozy air-conditioned office and having made money from the messed up warfare in some distant far-away country, having a large financial incentive to cause more conflict there.
Deleted Comment
Link prefetching is already a thing, so I don't see why we need another standard to resolve this.
Also the privacy argument is moot, I believe. In the questionable example of the AIDS patient, you are instead trusting Google with this info. That is not any better to me.
I'm a front-end developer and I see so many sites bogged down with many analytics and tracking providers, some multiple times. I can't help but feel like AMP is an attempt to maintain the tracking and analytics status quo, while giving the illusion of performance, instead of just chilling out on the multiple redundant client-side analytics.
It almost seems like the web is unusable aside from companies large enough to have a mirror here.
As a concrete example: my personal mail server (on a modern operating system) has its SMTP handling in a separate process from mailbox serving. If the SMTP process is compromised, and the attacker reaches uid=0, it doesn't matter -- no data from the mailboxes can be exfiltrated.
Only SMTP is broken, because mandatory access control prevents the SMTP "root" from doing anything the SMTP daemon would not ordinarily be permitted to do. The SMTP daemon is not empowered to read mailboxes, even if its uid is 0.
Then again, I admittedly learned 8080 and then Z80 and x86 first, so any RISC feels too simple; but those who learned any RISC first probably feel the exact opposite.
modern MIPS has "ext" and "ins", which are probably an improvement in that regard.
> plentiful-yet-unhelpfully-named registers
what's wrong with MIPS register names? my only comparison is x86 and that has been awful. I'm constantly looking up which registers are what.