Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Arno Welzel Newsgroups: comp.lang.javascript Subject: Re: Looking for a MIDI file parser acknowledging how broken javascript become. Date: Tue, 12 Nov 2019 12:08:39 +0100 Lines: 34 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: individual.net 5FqTQBVgv1uPzGkJcnSGXgmmyjB97bAvSnaQMRlYVDbf0PfKrv Cancel-Lock: sha1:qNzHnsSAT5T2q+6jMIWsvnu7qbM= In-Reply-To: Content-Language: en-US Xref: csiph.com comp.lang.javascript:37755 On 08.11.19 07:18, Jonas Thörnvall wrote: > It is a sad story of human stupidity. Basicly a midifile is messages > there is timed messages and data messages. The idiots building their > parsers using fig lingo. It is fucking tedious implementing parsers, > but when the endresult coming out of parser is harder to use then > make a parser of ones own, one wonder a bit of the state of matter. > > How fucking hard can it be to store the messages as strings in an > array? The hard part is reading out the fucking files. Keep in mind that MIDI was introduced more than 35 years ago in August 1982. At that time computers (including those in synthesizers) where not that powerful and did not have a lot of memory - we talk about kilobytes, not megabytes. Also see: > Not fucking get them into an array of messages. Each message is > simple to parse, no but the fucking monkeys must create objects for > this and that, so now i have to make a parser that not made for > monkeys playing with figo lingo.... What "objects" are you talking about? Is your rant about ? Then go ahead and write your own parser. -- Arno Welzel https://arnowelzel.de