How do you know jyte didn't break itself?
Jyte isn't suicidal.
Web applications (with their associated hardware configurations) aren't perfect. Normal use, or unusual loading, can expose design or programming issues. That wouldn't be the fault of some specific user.
For instance, before I tried to write some PHP I didn't know that the interpreter could trigger an HCF instruction
Did some wonky Ruby code cause the jyte server to burn down?
I think we claimed it to death.
Enter an OpenID to invite a Jyter to this claim, or an email address to invite someone new to Jyte.
Discussion (6)
How do you know jyte didn't break itself?
Jyte isn't suicidal.
Claims inspired by this comment
Jyte isn't suicidal.Web applications (with their associated hardware configurations) aren't perfect. Normal use, or unusual loading, can expose design or programming issues. That wouldn't be the fault of some specific user.
For instance, before I tried to write some PHP I didn't know that the interpreter could trigger an HCF instruction
Did some wonky Ruby code cause the jyte server to burn down?
I think we claimed it to death.