edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] js befuddle
Date: Tue, 15 Apr 2014 10:37:11 +0000	[thread overview]
Message-ID: <20140315103711.eklhad@comcast.net> (raw)

As I move forward with javascript, as time permits,
I just have to comment, or vent, at least once, on the state of js.
Not the language, that's fine, but the way people write it.
I'm convinced there is a program out there somewhere that is
called js_befuddle(), that strips the whitespace and comments
out of any js program, and changes the variables to meaningless
single letters.
It can't be coincidence; I've seen too much javascript code written like that.
My router for instance, has a js file that is 10K,
all on one line, no whitespace, no comments, and cryptic variables.
10K of what looks like line noise.

But it's worse than that.
Most of these programs hide operations in functions
when they don't need to, and even prototype on top of existing methods,
so that the standard string and array methods don't do
what you expect them to do.
Imagine if s.split(',') does something completely different than you expect.
It's worse than reading assembly language!

I guess they are thinking along these lines:
"My js code has to be public, I can't hide it,
I have to release the source, and I'm paranoid, so I'm going to make
it confusing and convoluted and impossible to understand."

Gee, thanks alot.

Most people would never know or care,
but if I want to know why edbrowse doesn't work on a site,
I have to trudge through all this shit to figure it out.
My goal then is to find some real world sites where edbrowse doesn't work,
and where the js is simple, short, and comprehensible;
and then hope those problems are representative of the shortfalls
of edbrowse js in general.
Jesus, Mary, Joseph, and all the saints!

Karl Dahlke

             reply	other threads:[~2014-04-15 14:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-15 10:37 Karl Dahlke [this message]
2014-04-15 15:18 ` Chris Brannon

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=20140315103711.eklhad@comcast.net \
    --to=eklhad@comcast.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).