4 ms·
Boy I am gonna get down voted, But I rather say this. I do consider myself C++ programmer, and I like it, but truth is truth. I think C++ designers are very we
by 0xFFC 9y ago
Boy I am gonna get down voted, But I rather say this.
I do consider myself C++ programmer, and I like it, but truth is truth. I think C++ designers are very well respected scientist. But they are not programmers. This is sad truth.
Every version of C++ comes out they tend to make C++ more complicate and introduce more ways to do something which was possible before. I was/am very happy with overall design of modern C++. But they did a very bad strategic mistake. Instead of making language simpler or at improving what was there, they are introducing new syntax for everything. Let me give you instance.
Imagine we have metafunction is_void.
Before C++11, there was only one way to call it :
> is_void<t>::value
C++11 they added :
> bool(is_void<t> {})
C++14 they added :
>is_void<T>{}()
and there was plan to add this syntax to C++17:
>is_void_v<T>
Okay. I am not scientist. And I do know someone people in committee are well respected scientist and tbh I like their job alot.
But when it comes practical stuff. This is nuts. Do they think how much makes this reading code bases hard ? How much makes tooling hard ? How much makes syntax unapproachable ?
I don't understand rational behind this, Why would they add new syntax for what already possible, when they can improve core language/libraries more and more.