When comparing C++ vs Haste, the Slant community recommends Haste for most people. In the question“What are the best languages that compile to JavaScript? ”Haste is ranked 15th while C++ is ranked 26th. The most important reason people chose Haste is:

Haste was designed to allow both the client and server to be written as parts of the same, type-safe application. This is in stark contrast to most other options, where the client and server are considered two separate entities, resulting in extra manual validation code and more chances for type errors.

Pros

Pro

Huge language supports most everything

C++ is a large language with an even larger community and following. It has libraries for every kind of task that is possible to do with C++

Pro

Powerful memory management

Allows puting large arrays on the "heap" to avoid "stack overflow".

Pro

Teaches fundamental OOP

Teaches you to leverage object oriented programming.

Pro

Excellent compiler optimization

Both open source compilers (such as Clang and GCC), and proprietary ones (like Intel's and Microsoft's) are very good at analyzing program flow and program optimization. This is mostly due to the widespread usage of C/C++ applications running everything from mobile/desktop/server Operating Systems, to search engines and webserver software, and the demand for performance.

Pro

Teaches problem solving

The great STL is the most powerful Data Structure and Algorithms Library. It would benefit you very much in problem solving, your main main way to love programming. The code is much compact compared to Java and C#. No unnecessary classes are in your way; yet when you need classes they are available unlike C. The code runs very fast.

Pro

Best way to understand algorithms

Pro

C code can be used in C++ code

Most C code will work as C++

Pro

STD is often updated

The functionalities keep growing throughout the years. C++11 gave us a soft type of garbage collecting with the smart pointers.

Pro

Client and Server as the same application

Haste was designed to allow both the client and server to be written as parts of the same, type-safe application. This is in stark contrast to most other options, where the client and server are considered two separate entities, resulting in extra manual validation code and more chances for type errors.

Pro

Almost full power of Haskell

Haste supports the Haskell 2010 standard except for Template Haskell as well as most GHC extensions.

Pro

Automatic, type safe program slicing

Haste lets you write client and server as a single program, automatically generating code for the server as well as the client, giving you full type safety even across the Internet.

Pro

Generates small, reasonably performant code

Cons

Con

Huge language gets in the way of learning

C++ is such an atrociously over-complicated language that its learning curve may get in the way of learning fundamentals. Learning C++ well is a ten-year project, and even experts are frequently surprised by the language.

Con

Module system is not great

C++ uses the #include mechanism provided by C. Which unfortunately is a poor way of accessing the API of a library. Some of the reasons why the module system is weak are:

Compile time scalability: The compiler must preprocess every header included in a file, and every header included in those headers. This process must be repeated for every translation unit in the program. As can be imagined, this doesn't scale very well. For each header added you are increasing the compilation time exponentially.

Fragile: modules included are treated as textual imports by the compiler. This causes all sorts of problems since they are subject to any macro definitions in the time of the inclusion. If any of these macro definitions collide with a name in the library it can break the library API .

Con

Undefined behavior

Subtle errors can render the entire program "undefined" by the complicated C++ standard. The standard imposes no requirements in such cases. Thus C++ compiler writers are free to ignore the existence of such cases and Bad Things are prone to happen instead. Even experts can't reliably avoid undefined cases in C++, so how can beginners be expected to do so?

Con

No two programmers can agree on which 10% subset of C++ to use

C++ is such a huge and complicated language, that programmers have to learn a disciplined subset of it to reliably get anything done. The problem is, no-one can agree on which subset to use and they can't understand each other.

Con

Retains nearly all bad habits of C

Con

Painfully slow compilation

Beginners need fast feedback

Con

Bugs easily corrupt the memory you need to find them

You can usually get a core dump, but often the call stack gets completely overwritten. Compilers are not even consistent in how they map the binary objects to code.

Con

Complicated types

Con

Standard library missing important features

Con

Arcane binding rules

Con

Tough to learn as the first language

Many of the concepts are hard to grasp if you have no prior programming experience.

Con

Duplicates C features in incompatible ways

Arrays, strings, pointers, etc. have both C and C++ versions. Sometimes the C++ versions are worse. This is more useless trivia beginners have to sort through.

Con

Incomprehensible operator overloading resoution

Con

Exceptions incompatible with C++ manual memory management

Con

No way to locate definitions

No modules, just files, and no way to tell where anything came from.

Con

No reflection

C++ objects are frustratingly opaque. This makes debugging especially difficult, something beginners have to do a lot.