It’s tiring though, to explain the same things over and over again, and for people who vastly outnumber you. And it’s hard to make them trust you, since what you’re saying goes against everything they have learned in school
-
-
Replying to @aras_p @ChristerEricson and
@ericniebler others and myself might feel the same way.1 reply 0 retweets 0 likes -
Replying to @Khipu_Kamayuq @aras_p and
Perhaps we should all go form our own standards body?
2 replies 0 retweets 4 likes -
Replying to @JoshuaBarczak @Khipu_Kamayuq and
So someone else can tell you YOUR work is garbage?
2 replies 0 retweets 14 likes -
Replying to @ericniebler @JoshuaBarczak and
Yes of course! ;) I’ll write a post about what I think I dislike wrt trends in c++ soon, twitter is bad for nuance indeed.
1 reply 1 retweet 53 likes -
Replying to @aras_p @ericniebler and
Aras, do it! It’s very unfortunate for new programmers coming into C++ to have the impression that they should actually use these standard library abominations in engineering practice.
8 replies 2 retweets 71 likes -
Replying to @TimSweeneyEpic @aras_p and
Perhaps an open-letter co-signed by a top 20 selection of programmers (you guys & more) with a list of what the author are/did work on would be a good deterrent.
2 replies 0 retweets 17 likes -
Replying to @ocornut @TimSweeneyEpic and
You guys are reacting to the ability to transform a range with a function (map) and the ability to join a range of range (list bind), and y'all are acting like Satan himself is walking on Earth. Get a grip.
1 reply 1 retweet 28 likes -
Replying to @ericniebler
That's not what people are reacting about. They are reacting because they know it is overly complex and costly both for minds and computers. We have seen the damage in _our industry_ and _our teams_ of this line of thought, we keep seeing it over and over every few years.
1 reply 2 retweets 34 likes -
Replying to @ocornut @ericniebler
And people are equally and justly debating how we feel alienated from the ideas promoted by this type of C++ (which probably had its use... somewhere?) and the absurd disconnect between them and the daily reality of our own industry.
3 replies 1 retweet 19 likes
At the core is a good idea, that ranges are a cleaner abstraction than iterators. But ultimately we end up with a solution that’s much worse than the problem, due to all the complexity and baggage, and since it doesn’t replace iterators we have the sum of all this complexity.
-
-
Engines are probably the fastest moving large programs to consume new C++ features. We loved lambdas and look forward to modules and (some version of) concepts, but don’t want to touch this sort of mess.
3 replies 0 retweets 18 likes -
I might be wrong, but both Unreal Engine and Frostbite (which is where my previous 3 years were spent) doesn’t use (all) Standard STL features, though? C++ features, sure, but not the STL, which is what’s messing my mind up the most here.
1 reply 0 retweets 0 likes - 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.