AXIOOOOOOS

Try Scala ... way less verbose and you can still use Java libraries

@jamesharrington ... the main benefit is ease of testing for larger or sensitive systems.

You can also possibly catch silly mistakes before the code even compiles with something like Typescript. So adds overall predictability.

Probably not worth it for a prototype though. Also I'm mainly referring to backend (node) here btw.

Good on you.. I'd recommend getting into the habit of using a type system, Flow is an option for JS. Typescript is another good one if you're not too stuck to JS. A type system or checker will make using Node in production way better.

A UX designer just gave up on life because of this

Hahah love the differences between react and angular. So true.

While you can build web servers with C++, it will take much much longer compared to something like Python with a minimal framework like Flask.

If you are keen on using C++, then perhaps you can use NodeJS to handle all server requests and C++ plugins/extentions for speed dependant processes or integrating with legacy systems.

If you don't absolutely need to use C++, then I'd highly recommend Python since it's incredibly easy to learn and use.

P.s. that's my personal take, others can very well have a different view on this.

Python mostly because of prototyping ease and community support for that specific topic. For example, Tensorflow (Google lib for ML and DNNs) has both Python and C++ frontends

++ for Python. You will find quite a bit of tools and libraries there, also some of them are optimized with C++ already. For production, Java or C++.

@billgates if possible, you could take on freelance projects that involve elements you want to learn as well as ones you're good at. This way you're learning and getting paid (even if a little less). I found this to be more motivating.

@Voxera yes exactly! +1

In JS, functions are treated as first class objects. This allows you to return a function or pass it as an argument/parameter into other functions. This means a function could be created in one place and called in another place; closures help us handle possible problems with variable access (scope). Different from context (`this`).

Reading articles is definitely useful, the one linked above seems handy.