As others have stated C#, PHP, Java are all good choices.
If you ever question whether or not you're picking a good language, you can always pop over here: http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html
They do data analysis on this very subject.
I personally prefer C# and we use it as the primary non-IBM i language for all our modern applications.
For report writing we use DevExpress XtraReports and SQL Reporting Services as the primary report writing tools. Making changes to a report using these reporting tools will make any RPG report writer envious due to the simplicity and flexibility you have with these tools. The GUI design and preview makes all the difference here as well as the ability to export to every modern file format you can think of with easy graphing, image, and barcoding support built into these products.
From: Booth Martin [mailto:booth@xxxxxxxxxxxx]
Sent: Saturday, January 12, 2013 7:19 PM
To: Midrange Systems Technical Discussion
Subject: Preferences for developing the i beyond the 5250 user interface
Hopefully this will be written well enough to start a discussion and avoid religious wars. My goal is to fairly hear the experiences and conclusions from those who have already traveled this path.
What works? What has a broad base of support? Where is IBM going with the user interface? How are designers, analysts, and developers moving forward with the i?
I want to develop my own skills to get the job done, and I am seeing far too many choices out there to feel comfortable with my ability to pick
the right paths forward. I have spent time working with: VARPG, OS/2,
GWT, Java, HTML, JSON, XML, Zend & PHP, EGL, and other offerings. The more I learn, the more uncomfortable I become with my skill at making choices; hence this desire to hear what others have to say.
So, what is _your_ opinion of where the future lies for RPG programmers?
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l