Re: [Jack-Devel] major change in jack1 MIDI handling

PrevNext  Index
DateSat, 12 Oct 2013 09:44:34 -0700
From Devin Anderson <[hidden] at gmail dot com>
ToPaul Davis <[hidden] at linuxaudiosystems dot com>
CcJACK <[hidden] at lists dot jackaudio dot org>
In-Reply-ToPaul Davis Re: [Jack-Devel] major change in jack1 MIDI handling
Follow-UpStéphane Letz Re: [Jack-Devel] major change in jack1 MIDI handling
On Sat, Oct 12, 2013 at 4:37 AM, Paul Davis <[hidden]> wrote:

> Jack2 has its own development "group"
> who are happy with its code structure and who have done some great stuff
> (Devin's work on MIDI drivers is really fantastic).

First off, I appreciate the compliment.  A lot. :)  Thanks.

I wouldn't say that I am "happy with [JACK 2's] code structure".  I
strongly dislike the architecture and design patterns used in JACK 2.
I find the coding style confusing and frustrating (CamelCase function
names are gross).  The overuse of inheritance and underuse of
component architecture makes it very difficult to track down function
definitions.  There are virtual functions that are pointlessly defined
(never used).  I could go on, but I think you get the point.

The reason I chose to add code to JACK 2 is because C++ afforded me
the path of least resistance.

I prefer the architecture and code structure of JACK 1.

-- 
Devin Anderson
surfacepatterns (at) gmail (dot) com

blog - http://surfacepatterns.blogspot.com/
midisnoop - http://midisnoop.googlecode.com/
psinsights - http://psinsights.googlecode.com/
synthclone - http://synthclone.googlecode.com/
PrevNext  Index

1381596279.2709_0.ltw:2, <CAG7zqTq-3xqVHApcc85A7RT96unVKD2PPUQUz4WQKsG7nr-dgg at mail dot gmail dot com>