Facebook is getting poisoned by its own code:
<div class="_2r6l accessible_elem" style="clip: rect(1px, 1px, 1px, 1px); height: 1px; left: 0px; overflow: hidden; position: absolute; top: 0px; white-space: nowrap; width: 1px;">
<div class="_1oxj uiLayer" style="left: 0px; outline: none; position: absolute; top: 0px; z-index: 200;">
<div class="_49v-" style="bottom: 0px; font-size: 0px; left: -29px; line-height: 0; position: absolute;">
<div class="_1oxk" data-reactroot="" height="52" style="background-image: none; background-position: initial initial; background-repeat: initial initial; border-bottom-left-radius: 0px; border-bottom-right-radius: 0px; border-top-left-radius: 0px; border-top-right-radius: 0px; box-shadow: none; padding: 5px 10px;">
I've programmed professionally and fairly well since the late seventies and if we had seen rubbish code like that, we would have it afire for the good of humanity. I have also been writing HTML (i.e. same language as above) since since 1995 but, baby, I can't read this.
Tip: no-one can. This is the kind of rubbish code which slows or kills computer systems and, witness Facebook, it hardly ever changes in any significant way. It's not likely that crap was written by a human but rather it probably came out of some type of compiler process; likely no human ever looked at it. Geez, what human would (larfs).
Here's an example of IBM Assembler:
L R14,0(,R1)
BR R14
The above example is concise and it's typically written by a sysfrog but not always and there is no significant compiler process to make it executable. The machine language generated by this code will be in the listing of the program and that's an immediate translation of those specific lines.
In the first example, the author has probably never even seen machine code.
Note: Google generates the same type of impossible almost unreadable code for Blogger and that may explain why it takes forever for them to fix a bug, just as it does with Facebook.
<div class="_2r6l accessible_elem" style="clip: rect(1px, 1px, 1px, 1px); height: 1px; left: 0px; overflow: hidden; position: absolute; top: 0px; white-space: nowrap; width: 1px;">
<div class="_1oxj uiLayer" style="left: 0px; outline: none; position: absolute; top: 0px; z-index: 200;">
<div class="_49v-" style="bottom: 0px; font-size: 0px; left: -29px; line-height: 0; position: absolute;">
<div class="_1oxk" data-reactroot="" height="52" style="background-image: none; background-position: initial initial; background-repeat: initial initial; border-bottom-left-radius: 0px; border-bottom-right-radius: 0px; border-top-left-radius: 0px; border-top-right-radius: 0px; box-shadow: none; padding: 5px 10px;">
I've programmed professionally and fairly well since the late seventies and if we had seen rubbish code like that, we would have it afire for the good of humanity. I have also been writing HTML (i.e. same language as above) since since 1995 but, baby, I can't read this.
Tip: no-one can. This is the kind of rubbish code which slows or kills computer systems and, witness Facebook, it hardly ever changes in any significant way. It's not likely that crap was written by a human but rather it probably came out of some type of compiler process; likely no human ever looked at it. Geez, what human would (larfs).
Here's an example of IBM Assembler:
L R14,0(,R1)
BR R14
The above example is concise and it's typically written by a sysfrog but not always and there is no significant compiler process to make it executable. The machine language generated by this code will be in the listing of the program and that's an immediate translation of those specific lines.
In the first example, the author has probably never even seen machine code.
Note: Google generates the same type of impossible almost unreadable code for Blogger and that may explain why it takes forever for them to fix a bug, just as it does with Facebook.
2 comments:
Comedy only another SYSPROG would understand... The punch line, of course, is that the Assembler example does, well, nothing! Ah, there's nothing like a good old fashioned BR14.
Hopefully R1 actually points at something! Why not go for maximum geek (larfs).
BR R14 is always great. Just go away, wherever, just somewhere else!
Post a Comment