closure cascading
cascading is the most popular way of javascript coding.it mentioned in javascript good parts. they call it looks like cascade such as chain of method.
"abc".split('').map(xxx).join()
benefits are
-you can make sure context of process according to dot bindings
-narrow down choices according to its own members(method, variable etc)
Raphaël(2008) is one of the good examples according to its "method cascading" style coding.recent good example is D3.js you can keep data objects and binding using dots.
When you create something it related with library or SDKs which has something new approach such as JQuery or D3 like, you have question from others or yourself such as "Is it just syntax sugar or new grammar or approach?"
some age past only providing syntax sugar but eventually all of them are repelled.
the idea of this is due to some disadvantage of method cascading, such as
- coding can not change dynamically, almost coding will be static data design
- difficult to give some effect into other objects or data context
the simple concept is "pipes on GUI".but not yahoo pipes or node red like. visual image is "BLOCK THE CLOCK" by IDEAL.
against further situation which we are going to face , quantum , genome or other huge data processing which over the assumption big data or deep learning. these have huge order of data and connection as we expect.
Ideally which has various context and control time and space such as multiverse or time leaping. and process is still liner that we only understand visually well.
so far , closure might be better choice in the circumstance.
(function(){
var f=function(){
return f;
}
return f;
})(0)(1)(2)(3)(4)(5);
These mala of arguments, we call "Closure cascading", these bunch of calls never ends like uroboros. we call this type "dragon" which has head argument which represents context data if you make sure context
(function(context){
var f=function(){
return f;
}
return f;
})({})(1)(2)(3)(4)(5);
big difference from method cascading is you don't worry about data types of context and rest of relation of argument data type or grammers. you can give abstract of relation with context and other arguments you can call object , function or oder data types.
"abc".split('').map(xxx).join()
benefits are
-you can make sure context of process according to dot bindings
-narrow down choices according to its own members(method, variable etc)
Raphaël(2008) is one of the good examples according to its "method cascading" style coding.recent good example is D3.js you can keep data objects and binding using dots.
When you create something it related with library or SDKs which has something new approach such as JQuery or D3 like, you have question from others or yourself such as "Is it just syntax sugar or new grammar or approach?"
some age past only providing syntax sugar but eventually all of them are repelled.
the idea of this is due to some disadvantage of method cascading, such as
- coding can not change dynamically, almost coding will be static data design
- difficult to give some effect into other objects or data context
the simple concept is "pipes on GUI".but not yahoo pipes or node red like. visual image is "BLOCK THE CLOCK" by IDEAL.
against further situation which we are going to face , quantum , genome or other huge data processing which over the assumption big data or deep learning. these have huge order of data and connection as we expect.
Ideally which has various context and control time and space such as multiverse or time leaping. and process is still liner that we only understand visually well.
so far , closure might be better choice in the circumstance.
(function(){
var f=function(){
return f;
}
return f;
})(0)(1)(2)(3)(4)(5);
These mala of arguments, we call "Closure cascading", these bunch of calls never ends like uroboros. we call this type "dragon" which has head argument which represents context data if you make sure context
(function(context){
var f=function(){
return f;
}
return f;
})({})(1)(2)(3)(4)(5);
big difference from method cascading is you don't worry about data types of context and rest of relation of argument data type or grammers. you can give abstract of relation with context and other arguments you can call object , function or oder data types.
コメント
コメントを投稿