Not that it's terribly important, but in the Lua circles, the reference implementation is usually referred to as PUC-Rio Lua.
It was mostly funded by Petrobras in Brazil.
Why Go Rocks for Building a Lua Interpreter
31–40 of 61 posts
Re: Why Go Rocks for Building a Lua Interpreter
#32Earlier quoted context omitted.
Typescript chose Go specicfically because they didn't rewrite it. Go has close enough semantics to TypeScript that they could write a Go backend for tsc and do a machine port to Go and continue working from that
Didn't MSFT also fire the lead engineer for this project shortly after?
Sorry, who got fired?
Re: Why Go Rocks for Building a Lua Interpreter
#33Not that it's terribly important, but in the Lua circles, the reference implementation is usually referred to as PUC-Rio Lua.
Thanks for letting me know! I've updated the blog post to reflect that terminology.
Re: Why Go Rocks for Building a Lua Interpreter
#34Earlier quoted context omitted.
Usually when something "rocks" it is better than other things in some way. I guess it can mean anything though.
"Rocks" is most commonly used in the context of (rock) music. A statement like " rocks!" usually indicates that someone enjoys said band. But what makes you think it also means that they see other bands as now being inferior in some way? As far as I can tell, most people who find a band that "rocks" also enjoy other bands as well, often even more, and are not looking for some kind of a battle of the bands to find the…
>> "Rocks" is most commonly used in the context of (rock) music
False.
>> we know from other context that there isn't a programming language competition.
I would have expected at least one comparison to another programming language. Like "COBOL" was a real pain for this, but "Go rocks".
>> ... other stuff ...
Yeah, I don't really care one way or the other. If people want say that everything in space and time are completely undifferentiated and therefore "rock" equally, I don't really care. Rock on.
Re: Why Go Rocks for Building a Lua Interpreter
#35Earlier quoted context omitted.
"Rocks" is most commonly used in the context of (rock) music. A statement like " rocks!" usually indicates that someone enjoys said band. But what makes you think it also means that they see other bands as now being inferior in some way? As far as I can tell, most people who find a band that "rocks" also enjoy other bands as well, often even more, and are not looking for some kind of a battle of the bands to find the…
>> "Rocks" is most commonly used in the context of (rock) music False. >> we know from other context that there isn't a programming language competition. I would have expected at least one comparison to another programming language. Like "COBOL" was a real pain for this, but "Go rocks". >> ... other stuff ... Yeah, I don't really care one way or the other. If people want say that everything in space and time are comp…
> I don't really care one way or the other.
Nobody does. Why would they? It isn't like there is a competition or something.
> If people want say that everything in space and time are completely undifferentiated and therefore "rock" equally, I don't really care.
Many things having the potential to "rock" does not imply that everything "rocks" equally, or at all. I strongly suspect his attempt to write a Lua interpreter in Brainfuck would not "rock".
Re: Why Go Rocks for Building a Lua Interpreter
#36Not that it's terribly important, but in the Lua circles, the reference implementation is usually referred to as PUC-Rio Lua.
Thanks for letting me know! I've updated the blog post to reflect that terminology.
Oh, you’re welcome! I didn’t think the author would read this comment. Cool software!
Re: Why Go Rocks for Building a Lua Interpreter
#37Earlier quoted context omitted.
>> "Rocks" is most commonly used in the context of (rock) music False. >> we know from other context that there isn't a programming language competition. I would have expected at least one comparison to another programming language. Like "COBOL" was a real pain for this, but "Go rocks". >> ... other stuff ... Yeah, I don't really care one way or the other. If people want say that everything in space and time are comp…
> I don't really care one way or the other. Nobody does. Why would they? It isn't like there is a competition or something. > If people want say that everything in space and time are completely undifferentiated and therefore "rock" equally, I don't really care. Many things having the potential to "rock" does not imply that everything "rocks" equally, or at all. I strongly suspect his attempt to write a Lua interprete…
Let's see if we can break HN nesting algo with this thread.
>> Many things having the potential to "rock" does not imply that everything "rocks" equally, or at all
That isn't what I am suggesting. I am saying that I do not care if people use the word "rocks" to describe an impossibly spherical marble rolling on an impossibly flat surface - equal across all space and time. Or, to describe, something that is uniquely better than all others. Use the term as you see fit. Use it to describe the value 4.532341 +/- 0.00001345 if you like.
Re: Why Go Rocks for Building a Lua Interpreter
#38Earlier quoted context omitted.
Didn't MSFT also fire the lead engineer for this project shortly after?
Sorry, who got fired?
He means probably Ron Buckton: https://xcancel.com/rbuckton/status/1922364558426911039
Re: Why Go Rocks for Building a Lua Interpreter
#39Earlier quoted context omitted.
> I don't really care one way or the other. Nobody does. Why would they? It isn't like there is a competition or something. > If people want say that everything in space and time are completely undifferentiated and therefore "rock" equally, I don't really care. Many things having the potential to "rock" does not imply that everything "rocks" equally, or at all. I strongly suspect his attempt to write a Lua interprete…
Let's see if we can break HN nesting algo with this thread. >> Many things having the potential to "rock" does not imply that everything "rocks" equally, or at all That isn't what I am suggesting. I am saying that I do not care if people use the word "rocks" to describe an impossibly spherical marble rolling on an impossibly flat surface - equal across all space and time. Or, to describe, something that is uniquely b…
> Use the term as you see fit.
Obviously. But you already suggested that in your first comment. For someone who claims to not care...
Re: Why Go Rocks for Building a Lua Interpreter
#40Go rocks for pretty much everything
Go routines are very nice. Way better than async await nonsense in other languages. if err != nil {return .., err} gets pretty tedious however. Everything tends to be very mutable / nullable as well which could be better. Also not really any faster than Java/C# - just another GCed language.
Go can be way faster than those. Garbage collection is not an issue at all if you write efficient code
And the error handling is way better than catching stuff because it’s so explicit