longpath

I confess to certain level of surprise that the FCC is oddly silent on this matter, as the FAA is essentially encroaching on their ostensible purview. I should also point out that the various US militaries have used C-band devices in conjunction with military aircraft without ill effect and have been used for terrestrial and satellite communication since the 1950s, so any dire consequences ought to have surfaced long ago.

My concern with resurrecting the MacBook name is the possibility of it only offering USB-C, without Thunderbolt, as was the case with the prior model. The current Air, ought not to be succeeded by a model that drops Thunderbolt.

The entitlement of people with little to no comprehension of supply and demand, let alone the rest of basic economics has a high correlation with absurd demands that have little to no chance of being fulfilled. Typically when such economic illiterates fail to get their way, they use the state to threaten violence by proxy to coerce their objectives into being, so I expect that will be coming next.

In short, students of Swift are screwed, especially if they’re trying to finish a project before the end of the semester. It’s interesting that the assumption made by many is that this flub has no meaningful consequences and disregard the fact that anyone building a skill set starts at a low level at some point and derailing the person at the low point of skill building has long term consequences. Hopefully Apple corrects this before the end of the week, so the only long term consequence will be that students will hold off on updating until the end of their projects when such updates arise in their future. I’m in the process of learning Swift on my own, and fortunately haven’t run this update; butI can only imagine the stress and anxiety of Xcode nuking a semester final project a week & a half before the due date, if I were still a university student.

Never grant the state any power you would not entrust to your worst enemy. This isn’t a hard concept.