Two of my friends and I worked at a company as the software engineers for a mini-mart project. The project manager told us that he had done a similar project which we could use to customize for the new project.
His project used Microsoft Access as the interface and SQL Server as the database system.
At the early point of the new project, we came to the stage of technology dilemma. Should we use the same technology, MS Access and SQL, VB, VB.Net, or Java?
All three of us were more comfortable with VB or VB.Net than MS Access but we chose the latter.
Before it was a surprise to me to hear most of my friends say that many companies (including a bank) in Cambodia are still using legacy language.
"Why the legacy language?"
or
"Why not the new and improved VB.Net? Or platform-independent Java?"
In our case, we chose the legacy language simply because that the previous project we base on use the legacy one and that we were told it would simply be a minor customization. But it turned out to be a major work! I'll tell the painful experience in the next blog.
Now why do companies use legacy language?
Possible reasons:
-They are used to it.
-They fear the risk of adopting new language.
It is similar to why Linux evangelists find it extremely hard to lure people out of Windows.