Python has analogs for almost everything that Java has. There are some differences though. Off the top of my head: Obligatory OOP. Python classes are optional. Access modifiers. Python has no analogs for public/private/protected. All classes and methods are public. Although there are conventions governing 'private' methods, there is nothing stopping you from using them in a public context. Packages. Python does allow modules, but the Java 'package' concept is missing. Typing. Python has no compile-time type checking. You can freely mix types and change types of variables at runtime. I would strongly suggest you look up Python type hints and start using them from day one. It will greatly aid debugging. Abstract classes. Python has an ABC (abstract base class) module which does almost the same thing, but there are differences. Interfaces. No such thing in Python. Since Python allows multiple inheritance, interfaces can be simulated with abstract base classes. Generics. Since there is no compile-time type checking, the concept of generics doesn't really apply. Again, you can use type hints to document generics, but they won't be enforced. Lambdas. Python does have lambdas, but they are limited to single expressions, unlike the code blocks that Java allows. More on reddit.com

I don't know who originally said this, but a quote I'm quite fond of is: Python is not the best language for anything, but it IS the second-best language for everything. Part of what makes Python popular and loved is that it is so versatile. You can write small little scripts, or you can write enterprise applications. I have done both. Is it going to be the fastest option? Almost certainly not. But in most cases it will certainly be fast enough. Besides, the real cost-sink in software is usually not in performance efficiency (how fast it runs), but instead in the cost to maintain the code-base (software engineers are expensive). Python can be just as maintainable as Java or C#, and is inherently more maintainable than some other languages (I'm looking at you, Go and Objective-C). Whether your Python code is maintainable is subjective and variable, up to the knowledge and experience of the engineers working on it. The versatility of Python is hard on some devs who feel that there is a "right way" to do everything. They balk at using "the second-best" option. They hate asking an object to quack and handle an error if it moos, rather than being told ahead of time "this is a duck". And that's FINE. Python doesn't have to be for you. Go enjoy C#. Oh, and a side-note it sounds like a lot of your frustration was with the tooling you were using when working in Python and/or your style of development. I find debugging Python to be much nicer than debugging other "loose" languages such as Javascript or Ruby. And IDE integration and auto-complete is a solved problem, if you bother to implement it (and are using a competent IDE). I suspect that an hour of pair-programming with a senior Python engineer who could show you that stuff would help ease a lot of the frustration you seem to be having. More on reddit.com

Lots of good answers here already. I don't think anyone's mentioned it already, but the garbage collection system in Java is amazing, and has lots of tuning options for different workloads. CPython's GC is quite basic compared to the JVM. More on reddit.com

I mean, they're both very advantageous, and have lots of job opportunities, though in different areas. Most Python jobs revolve around data science, AI, automation. Most Java jobs are back-ends for enterprise/large companies or enterprise related software, and legacy Android apps (I say legacy only because newer apps are most likely using Kotlin while Java is being used to maintain old apps). More on reddit.com