Re: The responsive web site debate

How do you test your code?

There are a number of ways:
- http://mochajs.org/ for unit testing of Javascript both client and
server-side.
- http://www.seleniumhq.org for user experience type testing
- etc.

Anything more than that may be an indication that your client-side code is

overly scoped, IMHO.

By "overly scoped" do you mean "too much code within the client"? The
primary discomfort I have with a lot of Javascript code on the client is
then users (or more pointedly: hackers) know much more about your
application infrastructure. Not saying "security by obscurity" is a good
fortress. Other than that I don't have issue with a thicker client.



Aaron Bartell

On Tue, Jul 14, 2015 at 11:58 AM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

That's where todomvc.com comes into play ...

Consolidates a lot resources pertaining to JavaScript frameworks, including
external references under one umbrella, nice!

One thing that stuck me was the number of inter-dependencies which exist
between the various offerings. Seems like JQuery is everywhere. Additional
other frameworks are common.

The large number of implementations and adaptations of
model-view-controller-whatever design patterns is another point. These may
be indications that folks are overly-scoping the client side of the
project, IMHO.

What should browsers do? Display page content and respond to UI events. How
do you test your code? Mouse, keyboard, and similar interactions. Anything
more than that may be an indication that your client-side code is overly
scoped, IMHO.

I also see some advantages of caching HTML templates on the client and
merging them with JSON data during the runtime. Perhaps that's one thing
that should be moved to the client.

These are just my opinions. I don't expect to have much influence in the
broad scheme of things.
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.