Glad you got the issue resolved though and didn't fork over the $10 because you would've just run into the same issue in the future if you didn't get to the root cause of it (misconfigured Apache).
138 karma · joined January 20, 2015
Glad you got the issue resolved though and didn't fork over the $10 because you would've just run into the same issue in the future if you didn't get to the root cause of it (misconfigured Apache).
They will work through your issue no matter what until a resolution is reached.
If the company has pidgeon holed themselves into the situation, they clearly have the 2 options you stated, and that should not reflect poorly on the original author.
Sorry that is extremely far from the truth. Any of the other major ISPs' would leap at the chance to guzzle up these customers if there was no other competition.
Seriously? Developers need to stop sprouting this crap as an install method. Nobody in their sane mine should curl a script into bash to install a product.
The prize money shouldn't be the incentive for these solutions, more of a by-product.
Your converse golden rule suffers the same problems as the golden rule - everyone should be treated individually, treating others the same as you expect people to treat you will not always work out as intended.
As you said, if a server catches fire, the newbie sysadmin will freak out and start running around in circles screaming. The experienced sysadmin has seen it 10x before and knows its not a big issue - removes, extinguishes and replaces it.
Edit: he commented below saying it was IE11 with the IE9 emulation enabled.