It's literally only because of Twitter and Twitch in the past few years (essentially listening in on other people's conversations) that I began to get any hint about the extent of dissatisfaction.
-
-
Replying to @JamesWidman @TimSweeneyEpic and
I feel like it's fair to say that communication habits could be improved.
2 replies 0 retweets 2 likes -
Replying to @JamesWidman @TimSweeneyEpic and
So, sure, by all means, write up your concerns. I'll make sure that one of the [shamefully private] mailing lists sees the URL.
1 reply 0 retweets 2 likes -
Replying to @JamesWidman @TimSweeneyEpic and
And sure, start a new standards body. But be ready for other programmers in the industry---programmers whose feedback you would value---to "have no time" for something that isn't part of their current crunch.
1 reply 0 retweets 2 likes -
Replying to @JamesWidman @TimSweeneyEpic and
And be ready for when you hear about their criticism only after it's too late to do anything about it.
1 reply 0 retweets 1 like -
Replying to @JamesWidman @TimSweeneyEpic and
(Note, this is not a defense of anything in the library. I'm a core-language person, and I'm just as baffled as you. This is also not a defense of the core language, which has Many Regrettable Things.)
1 reply 0 retweets 1 like -
Replying to @JamesWidman @TimSweeneyEpic and
(This is also not a defense of the committee's process, which is nutty and harmful in several ways.)
1 reply 0 retweets 1 like -
Replying to @JamesWidman @TimSweeneyEpic and
Some degree of "outreach" from the committee might help the situation, maybe surveys, or presentations/panels at industry events like GDC, where you'd get more organic feedback from people who can't be involved on their own.
2 replies 0 retweets 1 like -
Replying to @JoshuaBarczak @TimSweeneyEpic and
Since I haven't been regularly involved with the committee since very early 2015, I'm not sure how this would happen, although SG14 members should probably be aware that there is at least some interest in this.
1 reply 0 retweets 0 likes -
Replying to @JamesWidman @JoshuaBarczak and
I think generally gamedevs ignore the standard libraries so we just snipe at their bloat and complexity as it’s not practical to dig in adequately to share a deeply informed opinion on why each edge case doesn’t justify a new set of features.
1 reply 0 retweets 0 likes
On the core language, I think we all do like the general direction (lambdas, modules, concepts), and dislike the complexity growth, but extrapolating from just my experience here: whenever we dig in we do recognize the necessity for each quantum of complexity growth.
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.