Irony, or Abstraction?
The irony of my previous post is not lost on me. On the one hand, I am advocating that others learn music using a non-standard system (JiMS) due to the benefits of its higher level of abstraction, while at the same time choosing myself to learn a standard (programming) system despite the costs of its lower level of abstraction.
This analogy is misplaced, however, because a single level of abstraction removes the inconsistency.
Adobe's ActionScript/Flex/Flash toolset isn't the "standard programming system" today; today's standard is Java. Adobe's toolset is an alternative to today's standard that offers efficiency benefits in the development of Rich Internet Applications (RIAs). Therefore, if one views what I'm doing as learning to develop RIAs, then I'm choosing the non-standard, high-efficiency approach -- just as I am suggesting others do by using JiMS to do when learning to develop music (so to speak).
This analogy is misplaced, however, because a single level of abstraction removes the inconsistency.
Adobe's ActionScript/Flex/Flash toolset isn't the "standard programming system" today; today's standard is Java. Adobe's toolset is an alternative to today's standard that offers efficiency benefits in the development of Rich Internet Applications (RIAs). Therefore, if one views what I'm doing as learning to develop RIAs, then I'm choosing the non-standard, high-efficiency approach -- just as I am suggesting others do by using JiMS to do when learning to develop music (so to speak).
Labels: JiMS


0 Comments:
Post a Comment
Links to this post:
Create a Link
<< Home