Posts by Aremmes 86 publicly visible posts • joined 11 Dec 2007
Native Spanish speaker here. "Otoño" has the same root as "autumn" (namely, Latin "autumnus"), and learned that translation from my English teachers at school. I learned of "fall" after moving to the US mid-Atlantic, and also that people here don't seem fazed when hearing one or the other -- it's all the same to them.
Presuming that the -ret… part came from the Latin word for “net”, rēte, which is third declension, its singular genitive would be interrētis.
Thanks for the correction.
The modern Spanish descendant of ruptus is roto, but given the current definitions of roto, it might not be the best choice from which to coin a Spanish translation of “router”.
Roto/a (meaning broken) is one descendant, the other is ruta (meaning route), e.g. Ruta Panamericana.
Surely you meant to say *ductor interretī* given the second declension genitive, right?
It bugs me that there seemingly doesn't exist any good Spanish translation for router (*enrutador* doesn't sound right even if the parts look correct), or for a lot of IT terminology for that matter. The English language truly has cemented its hegemony in this field, for better or worse, and it doesn't appear to be losing ground there, ductores interreti notwithstanding.
Why not? It has done its intended job for decades and provided its users with clear upgrade paths to enable them to use modern technology without requiring them to abandon their old, stable codebases, and will continue to do so for the foreseeable future. The downsides of migrating off mainframes onto PC-based server networks are various and well documented, and anyone who attempts to do so without taking the cost of those downsides into account will only invite disaster.
Jamie Zawinski's classic XScreenSaver is still around, updated to work on MacOS (and still works on Linux/Unix). The BSOD mode is still there, updated to include more dead computer screens: the man page on my computer lists Windows, NT, Win2K, Win10, Ransomware, Amiga, Mac, Mac1 (another sad Mac, MacsBug (debugger screen), MacOS X, SCO, Atari, BSD, Linux, SparcLinux, HPPALinux, BlitDamage, Solaris, HPUX, Apple2, OS390, Tru64, VMS, MS-DOS, OS2, HVX, VMware, and Android. The last one is interesting as it's not really an Android screen but an HBOOT screen pretending that the boot volume has gone for a walk.
You recall incorrectly. In X, the server is the process that manages the display and input devices (keyboard and mouse) and the clients are the processes that use the display and inputs as mediated by the server. This inversion was deliberate, since the display, keyboard, and mouse are finite shared resources much like disks, printers, etc. can be finite shared resources. Per Wikipedia, "X takes the perspective of the application, rather than that of the end-user: X provides display and I/O services to applications, so it is a server; applications use these services, thus they are clients."
"GNU Emacs began life in the 1970s and is currently at version 25, which means it averages two releases to Vim's one, but still definitely on the slow side."
Actually, GNU Emacs is technically still at version 1 -- the 25 is the minor version number. It is said that RMS will release version 2 when the first stable version of GNU Hurd comes out.
"The main limitation of NAT is 16 bit ports. If port addresses were expanded to 32 bits, we'd probably be fine with IPv4 pretty much forever."
For larger networks you can set up source NAT pools, so that connections are spread over a number of IP addresses instead of a single NAT address (e.g., the NAT router), thus avoiding the 16-bit port number limit. Cisco has supported this since when NAT became a thing.
"Most Spaniards I'm guesing they will pronounce WhatsApp either "WASAP" or "WARSAP""
I can tell you that when speaking Spanish anything that introduces pauses into the syllable timing will get summarily dropped. Hence, "wasap" instead of "watsap". Spanish makes little use of syllable final consonants outside of "m", "n" and "s", and even then has a preference for ending syllables with vowels -- e.g., notice the aspirated final "r"s and "s"s in Caribbean Spanish.
Third-party software vendors have something to do with it, I'm afraid. Where I work we have a big "enterprise application suite" -- ERP stuff. It's a big nasty hodgepodge of PL/SQL, Pro*C, Pro*COBOL, Java, Forms, and other things that should be declared Not Safe For Work, very tightly integrated with the database and associated Oracle stack products. Unsurprisingly, the vendor certifies it compatible only with Oracle, and will not support its use with anything else -- I think they might even consider the use of another database product a violation of the contract or some other equally ludicrous claim. Fortunately, I'm not a DBA, nor do I want to be one.
Cray did something like that at least twice already. The XD1 uses ASICs to extend HyperTransport into a switched fabric to link 144 processors together into a single system image. The XT3 and successors connect the CPUs to the SeaStar interconnect via HyperTransport.
The processors can connect to each other without any glue logic but that consumes HT links quickly. One can only add so much to the die and packaging before it gets too expensive.
At last Google is at least acknowledging the search spam problem. Now, will they do something about the keyword search spam sites and the shopping spam sites that I keep getting in my search results? Take care of that, Google, and you'll have gotten rid of most of the spam results that I've faced.
So the requirements say that a method to asymmetrically authenticate a message is needed. There are several digital signature algorithms available, many within reach of a Google search. What do we do? We'll ignore decades of crypto research and invent our own signing algorithm, of course.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2025
