So I think we can safely assume that the number of current open Delphi positions, that are publicly posted is somewhere between 4 and 1000. This will no doubt illustrate the uncertainty principle in action. The more we enumerate Delphi job openings, we will have a direct result on the number of Delphi job openings, both by helping developers to find and apply for positions as well as create more awareness that there are Delphi developers looking for work.

So, in order to “fix” an, obviously too short list from DavidI, you post an, obviously, too long list?

Not the mention the sheer number of those that are somehow Delphi related that are for things such as “Retooling rich client functionality from Delphi and VB 6 to a .NET (C#) rich client”…

Not that it matters to me as I’m not in the US, but from a short glimpse on those sites and discounting duplicates between them, I’d say that *real* Delphi jobs in the US are at most in a couple hundreds, not in the one thousand!

Back that with the fact that most Delphi programmers have to forge their own niche out of the market with dynamite against C and Java prejudices and you have a bad example mixed with a sore spot.

It was dang sloppy for David I to not list more sources himself in the article to support his point. Someone was bound to call him on it. After all, if his job is to be a Delphi evangelist, should he really be shooting himself in the foot with mixed messages?

Job hunters might look further, but those who are reading him to get a general idea of what is going on aren’t, and indeed shouldn’t have to. This message was more self-sabotaging than saying nothing at all, and it is a shame because, as you yourself point out, anyone who IS in the know and even slightly motivated can find better examples.

Honestly, if I was trying to pick which languages to follow now like I did when I was young, I wouldn’t even bother looking at Delphi with the current state of the market, and flawed messages like David I’s, I would have all the justification I would need to feel right about it.

He screwed up, he was called on it. SHooting the messenger isn’t gonna change the fact that David I could and, based on his job, SHOULD have done better.

Now, let’s leave it at that, cause I figure next time David I is saying a huge “whoops” this time and will likely be more on the ball next time.

Delphi rocks… and I expect to spend many more years programming at efficiency level that other deveolpers (not using Delphi) can only dream of. That said, it would much easier with unicode support

I know a lot of Delphi developers who became C# developers because they thought that is where the jobs were, and I know a lot of companies moved to C# because they thought that was where the developers were. It is a circular argument. Not sure which side bought into the marketing first, but once one side did, it just spiraled from there. Migrating from Delphi to C# serves no practical purpose, it is just a waist of money, time and resources.

I have been a Delphi Developer for 10 years and I believe it is one of the most productive and versatile tools available today.
But companies are moving to Visual Studio C# .NET. There are many companies looking for contractors to migrate their products from Delphi to C# .NET.

I’m not saying the sky is falling, I am saying that companies have lost fate in Borland/CodeGear and Microsoft is the safe bet, who can truly blame them ?

For comparison purposes I searched DICE for for C# jobs - 7497 .