95014_refugee

See also “information desert” and ask yourself why a survival-oriented species might behave in this fashion.

Or don’t, it’s why they do.

“sj placed cool first” … in what universe?

Steve placed “Steve likes it” first. Many of the things he liked were terrible.

Cool things happen(ed) at Apple in spite of executive leadership, not because of it. The better E-team players know to stand back and not get in the way.

You are confusing waterfall with BDUF.

I do wonder how much of the hate on “waterfall” is perpetuated by folks that never read the paper. It’s the “socialism” of development workflows…

The exploit as described doesn't "brick" the device; that would require permanently disabling it. A tethered restore would be all that's required to recover in this case.

It would never have worked. So many of the things that owning xnu has made possible would never have happened on top of Linux. The things you can do when you know each and every customer of the stack, and you all belong to the same business with common objectives and leadership direction just can’t be done in the open-source context.

For a long time we held the line on not having file operations originate from within the kernel (layering reasons). Eventually less sane heads prevailed.

No.

One does not "hone in" on anything. To hone a thing is to make it sharper or more acute by removing parts of it with an abrasive. The word you are looking for is "home", as in a homing missile, etc.

Yes, this is a criticism. Hopefully it's twice as effective as being nice. 8)

Responding to a TCAS RA is not "overly cautious".

It's not inoperable; warnings are still issued, but the RA (resolution advisory, i.e. "climb", "dive" etc.) functionality is inhibited.

This makes some very naïve assumptions about the relationships between entities in a program; in particular that you can make arbitrary assertions about the representation of already-allocated datastructures across multiple versions of a component, that the program's compositional structure morphs in understandable ways, and that you can pause a program in a state where a component can actually be replaced.

By the time you have addressed these, you'll find yourself building a microkernel system with a collection of independent servers and well-defined interaction protocols. Which isn't necessarily a terrible way to assemble something, but it's not quite where you're trying to go...

You mean “can’t resist the name placement kickback promises”, surely.