We have perfectly good helicopters today, but you don't want one on your street. Just a few basic physical problems that won't be solved without antigravity.
Just as soon as the Moller Skycar is ready. It'll be real soon now, right? He's only been working on it for about 50 years.
Despite the brass ring TOS of whatever version you were previously running, an infection is as an infection does.
Also, read your antibiotic prescription carefully.
* may include systemd[**]
[**] First we keep Berlin, then we take Warsaw, someday soon we annex Prague, and eventually perhaps we'll incite the Arabs to cut Manhattan down to size.
All hail PC-BSD: the systemd-free libertarian antibiotic of last resort.
s/Hackers/contributing members of society/
Even a 64-bit address would have been seen as doubling memory requirements of routing hardware for no good reason.
There could have been an optional 32-bit client sub-address ignored by the public routing backbone.
Then, for most purposes, non-backbone routers need two routing tables: a routing table for the public network (if more complex than a few simple gateways), and an organization-local internal routing table (with 32-bit addresses, just like the public table).
The actual problem is that each TCP/IP connection would require for the connection tuple (src_IP, src_port, dst_IP, dst_port) not 12 bytes, but 20 bytes.
Probably something could have been done to mitigate that, too, as things stood long ago, but I don't feel like speculating further just now.
Even without mitigation, let's suppose you have an FTP server and you want to guarantee at least 16 kb/s for each active FTP connection (circa 14.4/28.8 modem technology). You need to provide nearly a kbit/s network bandwidth per byte of connection tuple held in system memory (we'll ignore the messy nature of FTP, much of whose ugliness could have been averted by a better original IP design).
At the same time, NAT isn't all bad. It does help to conceal the internal structure of your network from the evil public network (and makes exposing your non-firewall hosts more of a sin of commission rather than a simple sin of omission).
NAT also erects a barrier to ultimate host fingerprinting and traffic analysis, at least until HTTP came along to ruin things with user agent strings and cookies.
Some people are quick to point out that a low barrier is no barrier at all, but I like to force my adversaries to at least put on their ballet shoes before attacking my network, and then to stay alert for people with trunks full of tools good at hopping low barriers.
My proposal doesn't much complicate the backbone routing table, except for Sandvine, who would have—once we got there—been pissed in a big way (counterfactually), to much rejoicing.
For this one, no pretense of family language.
This post will cover first the competition fine print; then the long-term relationship; and, finally, the lamentable low bar responsible for this Tourettic outburst.
To qualify for certification, the DA candidate must be able to distinguish when I'm searching something deserving to bring it more fully into my consciousness, and when I'm searching something horrawful to determine the appropriate size of BFBM (big fucking black marker) required to cross that POS—along with any predictable next of kin—out of my life For-Fucking-Ever.
Digital assistant, read my lips: having now surveyed the top twenty search results in any extreme lather of sudden aghast attention, be it resolved that I hate this thing per the aforementioned For-Fucking-Ever. Please eradicate with extreme vigilance, or crawl back on your pathetic digital stomach to the corporation that brought you into this world with no goddamn balls.
YouTube, for example, keeps on suggesting styles of videos I explored for a tawdry half hour at some point in the distant past, long after a sane AI would have wooshed that bowel movement down the egress funnel, around the septic hair pin, to swirl and merge into the collective effluent.
But no, Google has settled for the derp, derp, derp algorithm in which it presumes that if you ate it once, you'll surely eat it again—forgetting, I suppose, that it gave you the major shits—so long as we continue to wave it under your nose until the end of time.
Nicely done, YouTube.
First, I'm sure there's lots of Open Source being used in Google's implementation - just not where we can see.
There is a speech recognizer from CMU that might be a good starting point. I haven't heard about plain-language software, though. There is additional rocket science to be done. Not insurmountable given things we've already done.
Training with millions of people? Actually, that's the part that community development is good at.
10 to the minus 6th power Movie = 1 Microfilm