[unemployed] job postings [IHBT]

-3+ years with HTML
5+ years experience hand-coding HTML and CSS

The number of times I see this is frankly shocking. It is extremely disappointing to lose all interest in a job because you realize whoever wrote the posting has no idea what programming is. I have also seen requirements for experience listing whatever new framework or API that will supposedly solve everyone's problems--mostly with JQuery, MooTools, CakePHP, etc.-- and an impossible amount of time using said API, meaning I had to have been using the API before it existed.

Master in Computer Science Obviously no degree was required for whoever in this company wrote the job posting.

Proficient with Visual Studio 2005 and higher.
I am proficient with all text editors. I still don't know what this means, and since I'll never ever pay for a Microsoft certification, I may never know.

o C# and/or VB.Net
these two things are interchangeable so easily?

You will leverage your knowledge of JEE-based web architecture and related technologies including Java, J2EE, Spring, AJAX, and GUI Expereince relational database connections.

I have seen Chinese electronics dealer websites with more comprehensible English.

Go ahead, even if you're fortunate and have a job right now, venture into your local craigslist.org/sof/ or other job website do foreigners have job websites? and check out the postings for your development specialty.

>>34
Ideally, that's the hardest part. Practically, drivers are even worse.
But yes, glueing everything together in a non-Unixy manner is hard.

The only viable option for a system-wise GC is generational GC, with a kernel private heap, an interprocess heap (whose access are ensured to be atomic operations), a per-process big heap (again, atomic access), and per-thread small heap, with kernel heap and small heaps guaranteed to not get swapped (thus killing the performance).
I'm not sure about copying vs mark-and-sweep. Allocation and collection in a copying GC are faster, but it becomes worse when you start allocating too much memory, since you always need two times the space you need. This may make harder to not swap the small heaps.
Mark-and-sweep is slower, but has a better memory usage.
A solution could be using a copying GC on the big heaps, and mark-and-sweep on the small heaps.