Pete,

I was actually going to use the cycle as a comparison too. In my case, I
actually loved the cycle when it fit. This was years ago when I did a lot
of report programming.

I never "forced" the cycle into an application, but for some applications
requiring level break processing, since I understood it, it was a no
brainer to use it. :)

With the asyc "features" of JS, you find out about it pretty quickly when
your app doesn't work, you search for a reason why, and hit a huge thread
on stackoverflow about it that's been there for years.

These new features are sort of how they removed/deprecated async:false in
AJAX calls since it was an oxymoron and are requesting SJAX instead (maybe
already available in jQuery).

Brad
www.bvstools.com

PS.. let's not get off topic to the cycle now... I apologize ahead of time!
lol

On Wed, Sep 14, 2016 at 5:21 PM, Pete Helgren <pete@xxxxxxxxxx> wrote:

There was a time very early in my RPG programming days where I used the
RPG cycle but had absolutely no idea how it worked or why it was there. I
just followed the "pattern". Someone finally sat down with me and talked
me through it. It was like "Wow! So THAT is why it is written that way"
Made me a better (more informed) programmer.

That is what happened as I viewed the video. There are some "side
effects" in my JavaScript scripting that I didn't completely understand and
now I have a better grasp. The best part was that it wasn't "propeller
head" stuff. Simple examples. Simple concepts. I am not sure how anybody
in the web world can avoid using JavaScript and if you are script with JS,
the video is illuminating IMHO.

Pete Helgren
www.petesworkshop.com
GIAC Secure Software Programmer-Java
LinkedIn - www.linkedin.com/in/petehelgren
Twitter - Sys_i_Geek IBM_i_Geek


This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].