On Tuesday, 31 March 2015 at 06:23:07 pm +0200, Élie Roux wrote: > > I'm not the right person to ask about this. I'm heavily biased towards > > Ruby. I really don't like the whitespace-aware structure of Python > > code. > > I admit I'd prefer Ruby too... A drawback is that we can forget about > the library and user interface... or, to say it otherwise, it restricts > the choices to rubyqt, but it might be a sensible choice. > > > > The lack of OO kept Go off my list. I wasn't aware of Rust. I will > > have to look into that. > > Well, it doesn't have 00 neither apparently...
At quick glance, Rust has implementations, traits, and structured types which may be good enough for what Gregorio needs. Rust is still in alpha though, so it's going to evolve quickly, maybe too quickly for us. > > Javascript would be a bit of a mess for Gregorio. The human would still > > need to be a translation layer when debugging it, unless you store > > strings, but then your memory usage will run wild. > > Right, javascript has too many drawbacks > > >> Lua would be interesting and easy to distribute, but everything would > >> have to be rebuilt from scratch (including yacc/flex files). > > > > This is worth some thought. I don't know about its memory > > characteristics though. > > I don't think memory would be a problem, but lua has the qualities of > its drawback (I'm not sure it's the right wording to translate a French > idiomatic expression): it's simple, so it would require much more code > than Ruby I believe... Yes, Lua would require much more code. I kind-of feel like experimenting with porting Gregorio to D, C++, and C# to see if I get anywhere. I am on vacation this week, but somehow I don't think it'll be enough to see even one of those efforts through, especially given my duties in church later this week. Henry _______________________________________________ Gregorio-devel mailing list [email protected] https://mail.gna.org/listinfo/gregorio-devel
