I also think that this is really hard to answer. OOP is easier to understand because it often maps real world problems in computer code. FP doesn't wrap the objects but the operations on that objects. FP has no side effects which makes it easier to work with but is harder to read in my opinion. I work with OOP but use some paradigms and patterns from FP in there (map, flatMap, etc).

If you really would like to understand the fundamental basics behind web development: start without the framework. If you would like to learn by doing, I don't see a problem in using the framework. In the case of React you are then also able to create mobile applications via React Native.

For learning the technologies and stacks behind both systems, you could also go both with Javascript (NodeJS on backend).

I actually think learning new languages helps you a lot because every language has some details that makes them special. In the end it's more about patterns and paradigms. In my opinion you can learn that at best with new languages that are built for that patterns. C, C++, Java are all imperative languages and C++ and Java are also object oriented. So I think you should learn about some functional patterns with JS, Scala , Haskell or Swift. There is no big gain in knowing all those languages in detail but it's very helpful to be able to read code written in it and to understand the main paradigms. Beside that you should later focus on one language that is the best fit for the platform you would like to develop for. Here are some suggestions per platform/layer: Web-Frontend: JS + some shiny framework like ReactJS Mobile: Swift (iOS) / Kotlin (Android) Backend: Go, PHP Scripting/DevOps: Python Machine Learning: Python I actually can't say much about Rust because I had no time yet to dig deeper in it. But what I heard so far sounds really amazing, is definitely a great replacement for C++.

Thanks for your follow ups! I wrote Github a mail and got a very fast response. They are happy about the feature requests (I had another one) and the responsible teams will take a look into it. Of course they can't promise anything but that's enough for me :)

Marco Alka do you know if there is some form to fill out for feature requests?

That fixes the posting problem. But having a 'profile picture' per repository would be better imo.

Yes, creating an organisation is definitely the way to go. But as you said, that fits best if a team is backing the project. Sometimes the project is still from one person only and creating an organisation would then reduce the clarity in my eyes. Do you know if there is a possibilty to create a feature request at @Github?

Thanks! What do you think about my proposed change?

Ah, I thought 'which just works' refers to C :D