Re:Streem – a new programming language from Matz
by apoorvai on Thursday December 11, 2014 @12:57PM
(#8736104)
I'm not really a programming language expert, but it seems to me that having an implementation being the spec wouldn't be a good idea. If the Streem implementation has a bug, then the bug becomes the authoritative behavior. Any platform specific quirks would also make it difficult to have defined behavior.
[ Parent
| on HN ]
Re:Streem – a new programming language from Matz
by ianlevesque on Thursday December 11, 2014 @12:59PM
(#8736120)
Yep, welcome to Ruby!
To be fair, a spec with tests was reversed out of the ruby implementation[1], so things have improved a bit.
Re:Streem – a new programming language from Matz
by aidenn0 on Thursday December 11, 2014 @01:10PM
(#8736179)
Implementations are nearly always the spec when a language is young. You want to be able to experiment and make changes. Then as it matures, you typically get a spec.
Re:Streem – a new programming language from Matz
by skrebbel on Thursday December 11, 2014 @01:03PM
(#8736138)
Sure, but this is not finished at all. Starting with the spec instead of a prototype implementation sounds like a very very limiting and unrewarding design process.
Re:Streem – a new programming language from Matz
by jfoutz on Thursday December 11, 2014 @01:02PM
(#8736133)
There's an old argument about worse is better. The gist is, doing things the right way is hard and takes a long time. sometimes, it's better to just get something simple out there and deal with the problems later.
Re:Streem – a new programming language from Matz
by Igglyboo on Thursday December 11, 2014 @01:46PM
(#8736397)
It looks like a weekends worth of work for Matz, I doubt he's even thinking of a spec at this point.
Re:Streem – a new programming language from Matz
by dragonwriter on Thursday December 11, 2014 @02:21PM
(#8736575)
Right now, the closest thing to a spec is the sample FizzBuzz code (as an implicit spec that "this code will solve FizzBuzz"); there is no implementation (just work-in-progress parser/lexer code.)
So, while I'll agree that there are issues that come from the implementation being the spec of a language in general, I would say we are well earlier than the point at which we can identify that as a problem with Streem.