4 ms·

I would say developing for java that ultimately will run on mainframe is worse than developing for java for another platform (because deploying to your developm

I would say developing for java that ultimately will run on mainframe is worse than developing for java for another platform (because deploying to your development websphere is slow and not so reliable). The other problem is that Java is the most 'modern' programming language available. Nobody wants to write a web app in COBOL or C. But Java isn't that good at it either (even without websphere, java does not deploy as fast as python, ruby, php, go). The only misconception is that its 20 years out of date instead of 50. The best reason to stay well clear of it is cost, though. Not just increased development cost but those things are expensive. But for a developer it can be good. Mainframe orgs tend to be stable and pay above average.

AnimalMuppet 6y ago
> The only misconception is that its 20 years out of date instead of 50. Clarification: Are you saying that Java is actually 50 years out of date?
- timwaagh 6y ago
  No, I was trying to say mainframes are 20 years out of date instead of 50.
lboc 6y ago
>The other problem is that Java is the most 'modern' programming language available. https://developer.ibm.com/swift/2018/07/06/using-swift-create-web-services-z-os/ https://developer.ibm.com/swift/2018/07/06/using-swift-creat... https://www.rocketsoftware.com/product-categories/mainframe/python-for-zos https://www.rocketsoftware.com/product-categories/mainframe/... https://developer.ibm.com/mainframe/2018/01/19/reasons-host-node-js-applications-zos/ https://developer.ibm.com/mainframe/2018/01/19/reasons-host-...
- timwaagh 6y ago
  The article did not mention those, so i wasnt aware.