cdonnellytx

Anyone else having trouble viewing this page? I'm on iOS and every time I go to the link it redirects me to a page claiming I "won" a "reward" with an alert box that I can't dismiss without tapping OK.

The problem is even _root_ can't add the missing /usr/local, because SIP prevents even root from touching /usr. SIP doesn't block /opt; if it did, MacPorts would also have broken, sudo or no sudo.

They even put the Decline button on the left, which goes against how virtually every other Windows installer (and wizards in general) are supposed to work.

The problem here is that "the West" is one of the regions "from which the West gathers intelligence". The NSA and GCHQ are both spying on even other Western countries like Germany, to say nothing of spying on their own citizens.

Too bad they couldn't even tell him what set it off, since he clearly did not remember:

  "I can’t think of anything. What does it say is triggering the alarm?" I asked.

  "I’m not going to tell you! It’s right here on my sheet, but I don’t have to tell you what it is!" he exclaimed, pointing at his clipboard.

''EDIT: formatting''

Maybe instead of "going dark" that should be what the homepage redirects to for that day. That way it raises awareness and provides reading material.

Unfortunately, they will take note of it as "run the government like a business", which tends to be how supply-side economists would prefer the government to be run anyway.

One simple reason I switched back to old-style scrolling: I also use Windows, and would definitely have issues going back and forth with the different scrolling styles.

The annoying thing is that the mklink command in Windows uses the opposite order, so you have to do

mklink link_to link_from

EDIT: formatting.

Which is what makes it even worse: it's not that they can't do it on the iPhone, it's that they won't.

And why not? It can't be a question of RAM: Java has had GC back when the average home computer had half the memory available in the first gen iPhone. Nor can it be efficiency: most GCs these days are efficient enough for the average program, and a developer can always disable it if she prefers manual memory allocation.

My point is that it just ends up being yet another example of Apple making arbitrary restrictions that do little for performance or user experience, while causing a lot of pain for developers.