4 ms·
It is also very antagonistic. It's not an evenhanded exploration of the tradeoffs of two approaches, it's pretty much just talking trash. Disappointing.
by steveklabnik 5y ago
It is also very antagonistic. It's not an evenhanded exploration of the tradeoffs of two approaches, it's pretty much just talking trash. Disappointing.
- roblabla 5y agoI disagree that it's "just talking trash". Sure, I agree the tone of the article is overly harsh on the gcc-rs project, but it does raise some solid points that, for the stated goals of the project, the approach appear suboptimal. Every time gcc-rs comes up, the discussion always devolves to a "but there's rustc_codegen_gcc, why bother rewriting the language in C++", and I have yet to see a compelling argument why GCC-RS is indeed a superior solution, despite the many downsides. I think the answer is that it isn't necessarily a better solution, but the people with the necessary knowledge to make a gcc frontend or backend happen tend to be more familiar with C++, and so GCC-rs is actually the path of least resistance?
- steveklabnik 5y agoAs I said below, one example of a significant advantage is not needing any sort of Rust compiler. It’s not one to me but it is to some. I am not saying that the project is above criticism, or that there are no downsides to its approach, but this article isn’t interested in dispassionate engineering analysis.
- cbmuser 5y agoYep, the author was very clear from the beginning that he didn't like the idea of gcc-rs and wasn't really willing to compare both approaches on the same level. I personally think that's a good thing that multiple approaches to the problem exist and in the end, the better one will hopefully be adopted by the community.
- wtetzner 5y ago> in the end, the better one will hopefully be adopted by the community. Or both. I mean, is there anything wrong with having multiple implementations of a language? They may each be better for different reasons.