Sendmail is asking for trouble, until they completely throw out the old code and rewrite it from the ground up, with security in mind.
I'm pretty sure that's already beendone. And while many will argue that sendmail scales better than either, both Postfix and qmail are in used in some awfully large sites itself--I'd maintain that scalability is a non-issue. Still, sendmail admins are (paradoxically) easier to come by, and its code has been scruitinized very thoroughly, at least enough so that one could be reasonably comfortable with its security.
Eh, the ordering of the SI prefixes is actually kibi-, mebi-, tebi-, etc. See here for more such nonsense. I, for one, find the new prefixes horribly unpronounceable, and expect them never to take hold in colloquial usage, save for the nerdiest of nerds. That said, it would be nice for them to be used in print, since the ambiguity is annoying at times.
So, about this "oot and aboot" business... it's just plain wrong.
Though for Americans "aboot" is what might sound closest to many Canadians' pronunciation of the word "about," it isn't correct. The sound present in some dialects of Canadian (and American!) English results from a phonological process known as Canadian Raising. The "ow" sound is pronounced pretty universally in America as [aU]--i.e. a diphthong whose first element is like the a in father and whose second is like the u in put. However, before a voiceless segment (basically a consonant during whose articulation one's vocal chords are not vibrating), the first element is raised to an "uh"-like sound; i.e., the u in tuck. This also applies to the so-called "long i," in which the/aI/ diphthong is pronounced [@I]. (This is much more common in America than the/aU/ portion of Canadian Raising, too, so it's less widely mocked this side of the border.)
So, yeah, "oot and aboot" is wrong. That is all.;)
Actually, your example is a little weak. Before I attack that, however, I'd like to state that, while I'm not especially familiar with Japanese phonology, I rather doubt that/l/ and/r/ are in fact in complementary distribution; my assumption has always been that the Japanese/r/ shares qualities with the two English phonemes, but in fact is articulated as a single phone. I could be mistaken, and would welcome a correction here.
However, pronouncing a voiced phone immediate after a voiceless one, especially when the voiced one is a sibilant (which are very prone to assimilation), is more than just awkard, it's downright impossible; not just in English, either! Almost every language that allows for such consonant clusters has an assimilation rule wherein either the sibilant is devoiced or the stop is voiced (almost always the former, for what it's worth). This is universal grammar talking. Alternation between allophones by way of a phonological rule is definitely not something that is so strong as something that seems almost certainly to be part of UG.
Well, Nat certainly has cooled off his work on the project, though I don't think "abandoned" is completely accurate. Check out Nat's dashboard blog, and you'll notice a few updates since this summer (when development was really cruising). Also, it seems as though some outside parties have begun picking up where Nat left off (e.g. here). My guess is that Nat just got overwhelmed by the whole Novell acquisition.
There in fact is an open source effort to recreate it: here. I was just about to describe the complete lack of activity for the project, but, upon checking the last update for the website, it was only four days ago, so who knows. =)
I would be interested in finding out whether HP is planning on continuing to support OpenVMS; I know that Compaq had been planning to port it to the Itanium. Can anyone comment?
No they are trying to implement C#. Which will never happen.
Never happen, eh? Might I direct your attention to the Mono project, on which Ximian is currently working. They've had a self-hosting C# compiler for quite some time now running under Linux.
This is getting worse than journalling filesystems:-(.
Well, like it or not, that's more or less the sentiment after which this piece of versioning software is going.
Slashdot Mirror
> Personally I'm still looking towards solar or fusion....
Just so you know, biofuels are a form of solar power.
Hmm... but couldn't you just grow the algae in a large, "3D" vat and circulate it so all the algae gets its share of the sun?
Eh, the ordering of the SI prefixes is actually kibi-, mebi-, tebi-, etc. See here for more such nonsense. I, for one, find the new prefixes horribly unpronounceable, and expect them never to take hold in colloquial usage, save for the nerdiest of nerds. That said, it would be nice for them to be used in print, since the ambiguity is annoying at times.
I'd suggest that you never give Emacs a try, then!
So, about this "oot and aboot" business... it's just plain wrong.
/aI/ diphthong is pronounced [@I]. (This is much more common in America than the /aU/ portion of Canadian Raising, too, so it's less widely mocked this side of the border.)
;)
Though for Americans "aboot" is what might sound closest to many Canadians' pronunciation of the word "about," it isn't correct. The sound present in some dialects of Canadian (and American!) English results from a phonological process known as Canadian Raising . The "ow" sound is pronounced pretty universally in America as [aU]--i.e. a diphthong whose first element is like the a in father and whose second is like the u in put. However, before a voiceless segment (basically a consonant during whose articulation one's vocal chords are not vibrating), the first element is raised to an "uh"-like sound; i.e., the u in tuck. This also applies to the so-called "long i," in which the
So, yeah, "oot and aboot" is wrong. That is all.
Actually, your example is a little weak. Before I attack that, however, I'd like to state that, while I'm not especially familiar with Japanese phonology, I rather doubt that /l/ and /r/ are in fact in complementary distribution; my assumption has always been that the Japanese /r/ shares qualities with the two English phonemes, but in fact is articulated as a single phone. I could be mistaken, and would welcome a correction here.
However, pronouncing a voiced phone immediate after a voiceless one, especially when the voiced one is a sibilant (which are very prone to assimilation), is more than just awkard, it's downright impossible; not just in English, either! Almost every language that allows for such consonant clusters has an assimilation rule wherein either the sibilant is devoiced or the stop is voiced (almost always the former, for what it's worth). This is universal grammar talking. Alternation between allophones by way of a phonological rule is definitely not something that is so strong as something that seems almost certainly to be part of UG.
Well, Nat certainly has cooled off his work on the project, though I don't think "abandoned" is completely accurate. Check out Nat's dashboard blog, and you'll notice a few updates since this summer (when development was really cruising). Also, it seems as though some outside parties have begun picking up where Nat left off (e.g. here). My guess is that Nat just got overwhelmed by the whole Novell acquisition.
If by steal your .sig you mean not claim it as his own, pointing out that it was another's, then yes.
i owned y0all
There in fact is an open source effort to recreate it: here. I was just about to describe the complete lack of activity for the project, but, upon checking the last update for the website, it was only four days ago, so who knows. =)
I would be interested in finding out whether HP is planning on continuing to support OpenVMS; I know that Compaq had been planning to port it to the Itanium. Can anyone comment?
No they are trying to implement C#. Which will never happen.
Never happen, eh? Might I direct your attention to the Mono project, on which Ximian is currently working. They've had a self-hosting C# compiler for quite some time now running under Linux.
This is getting worse than journalling filesystems :-(.
Well, like it or not, that's more or less the sentiment after which this piece of versioning software is going.