Well, it depends  on which one you use the most I guess… But some people obviously don’t think so. After using a particular language and only that language for a really long time it becomes a second nature to use constructs from that language. So when we switch to another, even if basically very similar language, we still type wrong constructs by inertia.

I have that problem with VB.NET – while helping my wife with her ASP.NET project I had to use VB.NET but I would constantly start typing in C#. Last time I used VB-like language was in the days of Microsoft Access 2.0, circa 1996 – and I only used a VBA derivative then.

Then the other day I needed to write a hex constant and I didn’t know how to do that. While searching the Internet, I ran into a post where a guy had exactly the reverse problem – he was trying to read C# code and couldn’t figure out the way hex constants were written.

He said how the problem was that (I paraphrase) there is a problem with the hex constants in C# because they are not written in a natural way like in VB.NET.

It didn’t occur to him that natural is different for developers who primarily use other languages

P.S. C# and C++ (probably Java too) use 0x2F, while VB.NET uses &H2F to denote a hex constant 2F. So, C# – prefix with 0x, VB.NET – prefix with &H.