Han-Wen Nienhuys-5 wrote:
>
> On Tue, Aug 7, 2012 at 1:50 AM, George_ <georgexu...@gmail.com> wrote:
>
>>> I'm trying to explain that the constant factor (namely 8-fold) comes
>>> at a tremendous cost. Writing multithreaded code without getting stuck
>>> in race-conditions and deadlocks is extremely difficult and time
>>> consuming, and lilypond already has a shortage of developers without
>>> taking on parallelism.
>>>
>>> In the context of the original remark (making lilypond more suited as
>>> a rendering engine), multithreading is simply a stupid way to spend
>>> programmer resources. If you're writing a GUI using Lily as a
>>> renderer, have the GUI manage the data structures (and possibly, the
>>> parallelism), so LilyPond can suffice to stay "simple" and
>>> single-threaded,
>
>> Where does the GUI come from?
>
> See Lucas Gonzo's mail earlier in the thread,
>
> --
> Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
>
> _______________________________________________
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
This one here?
http://old.nabble.com/Re%3A-Sibelius-Software-UK-office-shuts-down-p34246393.html
The reason I ask is, how will such a GUI compare in terms of features,
compatibility, and speed, to others already available, as well as to things
like LilyPondTool for jEdit?
--
View this message in context:
http://old.nabble.com/Sibelius-Software-UK-office-shuts-down-tp34245636p34264481.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
