U can use c++ on the back end and there are libraries that helps u to develop faster. But this doesn't mean u can't write front end in c++. A library called wt can help u to develop web app using c++. Kore( c library) Crowl(c++ library) ...

True, but you can't write pure C++ to execute through a front-end webpage. But you can run C++ on the backend. I wasn't sure if that's what he was asking.

What I mean is that you can't execute native machine code that was compiled via C++ in the browser. Sure, you can use Wasm, but that is a whole 'nother thing. It's a bytecode format.

using c++ for backend is pretty

?

Writing web apps with c++

that's why I use c# for backend and c++ for my own projects

I never really found C# a great language. For me, at least. It's much too similar to Java, which I cannot stand.

comparing C# to Java..... c# is a very well designed language

ofc nothing is comparable to C++ but

so seeing good C# code helps a lot understanding that the language itself has very nice possibilities

It's definitely a very popular language in business software (especially Windows apps), but that's why I don't write Windows apps.

C++ is really nice. I don't understand why people talk trash on it (ahem ahem Linus Torvalds). Yeah, it has a bigger overhead being object-oriented and all, but that's the whole point.

People talk trash about c++ because they cant handle it

modern C++ is sometimes faster than C if you use proper design and constexpr, move semantics etc

That's the point. People who doesn't know about something, talk trash about it. It happens with languages, with OSes and with everything.

*sometimes*. But it's usually a little behind. That's just because the way C code is written is much closer to machine code than object-oriented C++, which has a ton of overhead when being compiled.

I think that, it doesn't matter which language is more faster than other language. The important thing is, how well you write the code and how well you understand the language you are using. I've seen assembly code with poor performance against well C++ code. So...

Also very true. It's not just the language. But you have to agree that object-oriented languages have a lot more to compile than procedural ones.

*sometimes*. But it's usually a little behind. That's just because the way C code is written is much closer to machine code than object-oriented C++, which has a ton of overhead when being compiled.

It's not necessarily true. compiler knows better in many situations. And can optimize better things that cannot be expressed easily in C. For example std::sort is better and faster than qsort

In those certain off-cases. But for the majority of programs, writing in C is much more barebones than C++, and will this generate more optimized machine code. Object-oriented languages tend to leave more garbage code in the end result.

Which I was thinking as I wrote that. Writing Fibonacci in C++ is the same as in C, and compiles as so. This argument could go on for ages, but I personally think they both have their ups and downs. C++ is a lot easier to use in games, apps, and web stuff that requires a higher level of abstraction, while C is much more applicable in environments such as microprocessors and embedded systems.

Can someone help me out by letting me know where to start learning OCR with c++

Can someone help me out by letting me know where to start learning OCR with c++

And what makes constexpr the cover-all for C++?

Shut up! I don't have to

essley?

Hi guys could you tall me about loop and how to work essley

Because u can do evaluations at compile-time instead of runtime.

That's actually extremely useful. I'm a newbie to C++ this year (taking a college class for it in high school), and I haven't learned about constexpr yet.