Which Backend Language Should I Commit to Learning?

0
2
Asked By MellowCedar42 On

I've tried Python, but object-oriented programming and the way classes and objects interact still confuse me. I then moved toward JavaScript because I thought it would make working with JSON easier, but I'm finding the language's quirks frustrating. TypeScript is now appealing because it adds structure and type safety while keeping JavaScript's syntax. Should I commit to TypeScript, return to Python, or choose another backend language? I'm mainly looking for advice on how to stop switching languages and build a solid foundation.

3 Answers

Answered By TypeSafeNomad31 On

TypeScript is a good practical option if you already understand JavaScript’s basic structure and want fewer avoidable errors. Just remember that TypeScript isn’t a completely separate runtime—it gets compiled to JavaScript—so learning the underlying language is still important. Use a simple framework and avoid adding too many tools until you understand the basics.

Answered By CodeCanyon9 On

What specifically about OOP is confusing you? Java, C#, Python, and many other major backend languages use it, so avoiding the concept entirely may limit your options. Classes and objects can feel like a huge web of references at first, but you can start with small examples and gradually introduce relationships between objects. If you describe a concrete example that feels confusing, it becomes much easier to identify the missing piece.

MellowCedar42 -

The difficult part is when several classes and objects keep calling or containing one another. It starts to feel like a map of references. I may try learning it again with smaller examples rather than abandoning it completely.

Answered By PlainOak88 On

Python is still a strong backend choice because it’s readable, widely used, and capable of handling everything from APIs to automation and data services. JSON is only a data format, not a programming language, so choosing a language based on being able to “migrate” to JSON is mixing up two different concepts. Focus on building an API that receives and returns JSON instead.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.