Hm, and how is it relevant to the discussion on what to use for a new development? I am usually using whatever the current client uses, currently on v9.1d, before that was 10.1 something, before that was a mix of v9 and v10.Just out of curiosity, what version of Progress are you working with on a daily basis?
Don’t you need to sell it to the upper management?I believe the OP is developing something for in-house use
Productive yes, but they don’t become experts and do everything people in a short time.I have taken experienced developers with good database and algorithmic skills and had them productive in ABL in a short time
Don’t you use a timer within your app? So any control that has a timer is not usable. And you do need a timer just to refresh a screen from time to time.And just what are these controls? And why would they be relevant to a business application?
Learning classes is the same, but while you are learning those classes you are reading samples in c# or vb.net code, and then try to do the same in progress, hence learning more than 1 language at the same time – and why do you need to do it?Learning the UI classes is pretty much the same either way
I completely disagree with that. I consider MSDN docs to be pretty well organized and integrated well enough. Also don’t forget about power of google JI was saying that .NET documentation is junk.
Oh, the infamous for each. Well it doesn’t differ much from select * from customer. But we are not talking about character applications. I thought we are talking about windows gui client, where regular for each is used only to get multiple records from db and do something with them later on. Or if you do insist on the use of for each here is a c# code:I dunno, there's just something about: for each
Foreach (Customer c in Customers)
{
console.writeline(c.name);
}
This is just because you are used to it, but it doesn’t matter it is better or worse.And so much of the rest of the language just flows so much more smoothly than other languages.
Of course it didn’t, the same way as general concepts of programming haven’t changed for agesThe concepts of event-driven GUI coding haven't changed in any significant way.
True, that’s why I am still to find the reason to write something in the new OO except when you would need to do something with .Net GUI.The syntax isn't important. The thought process is
I am sure half of the Wall street companies will be very interested in this conclusionMission Critical Enterprise applications aren't built by departmental teams using C# and SQL Server.
Usually it is us, Progress people, who fight to let our technology in, not the other way aroundit is a very good idea to let them rather than fight them.
I had quite a different experience – from 4 out-of-college kids trained with Progress 0 left in the technology within 1.5 year.Otherwise I wouldn't bother hiring them.