Does this mean the next release of The Matrix on whatever 4k/8k media will have the credits list The Wachowski Sisters instead of Brothers?
I'm a pretty liberal dude, but the fervor of pronoun discussions these past few years grates on me in a way I can't quite put my finger on.
Where's my Chrome plugin to replace any instances of he/she to "ze" (or "it") already!
Small cells negate the "limited amount of spectrum" argument. It's a financial + logistical + political/regulatory limitation, not a technical one.
Technology will eventually advance to the point that the financial consideration is less important. We're already working with beam-forming -- a technology that's existed for decades, in radar applications -- for instance. Wireless is the future, no matter what the naysayers think, and if you're still thinking of "spectrum" as the limiting factor you're behind the curve. Makes me think of the folks who deploy IPv6 for the first time and start worrying about the "waste" of addresses.
My iPhone 7 came with *both* wired EarPods and an adapter for legacy headsets.
Only an Apple fan would use the term "legacy" in reference to a 3.5mm headphone jack.
There's no technical reason why an LTE network can't be engineered to provide truly unlimited data with acceptable speeds in most instances. There is, however, a financial reason, plus the usual regulatory/political concerns that get in the way of new cell sites. It's worth noting that T-Mobile manages to offer unlimited with an asterisk (video throttled to 1.5Mbps) and in many cases delivers superior speed than Verizon, so it's clearly POSSIBLE and PROFITABLE to use as a business model.
In rural/fixed-wireless settings LTE is actually cheaper than DSL/cable and the favorable contention ratios (i.e., low population density) make unlimited possible with today's network. It's a mystery to me why they won't offer an unlimited product for this market segment at least; it would be the death blow for satellite internet.
The big issue I see in my daily work life is that management acts as if using a third-party solution, be it proprietary or open-source, means we will receive perfect code at the beginning and never have to update it. We lock versions early in the dev cycle, but if a new version comes out mid-development there is a general distrust of changing to the new one.
And then, when the inevitable critical issue is discovered after we have release, we have no efficient plan on how to update. At least GPL solves that; when users have a pure-GPL system, they can always recompile/relink everything themselves after the big patch. But if I statically link a proprietary license library into our proprietary product, we have to step in and rebuild to get the fix out there. And the lack of preparation for this process does endanger security.
The management teams I've worked with are typically better at estimating and preparing for critical field breaks in "our" code. But that's why they like third-party, and that assumption of "perfect" that makes the future look so much better. So the bigger issue is that managers endanger secure software development.
Now there's a name I haven't heard of in a long time.
My first ever Unix account was on a Sequent Symmetry in 1990 for CS101 (RIP sage.cc.purdue.edu). The OS was Dynix, and I think the machine had six i386 cores.
Ah, those were the days, before shadowed passwords and TTYs with proper permissions. All via 9600-baud serial connections in the dorms. Fun stuff.
I put up my thumb... and it blotted out the planet Earth. -- Neil Armstrong