News for hackers. Stuff that matters.
Re:Porting the Go compiler from C to Go by yohanatan on Saturday April 26, 2014 @02:57AM (#7650663)
This should not have been down-voted. We are talking about translation from C -> Go and C++ -> Rust (which are both in the opposite direction of the definition given for 'transpiling').
Re:Porting the Go compiler from C to Go by vanderZwan on Saturday April 26, 2014 @03:28AM (#7650702)
I agree that your comment added value to the discussion, and gave a counter-vote.

However, arguably the term could make more sense there, if we ignore the earlier definition and instead assume "trans" is short for "transcendent", as in "climbing to a higher level".

If we then simplify that to "compile from one language to another of roughly equal or higher level", it becomes a useful word to indicate a specific subset of ways one can do compilation.

Of course, I'm completely pulling this out of my ass and I might piss off actual CompSci people who use very specific and strict definitions in their papers (kind of like how some get annoyed with the procedure/function mixup), so take this with a grain of salt.

Re:Porting the Go compiler from C to Go by ldrndll on Saturday April 26, 2014 @03:12AM (#7650679)
> You are technically correct in that compile already implicates a translation, but we usually use that term [ie compile] refering to a translation into a lower level language and not another language at the same level.

The way I understood what he wrote, he was making the same point as you. Presumably the people downvoting you had a similar interpretation of what he wrote.