From: Kevin Carhart <kevin@carhart.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] NASA is so weird we may never understand it
Date: Sat, 17 Mar 2018 23:43:26 -0700 (PDT) [thread overview]
Message-ID: <alpine.LRH.2.03.1803172307530.4839@carhart.net> (raw)
In-Reply-To: <20180216112600.eklhad@comcast.net>
> Such an alert is placed before each var, since those are the only syntactically safe places to do so.
> I couldn't find any other place that is safe.
> So only about 9% of lines havve markers, but it's something.
Interesting, good stuff. About "syntactically safe", weren't
you saying that anything could be put anywhere, if you use || and commas
rather than semicolons in order to inject logging, etc? I am interested
to know how come this is different?
About nasa, I think to some extent the components are downloadable on
their own, so we could test them in a vacuum if we want to do that. I've
done it a little with a jquery using a tiny test.html like
<HTML>
<SCRIPT SRC="jquery.js">
</SCRIPT>
some text
</HTML>
I just point edbrowse at test.html and find out what happens in a vacuum
before trying it in combination. It might also be
possible with ember, which has a site at emberjs.com. The other majors
that I know of are bootstrap, mootools
(used by fastmail), possibly rails which I think the xqsuperschools
website uses. There are some, but not that many. jquery has some
other projects like Sizzle which is CSS-related, and jqueryUI which people
appear to be including quite a bit.
It's a little helpful up to a point to know this. The insane overloading
is still a problem, but there are fewer of these large popular frameworks
than we may think so it will go far when we do get one.
thank you for the research, I am sure a lot of blood sweat and tears went
in to going that deep into vendor.js.
Kevin
prev parent reply other threads:[~2018-03-18 6:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 15:26 Karl Dahlke
2018-03-18 6:43 ` 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.LRH.2.03.1803172307530.4839@carhart.net \
--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).