Potential Names for the Next Generation of Wget

This is a page for discussing what we should call the next generation of Wget, which for the most part has been called Wget 2.0, but whose intended scope and feature set is really becoming significantly different from traditional Wget.

To see what Wget 2.0 is going to look like, see the "Next Generation Features" and "Unofficially Supported" sections of FeatureSpecifications. Also, see the thread at http://www.mail-archive.com/wget%40sunsite.dk/index.html#10511

So, here's the list. Discuss 'em! If you add new entries, please include a summary of the reasons why you think it's a good choice.

• Wget 2.0

  Micah: I'm not sure I like this, because it's looking to me like an app with a fundamentally different focus from Wget 1.x. On the other hand, it wouldn't be the first time an app has shifted focus; and the fact that the 1.x Wget will probably be moving to bug-fix-only-mode in a year or two means we probably don't have to worry about wanting to use the 2.x designation for a next-generation version of Wget that is closer in scope, functionality and interface to Wget 1.x. Still, I prefer an entirely new name. There might be an advantage to continuing to use the name "Wget", in that people who have already filed copyright assignments over future work on Wget won't need to file new ones just because of the name change.

• Awget
  "Asynchronous Wget" (referring to its asynchronous infrastructure for fetching multiple files)

  See Pget for similar reasons why I dislike this.
  ("Awesome-er Wget"?)

• --Reget-- "Recursive get", or "Re-envisioned Wget"

  Micah: I like this one best so far, personally.

  Daniel: See reget.com, it seems this is already a "Powerful and super-fast download manager with resuming."

• Pget "Parallel get".

  Micah: To draw attention to the fact that it supports multiple simultaneous connections to different hosts. What I dislike about this one is that parallel downloads is going to be only a part of the new functionality for this software; and in fact it won't even be supported for some planned modes (for instance, parallel connections would be impossible when downloading content to a multipart/related file, or gzipped tarball).

• Tget "Torrent-like get".

  Micah: Probably referring to the planned support for MetaLink, which allows fallbacks to a different location, or fetching multiple pieces of the same file from different hosts. However, this is not currently planned to be part of Wget's "core" functionality, but rather a plugin (though that is subject to change).

• Bget "Bigger get"

• BBWget "Bigger, Better Wget"

• Wim

  "Wget improved"

• Fetch

  Not yet taken, according to yurimxpxman (Joshua David Williams).

  Daniel: This is the name already used for a http/ftp transfer tool in FreeBSD

• ExtGet or ExtWget

  Josh: Denotes that the version is an extension of the original Wget project, but with more functionality.

  Micah: Eget might make a possible alternative. Or would that imply that it's an Emacs mode? How about "Ewget"?

• JustGetIt

  Micah: I prefer short names that don't require the shift key to type at the commandline.

• GoFetch

• SuckItUp

• Hoover

• DragNet

• netsucker

• getit

• getw

  Micah: kinda has a nice ring to it.

• suck

• hose

  Micah: "hose" sounds more like pushing than pulling, to me.

• vac

• wgrab

• wfetch

• slurp

• webvac

• obtain

• wvac

• whisk

• w

• sinkhole

• cenote (see http://en.wikipedia.org/wiki/Cenote)

• wpull

• pull

• drain

• xget (x being the letter after w, and could also stand for Extended Wget (see ExtGet).

• niwt (Nifty Integrated Web Tools)

• wgetng i propose wgetng, or nget (new wget) or maybe wgete (wget extended)

• retr

• dl

• dload

• down

• aquire

• transget

• yank