Collective Interview Question Software Engineer / Developers
Country: India
Interview Type: In-Person
is a comprehensive book on getting a job at a top tech company, while focuses on dev interviews and does this for PMs.
CareerCup's interview videos give you a real-life look at technical interviews. In these unscripted videos, watch how other candidates handle tough questions and how the interviewer thinks about their performance.
Most engineers make critical mistakes on their resumes -- we can fix your resume with our custom resume review service. And, we use fellow engineers as our resume reviewers, so you can be sure that we "get" what you're saying.
Our Mock Interviews will be conducted "in character" just like a real interview, and can focus on whatever topics you want. All our interviewers have worked for Microsoft, Google or Amazon, you know you'll get a true-to-life experience.
Hashtable and HashMap both are hash based collection and works on principle of hashing.
- Srigopal Chitrapu April 29, 2014Hashtable and HashMap both provide constant time performance for put and get method if objects are distributed uniformly across bucket.
1. Hashtable is synchronized, whereas HashMap is not.
This makes HashMap better for non-threaded applications, as unsynchronized Objects typically perform better than synchronized ones.
2. Hashtable does not allow null keys or values. HashMap allows one null key and any number of null values.
3. One of HashMap's subclasses is LinkedHashMap, so in the event that you'd want predictable iteration order (which is insertion order by default), you could easily swap out the HashMap for a LinkedHashMap. This wouldn't be as easy if you were using Hashtable.
4. If synchronization is not an issue, we can recommend HashMap. If synchronization becomes an issue, we may also look at ConcurrentHashMap.
5. Performance: Since HashMap is not synchronized it perform better than Hashtable.
6. In hashmap you can remove element while iterating, safely. where as it is not possible in hashtables.
7. If i am not wrong, Hashtable is obsolete class and you should be using ConcurrentHashMap in place of Hashtable in Java.
There is a nice discussion going on in StackOverflow, might helpful for others.
stackoverflow.com/questions/40471/differences-between-hashmap-and-hashtable
Since there is no HashMap in C#.
Dictionary is probably the closest, but not exact, (one e.g. it wont accept null key values.)
System.Collections.Generic.Dictionary implements the System.Collections.Generic.IDictionary interface.
Refer the below thread for more info.
stackoverflow.com/questions/1273139/c-sharp-java-hashmap-equivalent