"...one must check whether one has PHP 5.2 (or newer) installed upon their Internet server..."
Should this not be 'one's Internet server'?
"Something our primitive stateside friends can understand"
What is this 'stateside' you speak of, Sir? Our Colonial Cousins may also resent the adjective that has been applied.
I personally rather regret the automatic recitation of Arne's ditty when visiting the page.
PS: 'Spiffing' is later and the Jeeves references in the HTML markup point to 1920s. Biggles. Biplanes.
Possibly the first time I have appreciated auto-play music on a site, made me laugh. And now it's put me into a baroque mood which is always a good thing.
'colour' => 'color',
'grey' => 'gray',
'!please' => '!important',
'transparency' => 'opacity',
'centre' => 'center',
'plump' => 'bold',
'photograph' => 'image',
'capitalise' => 'capitalize'
: Taken from https://github.com/idiot/Spiffing/blob/master/spiffing.php (aside, please don't use this project as a good example of PHP code style).
Reminded me of INTERCAL:
INTERCAL has [..] modifiers such as "PLEASE". This last keyword provides two reasons for the program's rejection by the compiler: if "PLEASE" does not appear often enough, the program is considered insufficiently polite, and the error message says this; if too often, the program could be rejected as excessively polite.
In Illustrator, for example, the interface has an opacity setting but the help file refers to it as setting the transparency since that is essentially what you're doing when you lower the opacity. (Personally, I prefer the word transparency, it just seems clearer to me.)
I cannot decide to up vote or down vote your comment based solely upon this statement. Therefore, take my lack of voting as a positive affirmation that I have no strong feelings one way or the other.
I was listening to some music in the background with multiple tabs open, and I didn't expect a project link from HN to autoplay music. Confusion ensues.
Wouldn't mind a few more substitutions in the language, but it seems like most of the work went into making a really nice landing page. Great job there! (Autoplay music forgivable on a joke at least)
I feel I'm missing something with this example.
And as you say, "transparency: 0.2;" would equal "opacity: 0.8;"
background: #000 url(pic.png) no-repeat;
So having background-repeat: none; would conflict with background/background-image: none;
Oh well, toodle-pip.
Or how about UsingCamelCase? Give than some languages don't have the concept of UPPER/lower case.
Does Go require you to use "er" for interfaces as in Writer, Reader, Serializer? That seems even worse given that it not just roman letters only it's English only. I don't know other languages but I suspect the suffix 'er' has no meaning in Spanish, Italian, French, and that being forced to added it to classes written using those languages would really suck.
type Escribirer interface // !?!?
Isn't that kind of disingenuous? Everything may use the American English character set and dialect, but they're called programming languages for a reason. I don't consider my work to be in English, I consider it Objective-C or Java. In this way, they have their own subdialects anyway.
Spelling in documentation is much less important.
"transparency: 1" != "opacity: 1"
We use transparency in the US. Transparency is how much light passes through an object and Opacity is how much it blocks.
"transparency: 1" == "opacity: 0"
"transparency: 0.5" == "opacity: 0.5"
Because it should.