I think this is a religious question ;-) Java is often underestimated, because people are not aware of its lambda functionality which makes the code very readable. Scala - it depends who programs it. People coming with the normal Java background write Java-like code in scala which might not be so good. People from a functional background write it more functional like - i.e. You have a lot of things in one line of code which can be a curse even for other functional programmers, especially if the application is distributed as in the case of Spark. Usually no comment is provided and you have - even as a functional programmer - to do a lot of drill down. Python is somehow similar, but since it has no connection with Java you do not have these extremes. There it depends more on the community (e.g. Medical, financials) and skills of people how the code look likes. However the difficulty comes with the distributed applications behind Spark which may have unforeseen side effects if the users do not know this, ie if they have never been used to parallel programming.
> On 7. Jun 2017, at 17:20, Mich Talebzadeh <mich.talebza...@gmail.com> wrote: > > > Hi, > > I am a fan of Scala and functional programming hence I prefer Scala. > > I had a discussion with a hardcore Java programmer and a data scientist who > prefers Python. > > Their view is that in a collaborative work using Scala programming it is > almost impossible to understand someone else's Scala code. > > Hence I was wondering how much truth is there in this statement. Given that > Spark uses Scala as its core development language, what is the general view > on the use of Scala, Python or Java? > > Thanks, > > Dr Mich Talebzadeh > > LinkedIn > https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw > > http://talebzadehmich.wordpress.com > > Disclaimer: Use it at your own risk. Any and all responsibility for any loss, > damage or destruction of data or any other property which may arise from > relying on this email's technical content is explicitly disclaimed. The > author will in no case be liable for any monetary damages arising from such > loss, damage or destruction. >
