PHP. It's also the language I'm probably most fluent in.
Or Batch. (a lot of people will shoot me for saying that, but I like how it gets things done right away in just one command. Few other languages have a single three-letter function to delete a file.)
perl has unlink. Visual Basic has kill. BASIC has kill as well. BASH has rm. python has os.remove, C#/VB.NET has File.Delete().
As far as I'm concerned, the fact that a given language/shell happens to be have a shorter command to perform certain functions only serves to deepen the ambiguity. Bash has rm, but seriously, how is that self-indicating? Sure, it stands for "remove" but it could just as easily stand for Raise Modifier, or "reset mysql" or something (and rm=remove.... remove what?) same with "kill" in VB6 is ambiguous, and hardly self-documenting, since you will have to look it up if you don't know what it does. File.Delete() requires absolutely no information to understand what it is doing. Yes, it does the unthinkable and requires more typing- but it's more clear. The shorter you make keywords, functions, and parameter names, the more likely it is that what you are working with becomes write-only. Consider the premier write-only language- regular expressions, and how most of it's structures are a single character or bracketed set of characters, then come back and tell me how that serves an advantage to people trying to read it.
So Batch has del, which is really just a short form of erase (though I don't remember which was first). this makes sense, one can assume any non-associative command is probably to do with files. SQL has "DELETE" as well, but it is specific to it's own domain whereby it deals in database structures. new functions, classes, namespaces, and libraries need to be designed, not just thrown in randomly. Particularly in polymorphic languages, where you ought to be able to deal with any number of related structures in similar ways. Or, you could have languages like PHP which start out without any long-term goal and as they develop new features are just tacked on with new functions using a naming scheme that seems to depend more in the chinese calendar than it does on trying to be self-documenting.
PHP is a fine language, for it's own purposes. Honestly I think a little piece of me dies inside when I am forced to deal with it. Not because it's a bad language, but because the standard constructs are just so awfully planned out. Quick- without looking it up- is the function isset() or is_set()? is it isnull(), or is_null()? Do you call sort() or array_sort()? etc. I stopped bothering to even try to remember half the functions outside the few more consistently named ones and just keep about 20 tabs open to PHP documentation, with a side of some alcoholic beverage to keep me sane, when I need to deal with PHP. One blessing it has is that you actually have to explicitly mark variables global, which is a good thing to keep from polluting the namespace. But when it's already filled with so many functions with inconsistent names, return values, and parameter lists I'm not really sure you could pollute it if you tried.
