I use PowerBuilder (of Sybase) at my job. We have a database centric stack mainly built with stored procedures and PowerBuilder works pretty well (PowerBuilder

I use PowerBuilder (of Sybase) at my job. We have a database centric stack mainly built with stored procedures and PowerBuilder works pretty well (PowerBuilder datawindows just represent a SELECT query or point to a stored procedure). It's very legacy. The syntax is similar to BASIC, with some SQL database querying built in as a kind of DSL. The built-in string and array libraries are particularly bad. The Powerbuilder IDE rebuilds the object you're working on whenever you save, so if there are any errors you can't save the file from within the IDE. You can't view or edit a script and its ancestor at the same time. When source control is switched on, you can't save a file without checking it out first - but you can't check it out without closing it and discarding any changes you made. I usually have Notepad++ open alongside PowerBuilder at all times.