|
|
|
|
|
by throw234234234
331 days ago
|
|
I've been thinking that for some time. Its a "looser way" to describe what you want as a different modality; a dynamic interface if you will. Even with code editors I've found its good to generate a lot of volume, but the detail still needs iteration or going back to direct instruction (i.e. code/clicking/etc). That applies to any artifact where iteration and validation is required to get it right. Instead of deterministic clicking and having to instruct every detail you can describe in "vague english" and the 80%/20% rule applies. Definitely an acceleration/leverage and a smaller learning curve. |
|
Like there is no money in "GUI". There is a lot of work that each company wanting to build a good GUI app needs to put into their particular app. And the more specialized the app, the more custom and potentially complex and expensive that will be. But there are no "GUI companies", unless you count Microsoft and Apple as GUI companies.