Thursday, July 31, 2008
Livingness vs non-livingness
this article is motivated from my belief that the beauty of the livingness is not the fruit of only it's capability but also we have non-livingness which shares a great proportion in the credit for the evolution of livinenss. for this dicussion to be taken forward i just need to share what i think about these two independent terms. so what livingness is just a perpatual fight for one's existance ,it just continues to strive for being in the state in which its comfortable and enjoys its existance, however feelings,sentiments,individuality all are derived parameters which alltogether keep livingness in action and focussed to its motive. And what the non-livingness is just absence of all the parameters mentioned above. However being ignorant to the fact of its physical existance Non-livingness has always supported livingness for the actions of livingness to be exceuted and achieving the goals. If the whole planet were alive(i mean each and every entity, constituent of the system) then the livingness wudnt have been that beautiful as it is and as it feels to livingness at least.Reason behind this is so simple to understand that if all were alive they all have had some motives and obviosuly they would suffer from ill feelings i mentioned above and conflict of motives,methods of workings wud stand against the rise of its own.so it wont be an exaggeration to say that livingness depended much on non-livingness. and this dependency is proliferating day by day, one day surely gonna come when majorities of human(the main living entity responsible for structuring and hence assigning non livinness its work) actions will be executed by non-livingness while livingness will have to witness the power,the efficiency,the altrusim it possesses. this all should be very much apparent if you just observe your daily shedule and involvement of machines in that. but wait m not critisizing livingness, this was just to realize the power of non-livingness. by the facts(my observations very common in fact) drawn above i may be appearing to say that "by getting assisted by non-livingness livingness has lost its capability", but its not that.in fact it has enhanced it's capability with the help of blend of power of both.this is how i agree with the proposition (which i make here in this article) that non-livingness has the power, the power of efficiency,correctness,unbiasedness and immunity to pain and tiredness. someone may disagree and award the whole credit to only livingness by arguing that non-livingness was nothing without livingness's support who could assemble non living things to behave as a working unit otherwise it was an useless piece of physical structure. But this argument can be strongly opposed by the fact that livingness sees the usability in terms of its needs, so there is not any global reference to measure the usability. If livingness has given a shape, a structure to non-livingness then this is for it's own needs only.So its not only the liningness which should be given the whole credit but also non-livngess without which things were not be as beautiful as today.SO LIVINGNESS OWES MUCH TOO non-livingness.
Tuesday, July 15, 2008
What humanity means to me
humanity means....to first realise da fact that we are human beings (the only blessed living animal with consciousness and logical thinking )...humanity refres to the maximum use of these abilities in order to achive the ultimate goal(however goals are matter of individual interests and understandings of life) while hurting nobody and helping others as if we were doing it for ourself only.....
Monday, July 14, 2008
The truth of information hiding and encapsulation
As many people oftenly get confused in the jargon of these two closley interrelated terms(even me too ). Here i am jotting down what i could percieve about thses two gaints (ya they are!).
so at the very beginning i would like to tell you that there is not any ultimate defination (global agreement) of these terms. they have different meanings in different context. however i could clasify (in fact many experts also suggest the same thing) the two meanings in 1. Design perspective 2. Programming perspective
Design perspective:
lets first talk about the design principle.....feeling comfortable tll this point?!!
allright , one of the main motives of the design is to understand and control the complexity of the system (the problem). so we tend to redue the complexity by means of bunddling related things together.These bundles represnts a working unit(as elementry as possible) of the system. Now as these bundles are the actual c0nstructs of the system , so obviosuly they need to interact with each other(if they get enforced in a complete isolation then the system would become a simple wizzard in which there are discrete components , and no component knows about any other, each may perform its own job but it will be very difficult for others to take benifit of the job done, so not forming the system.). Now here we need to provide some mechanism by means of which one component may inetract with others so as to take benefits of the functioanlities in getting its own working done. Now this mechanism is called interafce. This interface will be the communication point of one bundle to another. so obviosly however a good design considers and tends to minimize these connections for achieving modularization. so this is all about encapsulation at design level. at this stage of design one can see the effect of change of one bundle on others, so one has to think in terms of protecting one part from the change (intented or accidental at the run time) of the other part..this introduces the great concept of information hiding. lets also have a glimpse of the dependency or interrelation of one to the other. Encapsulation itself is not an isolated concept , for example ..how to decide that which things are related and hence should be kept together in a spearate bundle (the encapsulated entity) , this problem gets solved by the concept of information hiding....it tells that, group only those elements together which correspond to a design decision to be hidden and prevent others by decreasing the connections to this group . so this shows the dependency of encapsulation on information hiding. information hiding also incorporates encapsulation , because by encapsulating we are hiding information from each other.
Programming perspective:
the fact that data and the methods to operate this data are shielded in a physical boundry(say a capsule and in object oriented programming language we call it an object) is called encapsulation.
however the concept of encapsulation at this level is to bring out the compartmentalization of the related things. this does not consider hiding something . at this point (As we havent introduced information hiding till now, by saying so i dont mean at all that these two things exist totally in isolation and dont even reject their concurrent existance, in fact they are oftenly concurrent as i discussed in the design perspective. so saying "at this point" i simply intend to comfortably illustrate the difference bw the two terms) there is not any comcern of hiding information objects (the capsule in the encapsulation analogy) from each other. Now programmer checks if there is some vital data(information) mishandling of which may cause dire(or even a little undesired too) consequences. so now he/she will tend to protect (by hiding from other part) that data by some mechanism (here comes access modifoers). And hence he by doing so successfully hidden the data from the outside world.
From the above discussion it would be clear that encapsulation doesnt guarantee information hiding (protection of data form accidental manipulation). A good object oriented programming incorporates both concepts in concurrent manner.
hope this was helpful to you...the article presented here is motivated by the perception made by the study of different articles found on the internet. this is an abstract of all thesis and lectures made by different experts..this doesnt reflect thinking of a single mind (just because thes two terms are too controversial...people still have much different opinions as i stated in the beggining)
this was a little effort , hope it helped...suggessions are invited loaded with queries
so at the very beginning i would like to tell you that there is not any ultimate defination (global agreement) of these terms. they have different meanings in different context. however i could clasify (in fact many experts also suggest the same thing) the two meanings in 1. Design perspective 2. Programming perspective
Design perspective:
lets first talk about the design principle.....feeling comfortable tll this point?!!
allright , one of the main motives of the design is to understand and control the complexity of the system (the problem). so we tend to redue the complexity by means of bunddling related things together.These bundles represnts a working unit(as elementry as possible) of the system. Now as these bundles are the actual c0nstructs of the system , so obviosuly they need to interact with each other(if they get enforced in a complete isolation then the system would become a simple wizzard in which there are discrete components , and no component knows about any other, each may perform its own job but it will be very difficult for others to take benifit of the job done, so not forming the system.). Now here we need to provide some mechanism by means of which one component may inetract with others so as to take benefits of the functioanlities in getting its own working done. Now this mechanism is called interafce. This interface will be the communication point of one bundle to another. so obviosly however a good design considers and tends to minimize these connections for achieving modularization. so this is all about encapsulation at design level. at this stage of design one can see the effect of change of one bundle on others, so one has to think in terms of protecting one part from the change (intented or accidental at the run time) of the other part..this introduces the great concept of information hiding. lets also have a glimpse of the dependency or interrelation of one to the other. Encapsulation itself is not an isolated concept , for example ..how to decide that which things are related and hence should be kept together in a spearate bundle (the encapsulated entity) , this problem gets solved by the concept of information hiding....it tells that, group only those elements together which correspond to a design decision to be hidden and prevent others by decreasing the connections to this group . so this shows the dependency of encapsulation on information hiding. information hiding also incorporates encapsulation , because by encapsulating we are hiding information from each other.
Programming perspective:
the fact that data and the methods to operate this data are shielded in a physical boundry(say a capsule and in object oriented programming language we call it an object) is called encapsulation.
however the concept of encapsulation at this level is to bring out the compartmentalization of the related things. this does not consider hiding something . at this point (As we havent introduced information hiding till now, by saying so i dont mean at all that these two things exist totally in isolation and dont even reject their concurrent existance, in fact they are oftenly concurrent as i discussed in the design perspective. so saying "at this point" i simply intend to comfortably illustrate the difference bw the two terms) there is not any comcern of hiding information objects (the capsule in the encapsulation analogy) from each other. Now programmer checks if there is some vital data(information) mishandling of which may cause dire(or even a little undesired too) consequences. so now he/she will tend to protect (by hiding from other part) that data by some mechanism (here comes access modifoers). And hence he by doing so successfully hidden the data from the outside world.
From the above discussion it would be clear that encapsulation doesnt guarantee information hiding (protection of data form accidental manipulation). A good object oriented programming incorporates both concepts in concurrent manner.
hope this was helpful to you...the article presented here is motivated by the perception made by the study of different articles found on the internet. this is an abstract of all thesis and lectures made by different experts..this doesnt reflect thinking of a single mind (just because thes two terms are too controversial...people still have much different opinions as i stated in the beggining)
this was a little effort , hope it helped...suggessions are invited loaded with queries
Sunday, July 13, 2008
Introduction
As this is an era of web2 . so obviously there are many sources of social networking. so what i feel is the blogs are not meant only for you to exist as a web entity but also for the source of global knowledge sharing...its neither a platform for one to project himself/herself nor a communication centre (as many bloggers use to do it)..it is an interface which allows us to share what we observe,what we perceive and wats the important we think we consider.....in short here we can strenthen our power of understandings, and ability to have the closest view of the truth which one doesnt have because his/her ability to obeserve something is confined within his/her way of percepting the things...so lets harness the power of blogs in making the hunger of knowledge more intensified .....
Subscribe to:
Posts (Atom)