"Conventional" (pianoroll-sequencer) DAWs only became the standard recently because nobody wanted to learn how to use a tracker. The main downsides are that they are a slave to the mouse (therefore much slower than trackers) and you generally can't see the notes of more than one channel at once. The only upside that they have on trackers is that they are generally easier to learn. What would take a proficient pianoroll-sequencer user an hour generally takes me 10 minutes in a tracker. Coming back to the hhkb, those speed gains would be lost by needing to use FN to access the arrow keys and insert.
also, just because I don't want to drop the sunvox thing
More
sunvox on ios and android is for people who use trackers already and are in a situation where they cannot access their PC anymore. It is, by far, the most inferior version of the tracker, but it's not meant to be good. It's meant to give people stuck on mobile something other than MilkyTracker, which is an exact clone of FTII (which, by the way, was released in the 90's). It is for people like my close friend who originally showed me Renoise and Sunvox (famitracker was my first tracker but I thought it was the only tracker for a long time), he's bedridden by "something" causing extreme fatigue, along with early-onset arthritis in a fair amount of his joints. Don't reply to anything about him if you quote this.
My first experience with trackers was Buzz, and then Renoise. I just didn't warm up to either, and prefer the DAW sequencer approach, which feels more intuitive to me. I started out a keyboard player, so the pianoroll is much more intuitive to me visually than the spreadsheet look of trackers. And although some trackers have pianoroll implemented, there are other issues that just don't mesh well with pro audio standards/workflow. When/if I run into a problem,I can't exactly go to my composer colleagues and ask for tips, since none of them are using trackers--they are all using industry standard DAW. And since most tracker users aren't professional composers doing orchestral scores (it's mostly used for electronic music), they won't be able to help with specific issues I would need help with, such as running into problems when using high-end orchestral libraries inside a tracker.
Anyway, it's just horses for courses; different needs, different preferences. I try everything and then stick to what works best for me. with DAW's, I started with Studio Vision, then Cubase, then Sonar, and have played around with various other popular or obscure ones over the last 20 years or so. These days, they copy each others' features so much that you can pretty much pick any of the big DAW's and have a similar workflow. I stick with Sonar now because I'm most familiar with it.
At the end of the day, it's the music you make that matters, just like with all the keyboard discussions and debates, what really matters in the end is what you actually write/code/play with the keyboards. Someone can talk until blue in the face about keyboards, but if the keyboards are only being used for meaningless things, then does it ultimately matter? But if someone is using the cheapest membrane keyboard on the market, yet he's writing the next Great American Novel that will transform the literary landscape of the 21st century, then who cares what keyboard he's using?