3 ms·
Your argument assumes workflows never change. If that were true, we would still be using whatever workflows our forebears used for every task. Since that is c
by sdp 17y ago
Your argument assumes workflows never change. If that were true, we would still be using whatever workflows our forebears used for every task. Since that is clearly untrue, workflows must be able to change.
However, given that business are formed to turn a profit, the standard workflow will remain unchanged until it is profitable to do otherwise.
If a markup-generating DSL was simple enough for designers to pick up quickly, it would make good business sense to push them through the transition.
- chiffonade 17y agoThe workflow between you and your accountant hasn't changed for quite a while. You still share information and work through a medium you can both understand - receipts and expense logs and invoices - that's what an HTML template is.
- tvon 17y ago> If a markup-generating DSL was simple enough for designers to pick up quickly, it would make good business sense to push them through the transition. Designers being able to do it isn't the problem, justifying why designers should need to is the problem.
- sdp 17y agoAh, I was making a couple of assumptions: any DSL which generates markup must be more concise than the markup itself Otherwise, there will have been no point in creating the DSL. This assumption is probably fair. An example of this would be Seaside's HTML generation DSL. a more concise language will be better in the long run This assumption is flawed and doesn't take the designers' tools into account. A DSL would need its own tools before it became a valuable long-term investment.