If PHP Were British (2011)
aloneonahill.com
If PHP Were British (2011)
1–10 of 47 posts
Re: If PHP Were British (2011)
#2I assume the site is coded in PHP and that's why it's down ;) Text-only cache [1]
[1] http://webcache.googleusercontent.com/search?q=cache:imONA_3...
Re: If PHP Were British (2011)
#3Snort The idea of the super global £_BISCUIT instead of $_COOKIE - that made my morning.
Re: If PHP Were British (2011)
#4I would argue that there is a need for a proper British PHP compiler.
Re: If PHP Were British (2011)
#5I assume the site is coded in PHP and that's why it's down ;) Text-only cache [1] [1] http://webcache.googleusercontent.com/search?q=cache:imONA_3...
LOL this is great.
Re: If PHP Were British (2011)
#6I assume the site is coded in PHP and that's why it's down ;) Text-only cache [1] [1] http://webcache.googleusercontent.com/search?q=cache:imONA_3...
It must be, cause only PHP sites go down under heavy load/s
Re: If PHP Were British (2011)
#7I have to concede that I do prefer the longer abbreviations, especially nowadays when most editors have auto-completion, although of course there are limits. A healthy balance between (0) and (1). This also reminds me of those ridiculously long class names (2).
(0) my_structured_query_language_connect()
(1) SHFILEOPSTRUCTW [0]
(2) InternalFrameInternalFrameTitlePaneInternalFrameTitlePaneMaximizeButtonPainter [1]
[1] https://www.pushing-pixels.org/2007/11/07/and-the-longest-jr...
Re: If PHP Were British (2011)
#8I assume the site is coded in PHP and that's why it's down ;) Text-only cache [1] [1] http://webcache.googleusercontent.com/search?q=cache:imONA_3...
Full-content cache:
https://ipfs.eternum.io/ipfs/Qmf8bKiaDquBaspP1krKVMGnorby38h...
Re: If PHP Were British (2011)
#9I have to concede that I do prefer the longer abbreviations, especially nowadays when most editors have auto-completion, although of course there are limits. A healthy balance between (0) and (1). This also reminds me of those ridiculously long class names (2). (0) my_structured_query_language_connect() (1) SHFILEOPSTRUCTW [0] (2) InternalFrameInternalFrameTitlePaneInternalFrameTitlePaneMaximizeButtonPainter [1] [0]…
This is part of the code-as-docs ethos which has really changed how I write everything. I try to make my code as intuitive as possible to obviate comments and documentation that only explain what the code is doing. You could also call it code-as-prose.
This is impeded when languages have popular modules with names that are absolutely unintuitive, like the Python "requests" module. Requests what? Oh, HTTP? Then it should have been called http_requests. And the module that one uses, urllib3, is actually an HTTP library, not a generic URL library (URLs can be any web request, such as ftp, mailto, jdbc, etc).
Re: If PHP Were British (2011)
#10Snort The idea of the super global £_BISCUIT instead of $_COOKIE - that made my morning.
My favourite was ““replacement of "include()" with something like "i_might_be_partial_to()", ””