I think that it has some pitfalls when it comes to how Logic works VS DP. Think German app VS american app... there is a fundamental difference in how they approach the same issues.
I have always divided the main Mac DAWs into 2 groups: DP and Pro Tools, US, and Cubase/Nuendo/Logic into the European camp. I can jump from one daw in a group to the other pretty easily. I went from Logic to nuendo and back for a while, and found it to be very easy.
I have a couple of clients (I do tech support in the music industry here in LA) who use DP, and they are always grumbling at me to learn DP. I have tried, and can do most things, but it took a while to "get" that DP, like ProTools, does midi as a track, a VI is a track, and an audio track is a single thing, and up until very recently, that is how they were, whereas Logic had midi for external, midi for the built in VI, and audio.
That means in DOP O make a midi track that drives the additional VI track. In Logic they are both in a single track under most circumstances. Now that we are getting into more multitimbral midi based devices (Kontakt, omnisphere, RMX for example) Logic people are starting to learn the DP way of doing things: Midi triggers VI sends to multi outputs for audio. BUT for Logic users, this wasn't the norm, and most oldt imers have had to adapt to this new way of working. In DP it is normal.
Logic has the track inspector, where your track modifiers live... midi quantization, velocity adjustments, placement on the time line in regards to moving the data back or forward in ticks or milliseconds... It makes adjustments very easy. In DP you have to open up a menu to do that, the same with ProTools.
It's really hard to explain (as you can see by my somewhat convoluted reply) but like I said, it's more of how one thinks with one DAW VS the other...
Does that make any sense yo you at all?