Re: The responsive web site debate

jQuery is everywhere because it is a great "getting starting" JavaScript library that gets things done pretty easily. It is getting more heavy and I am thankful that I can pick and choose components to get just what I need. There is much that you can do without jQuery and it is getting easier with ES6 and ES7 as more stuff moves into the engine and is "standard". I expect that that is exactly what will happen with the mobile world: The browser will abstract away all the OS/device specific stuff and end up making the mobile world as easy as as the PC based world.

Imagine if today you had to write different HTML, CSS and JavaScript code for Mac, Windows and Linux to accommodate OS differences...it would be a nightmare and that is just where we are with mobile. Eventually I'm guessing some browser software version will handle cameras, accelerometers, storage and all the other device specific functionality from a single JS API (and I am guessing Chrome will get there first). Then as long as you run this "mobile" Chrome, you'll write it once and it will work across all devices. IMHO the current hybrid model Phonegap/Cordova and others will go away. "One API to rule them all"! That what all browsers will adopt.

Pete Helgren
www.petesworkshop.com
GIAC Secure Software Programmer-Java

On 7/14/2015 11:58 AM, Nathan Andelin 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.