Re:Performance patches in Go 1.11
by pjmlp on Friday June 22, 2018 @09:30AM
(#17373780)
I am always torn in such approaches, in one way it means throwing away decades of code optimization.
On the other hand, in a world that devs only believe in stuff when others actually implement it in production, it is nice to see that their toolchain is self sufficient without the usual C or C++ dependency.
Many language designers opt for implementing their toolchains in C or C++ just for mere convinience, and it is ok so.
However it creates the wrong perception among those without compiler development knowledge, that C and C++ are the only way to implement a toolchain.
Re:Performance patches in Go 1.11
by masklinn on Friday June 22, 2018 @09:37AM
(#17373827)
Seems to me these are orthogonal concerns, LLVM is in C++ but the question I answered was about using LLVM versus implementing a custom toolchain, not implementing a custom toolchain in C++ versus some other language.
On the other hand, in a world that devs only believe in stuff when others actually implement it in production, it is nice to see that their toolchain is self sufficient without the usual C or C++ dependency.
Many language designers opt for implementing their toolchains in C or C++ just for mere convinience, and it is ok so.
However it creates the wrong perception among those without compiler development knowledge, that C and C++ are the only way to implement a toolchain.