|
You are here |
linksort.com | ||
| | | | |
www.joeshaw.org
|
|
| | | | | A scheme for consistent and safe HTTP API errors | |
| | | | |
blog.carlana.net
|
|
| | | | | The other day, I was reading a website about some historical documents, when I saw that it had an error message on top: Screenshot from the site Some quick searching online for the error message revealed that it was caused by a mismatch between the site's versions of PHP and WordPress. Older versions of WordPress had a bug in the switch statement of a certain localization component, and later versions of PHP dump a warning about this bug out to the end user HTML. When I came back to the site a few days later, it had been fixed. The ultimate reason for my seeing for the error message as a random reader is that PHP has too many ways to deal with errors: Builtin PHP functions, and therefore any PHP project, have a whole range of error handling mechanisms - erro... | |
| | | | |
alnvdl.github.io
|
|
| | | | | A bit of history, a bit of atonement, a bit of shameless self-promotion. | |
| | | | |
www.integralist.co.uk
|
|
| | | I've been learning Rust recently. This will probably be my third (lazy) attempt to learn the language. The reason I've failed previously is simply because I had no reason to learn it. Other than the memory safety aspects, which I like a lot, I don't actually like the design of the language at all (but that's a conversation for another day). This time around I want to learn the language as it's pertinent to my job. | ||