Ah, I misunderstood you then. I'm sorry for that (on the networking). So the only thing we disagree on is whether or not the networking library should directly support web technologies directly. Because I actually think that the standard library should try to stay up to date with web technologies.
I said "need" there because I think it's one of the blanks that should be filled in the standard library.
@jlb: I forgot to say this earlier. You said
|And what is wrong with that? I think it is a very good thing that C and C++ aren't considered good candidates for web development. Look at how much problems you have been having with your C++ book, do you really think that C++ should be a first choice for something as "simple" as web development?|
You know, I don't understand why you want C++ to be thought of as hard. Complexity is the enemy of simplicity. Code should be kept as simple as possible. That's something Stroustrup preached in PPP2. You read that book, too, didn't you?
(@jlb and @helios) I disagree with just using the fact that people have difficulty with doing things in C++ as an argument to say that it shouldn't be a candidate for a language used for web development. In fact, people do already use it for that and it's actually really easy if you use the right framework or library (and if you actually understand how to use that framework or library). The standard library just needs to provide support for it directly and also give us the things we need in a modern language that Python and other web languages provide already. Some of those things, sans the web support, are already in TS papers being considered for standardization in C++20 or later. Once those things make it in, people who left C++ might come back anyway. Because at that time it'll be easier to do the things that people want to be able to do in a modern programming language. And then when the standard library gives support for web technologies, people will care about it more than they would if those other things weren't already supported directly. And that's what I think the standards committee should do. It'd be better if we got web technology support along with the other stuff, though.
And it's not really even the standards committee's fault if people think C++ is hard. It's our fault as the users. Read this: https://arne-mertz.de/why-simplify-cpp/
. I think both you and Helios should read this. It's a plea to "keep C++ simple". But it's not a plea to the standards committee, but to the users of the language. Because it's the users' code that makes other people think C++ is harder than it actually is. Or at least it's a part of it.