From: Kevin Carhart <kevin@carhart.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [edbrowse-dev] ugliest code ever
Date: Mon, 9 Sep 2019 17:29:13 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.1909091721450.87884@phoenix> (raw)
In-Reply-To: <20190809061628.eklhad@comcast.net>
Wow, that's appalling. Amazon had a file where the JS keywords themselves
were carved into pieces like ['getE','leme','split','ntsBy']. The
substrings of the keywords did not necessarily occur together. And then
the code itself would use those strings as a call.
(array[43]+array[97])(blah). I don't like to think about it..
On Mon, 9 Sep 2019, Karl Dahlke wrote:
> You thought minimized javascript looked like dog vomit - well imagine this.
> Minimize the code, then reexpand it using long awkward and pointless variable names.
> This is the section I'm trying to debug.
>
> for (var _0x9247e4 = 0, _0x3893d3 = _0x525f46['length']; _0x9247e4 < _0x3893d3; _0x9247e4++) {trace@(a45)
> var _0x39f51f = _0x525f46[_0x9247e4];
> _0x42817f += '; ' + _0x39f51f;
> trace@(a46)var _0x3ec78e = _0x525f46[_0x39f51f];
> _0x525f46['push'](_0x3ec78e);
> _0x3893d3 = _0x525f46['length'];
> if (_0x3ec78e !== !![]) {trace@(a47)
> _0x42817f += '=' + _0x3ec78e;
> }
> }
>
> Karl Dahlke
>
prev parent reply other threads:[~2019-09-10 0:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 10:16 Karl Dahlke
2019-09-10 0:29 ` Kevin Carhart [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.21.1909091721450.87884@phoenix \
--to=kevin@carhart.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).