'Some are born great, some achieve greatness and some have greatness thrust upon em'
PREM....LOVE AS MUCH AS U CAN ……… i just want to live upto my name and wish to inspire others in any manner.. i'm just like any ordinary person with dreams and aspirations in my eyes and an urge to accomplish something in life for which i may b remembered forever.
The basic premise of Ladder Theory is that all men gauge women on an I-would-have-sex-with-this woman/how-likely-is-she-to-have-sex-with-me scale.
Women apparently have two ladders:
Potential sexual partners, and
Platonic partners - those she would never have sex with.
Given that women are arguably a lot more more complex than men, then that figures..
Classification and ranking (for both sexes) is described as a 'Ladder' hence the name Ladder Theory.
Allegedly, the higher up on someone's ladder you are the more likely you are to get laid.
The following (basic) table sets out how men and women apparently make their initial mental assessment of each other.
ladder theory male/female assessment factors
men
%
women
%
How attractive is she
60
How much money/power does he have
50
How soon she will have sex with me
30
How attractive is he*
40
Other aspects
10
How much women say and don't mean (e.g., I prefer a man with a sense of humour, a sensitive man, etc)
10
* Attractive (40%) to women is broken down as follows:
50% - Physical Attraction
20% - Competition (is he someone else's, does he ignore me, I-want-what-I-can't-have, etc..)
20% - Novelty (women it appears lay some kudos on men being 'novel')
10% - Other (we can only guess..)
men's ladders
Based on the above, a man will place a woman highest on his ladder if (he judges) she is willing to have sex with him and he finds her attractive.
It could be said that most men and women would not find that statement ground-breaking.
Men apparently classify women as follows:
Top - (of course) is the woman he really/most fancies.
Next - the women who he would have sex with and admit to.
Last - those women he would have sex with but never admit to it (or be too drunk to remember who she was). Too much alcohol can as we know make even the most unattractive woman (and man) appear desirable.
As an aside it should be remembered that beauty is subjective, and (often) superficial, especially when applied to women (although some men also prefer not to be to seen without their make-up or other physical enhancements).
Men, as stated in the Ladder Theory, do not have a ladder for 'Platonic' females since the theory works on the premise that all men basically evaluate women as sexual objects.
women's ladders
Women as stated earlier have two ladders - Potential Sexual Partners and Platonic Partners.
The first problem here for men is that they often don't know which ladder they are on.
When they do get it wrong they can come to an 'abysmal' end.
Women place Money/Power as a man's most attractive aspect.
This is borne out by how many 'not very attractive' powerful rich men have beautiful women companions. (If the cap fits..)
Do not stand at my grave and weep, I am not there, I do not sleep.
I am a thousand winds that blow. I am the diamond glint on snow. I am the sunlight on ripened grain. I am the gentle autumn rain.
When you wake in the morning hush, I am the swift, uplifting rush Of quiet birds in circling flight. I am the soft starlight at night.
Do not stand at my grave and weep. I am not there, I do not sleep. Do not stand at my grave and cry. I am not there, I did not die!
Do not stand at my grave and weep. I am not there, I do not sleep.
I am the song that will never end. I am the love of family and friend. I am the child who has come to rest In the arms of the Father who knows him best.
When you see the sunset fair, I am the scented evening air. I am the joy of a task well done. I am the glow of the setting sun.
Do not stand at my grave and weep. I am not there, I do not sleep. Do not stand at my grave and cry. I am not there, I did not die!
Java 1.6 was released to overcome a few shortcomings and provide enhanced features when compared to Java 1.5
Details of 1.6 are mentioned below.
Advantages to running applications on Java SE 6 Applications run faster on the desktop and servers New 'Dynamic Attach' diagnostics simplify troubleshooting Expanded Solaris DTrace support provides additional value on Solaris Improved 'native' look and feel across Solaris, Linux, and Windows First Java platform with full support for Windows Vista Benefits in upgrading developer environments to Sun's Java SE 6 JavaScript integrated and included with the platform Scripting languages framework extends support for Ruby, Python, and other languages Complete light-weight platform for web services, right out of the box Simplified GUI design and expanded native platform support Full JDBC4 implementation providing improved XML support for Databases Java DB included with the JDK, a free to use and deploy Java Database Full support by NetBeans IDE 5.5 Sun Developer Services available to help build more robust applications Improved User Experience
Look-and-feel updates to better match underlying operating system Improved desktop performance and integration Enhanced internationalization support Improved performance Upwards binary compatibility
Security Features and Enhancements
Native platform Security (GSS/Kerberos) integration. Java Authentication and Authorization Service (JAAS) login module that employs LDAP authentication New Smart Card I/O API Native security services technical article » Find out more
Integrated Web Services
New API for XML digital signature services for secure web services New Client and Core Java Architecture for XML-Web Services (JAX-WS) 2.0 APIs New support for Java Architecture for XML Binding (JAXB) 2.0 XML home page » Find out more
Scripting Language Support (JSR 223)
New framework and API for scripting languages Mozilla Rhino engine for JavaScript built into the platform Scripting for the Java Platform technical article » Find out more
Enhanced Management and Serviceability
Improved JMX Monitoring API Runtime Support for dTrace (Solaris 10 and future Solaris OS releases only) Improved memory usage analysis and leak detection Monitoring and Management technical article
Increased Developer Productivity
JDBC 4.0 support (JSR 221) Significant library improvements Improvements to the Java Platform Debug Architecture (JPDA) & JVM Tool Interface
Collections Framework Enhancements
This page summarizes enhancements to the collections framework in Java SE 6. This release saw fewer API changes than 5.0, but there was more of a focus on the accuracy and clarity of the specification. We recommend using the Java SE 6 specification even when writing programs for older releases. The primary theme of the API changes was better bi-directional collection access. These new collection interfaces are provided: • Deque - a double ended queue, supporting element insertion and removal at both ends. Extends the Queue interface. • BlockingDeque - a Deque with operations that wait for the deque to become non-empty when retrieving an element, and wait for space to become available in the deque when storing an element. Extends both the Deque andBlockingQueue interfaces. (This interface is part of java.util.concurrent.) • NavigableSet - a SortedSet extended with navigation methods reporting closest matches for given search targets. A NavigableSet may be accessed and traversed in either ascending or descending order. This interface is intended to supersede the SortedSet interface. • NavigableMap - a SortedMap extended with navigation methods returning the closest matches for given search targets. A NavigableMap may be accessed and traversed in either ascending or descending key order. This interface is intended to supersede the SortedMap interface. • ConcurrentNavigableMap - a ConcurrentMap that is also a NavigableMap. (This interface is part of java.util.concurrent.) The following concrete implementation classes have been added: • ArrayDeque - efficient resizable-array implementation of the Deque interface. • ConcurrentSkipListSet - concurrent scalable skip list implementation of the NavigableSet interface. • ConcurrentSkipListMap - concurrent scalable skip list implementation of the ConcurrentNavigableMap interface. • LinkedBlockingDeque - concurrent scalable optionally bounded FIFO blocking deque backed by linked nodes. • AbstractMap.SimpleEntry - simple mutable implementation of Map.Entry • AbstractMap.SimpleImmutableEntry - simple immutable implementation of Map.Entry These existing classes have been retrofitted to implement new interfaces: • LinkedList - retrofitted to implement the Deque interface. • TreeSet - retrofitted to implement the NavigableSet interface. • TreeMap - retrofitted to implement the NavigableMap interface. Two new methods were added to the Collections utility class: • newSetFromMap(Map) - creates a general purpose Set implementation from a general purpose Map implementation. There is no IdentityHashSet class, but instead, just use Set
