There’s two parts to this.
Choosing Oxygene as a language is mainly a matter of taste and preference. For various projects I work on, I switch between Oxygene, C# and Swift (can’t quite get myself to do a serious project in Iodine yet, though I should ;). All have their strengths and weaknesses, and we’re working on managing them out. Just today, I missed being able to use a
for loop expression, in C# — only Oxygene can do that. Yesterday, i missed having
if x is Foo foo in Oxygene, which (for now) is a C# thing.
But mostly it comes down to what syntax you like better, and one time, we’ll get most features into all languages.
Choosing Elements over a different tool (in your case, Visual C#) has a lot of benefits, regardless of which language you choose — even more so (for you) once Water is out.
About 75% off my coding work is on Fire/Water, which is all C#. So when I work Windows side, that seems pretty unexciting — I could just use VC#, right? Nope. every time I’m forced to use Visual Studio (over Water), I wanna poke my eyes out. Yesterday I had to make some changes to a project (not mine) that still complied via VC#, and I was shocked about the stuff I take for granted works in RemObjects C# that doesn’t in Visual C#. (e.g. I could not implement a read-only interface property via a read/write-able property. insane!)
RemObjects C# is there better C# compiler. even if you only ever want to target .NET, even if you prefer using C#, Elements is the better option. Silver is the better Swift compiler. Even when I write a project that’s only ever gonna be Mac or iOS, I’d never even consider using Xcode instead of Silver — even though the language would be the same.
Of course on top of this come all the benefits from being able to use the same language, across multiple platforms. Or using two (or more) different languages in the same project. Or… Or… Or…
It’s worth getting familiar with C#, yes. But I wager even if you decide you prefer C#, you’re better of with our C# than you are with Microsoft’s.
but of course, with Elements it’s also not a question of none or the other. You can ix Oxygene and C# freely in your code. If/since you like Pascal, write the bulk of your code in Oxygene. If you find a nice class on-line that you wanna reuse, and you don’t wan’ to Oxidize it, then you can just use it as is, in the same project. Just add a
.cs file and add it. You can even have the same class split cross multiple partial class files, in different languages.