jQuery is Dead - Long Live JavaScript!
jQuery is Dead - Long Live JavaScript! It might come as a surprise to you - especially if you are recently learning to use script with QuickBase - but jQuery is considered dead by many developers a...
Forum Discussion
lol or just period dont use jquery there is no need, Jquery is a waste of time......
Wolf: little developer let me in.
Me: not through the parser in my little dom tree.
Wolf: well i'll huff and i'll puff and inject an unexpected token,
Me: you can try hard as you might but i have have immunity and improved functionality over your antiquated ways, disappear now and allow W3C/ECMA to pave the way.
A) Use fetch or xhttp - preference on fetch, while i know Dan has identified what some may perceive a few draw backs, i personally dont mind that i need handle a a bit more "annnndddd theeennnn" see below.
.
B) native promises are far superior to any jquery/bluebird/early days polyfill approach, check out async functions for the mother of all promise chaining, get your nice anndddd theeennnnn chain underway.
C) Dont touch frameworks, there a waste of time. Library extensions are ok but likely better to identify the functions you actually require, take inspiration then rewrite what you need into your generator function.
D) Learn to build Generators, love them, adore them, improve them and keep them vanilla JS to saver them for life.
Wolf: little developer let me in.
Me: not through the parser in my little dom tree.
Wolf: well i'll huff and i'll puff and inject an unexpected token,
Me: you can try hard as you might but i have have immunity and improved functionality over your antiquated ways, disappear now and allow W3C/ECMA to pave the way.
A) Use fetch or xhttp - preference on fetch, while i know Dan has identified what some may perceive a few draw backs, i personally dont mind that i need handle a a bit more "annnndddd theeennnn" see below.
.
B) native promises are far superior to any jquery/bluebird/early days polyfill approach, check out async functions for the mother of all promise chaining, get your nice anndddd theeennnnn chain underway.
C) Dont touch frameworks, there a waste of time. Library extensions are ok but likely better to identify the functions you actually require, take inspiration then rewrite what you need into your generator function.
D) Learn to build Generators, love them, adore them, improve them and keep them vanilla JS to saver them for life.
- great source dan, for everyone else, ES2017 introduced Async Await which i use in my generators - yield to the power of the force - enough said haha: https://medium.com/front-end-hacking/modern-javascript-and-asynchronous-programming-generators-yield...
- That's what I love about these "no code" platforms - you get to use a lot of advanced coding features to solve problems.
ES2019 is going to give us dynamic import (already in Chrome):
http://2ality.com/2018/02/ecmascript-2019.html#candidate-features-stage-3 - Hadn't read about that yet! going to give it a good go through now cheers. I'm at the point where the benefits of low code are undone by the inflexibility of me introducing my own themes/bootstrap (not hacked in), lack of on premises hosting and flexibility etc etc, I'm well underway on building my own CRUD on Nodejs mapped to MS SQL with PHP front end with Bootstrap for one of the apps we use QB for as longer term reliance without the things i mentioned above means we cant set and forget with support handed over to our infra team. _
