I thought it might be helpful for the Python community to be aware of the growth issues that the C++ community has/is discussing, at the moment. I am *not *saying we have those same issues, but we might know to avoid similar issues in our future? Here's and letter: http://open-std.org/JTC1/SC22/WG21/docs/papers/2018/p0977r0.pdf And an article on a later interview: http://www.theregister.co.uk/2018/06/18/bjarne_stroustrup_c_plus_plus/
Paddy3118 wrote:
Here's and letter: http://open-std.org/JTC1/SC22/WG21/docs/papers/2018/p0977r0.pdf
This is why it's important for a language to have a BDFL. -- Greg
On Mon, 18 Jun 2018 03:49:35 -0700 (PDT) Paddy3118 <paddy3118@gmail.com> wrote:
Interesting quote: « Adding anything new, however minor carries a cost, such as implementation, teaching, tools upgrades. Major features are those that change the way we think about programming. Those are the ones we must concentrate on. » Regards Antoine.
Paddy3118 wrote:
Here's and letter: http://open-std.org/JTC1/SC22/WG21/docs/papers/2018/p0977r0.pdf
This is why it's important for a language to have a BDFL. -- Greg
On Mon, 18 Jun 2018 03:49:35 -0700 (PDT) Paddy3118 <paddy3118@gmail.com> wrote:
Interesting quote: « Adding anything new, however minor carries a cost, such as implementation, teaching, tools upgrades. Major features are those that change the way we think about programming. Those are the ones we must concentrate on. » Regards Antoine.
participants (3)
-
Antoine Pitrou -
Greg Ewing -
Paddy3118