Acronym Soup
Here’s one that should be entertaining — a listing of all the acronyms I come across on a daily basis, along with my opinion (or other tidbits) on them:
- PHP — originally “Personal Home Page”, now the recursive acronym: “PHP: Hypertext Pre-processor”. Not too painful to use, given the alternatives.
- PERL — “Practical Extraction and Report Language”. AcronymFinder also lists “Pathologically Eclectic Rubbish Lister”, which is reasonably accurate, from my experience with it.
- SQL — “Structured Query Language”. Not “Standard”. Unfortunately.
- SSH — “Secure SHell”. Uses SSL (see below). Very solid and reliable, in my experience.
- SSL — “Secure Sockets Layer”. A technology for implementing mostly-transparent secure data transfer.
- HTTP — “HyperText Transfer Protocol”. Stateless, Simple, and Stupid. Also, very useful.
- HTTPS — either “HTTP, Secure”, or “HTTP over SSL” (which, IMO, should be HTTP/SSL), depending on who you believe. See also HTTP, SSL (above).
- SFTP — “Secure File Transfer Protocol” (not to be confused with FTPS, which is actually FTP/SSL, and doesn’t have much traction in the real world), a service provided by (Open)SSH servers in addition to the shell service.
- AIM — “AOL Instant Messenger”. Crappy software, but with a third-party client like Pidgin is actually reasonable. See also AOL (below).
- AOL — “America OnLine”. Shitty company, well known for being asshole-ish towards its customers (known internally as “members”).
- Y!M — “Yahoo! Messenger”. Semi-crappy messenger service. Reasonably functional, though, and quite stable.
- GTalk — “Google Talk”. Another messenger service, this one built on Jabber/XMPP (see below) and made by Google, the “Don’t be evil” company. Not too evil.
- XMPP — “eXtensible Messaging and Presence Protocol”. An open standard for exchanging (instant) messages over an XML-like protocol. Speaking of which:
- XML — “eXtensible Markup Language”. I just love these X-acronyms, they always make me feel like I’m living in the future.
- IRC — “Internet Relay Chat”. Yes, people still use it. Some pretty awesome people, in some cases, as it turns out.
- APT — “Advanced Packaging Tool”. So far, the best package management tool I’ve seen. However, my experience is limited, so a grain of salt is recommended.
- PTS — “Pseudo-Terminal Slave”. What your SSH session spawns into: a terminal with no associated hardware (virtual or otherwise).
There are probably more I’ve missed, but these will do for the time being. How about you? What are the interesting/important acronyms that you work with every day?
3 Comments
Add your comment
XHTML: You may use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

A very important one I come across every day is GIGO – “Garbage In, Garbage Out”.
There are others, but they are sooo biology-specific that I’ll spare you the white noise.
Oh, and my university is using SFTP. There’s a nice Firefox add-on I’m using for that, FireFTP, which provides easy r/w access to all kinds of ftp-like servers.
Gah, I meant FTPS, sorry. I suspect it will get more traction in other places that have the SSL infrastructure in place and don’t want their users thinking about even asking for a shell.
Anyhow, FireFTP speaks both.
Well, Wikipedia says the FTPS RFC wasn’t finalized until 2005, which is probably why SFTP (which, as it turns out, stands for SSH FTP, not Secure FTP) gained lots of traction. Plus, I guess it makes sense for us programmer types, who really do need that shell account, too.
I actually ended up buying StfpDrive for my internal networking needs, but for the huge file listings we have at my workplace, WinSCP remains king.