Talk:Using a speech engine to highlight words

From Rosetta Code
Revision as of 12:59, 4 April 2011 by MikeMol (talk | contribs) (→‎Problems: Clarifications)

Problems

I think their may be problems with the task as their will be too few languages with in-built speech-recognition features. I suggest we delete the task and the original task creator add the suggestion to Rosetta Code:Village Pump/Suggest a programming task maybe?

Unless two or more languages have the ability, the task will devolve into ways to call an external library - for which we already have tasks, and it will hardly help comparing languages.

In summary, I think the task may break the guidelines section "Don't require exceedingly rare features.". --Paddy3118 12:25, 4 April 2011 (UTC)

I don't have a problem with tasks which wind up primarily calling out to libraries. Seeing how a language interacts with a particular library isn't necessarily useful in comparing a language to another language, but it is still useful for users of that language and users of that library, and may be useful in comparing libraries. Utility to users of a particular language is a significant language-community motivator for adding code to the wiki, and I've seen several languages whose communities get together to add to RC for that purpose. As for comparisons between libraries...that's something I've wanted RC to be able to cover for years. Like languages, libraries are another tool where active competition and code and idea development occur.
The bit about "don't require exceedingly rare features" was not intended to excluding calling outside the language's native semantic space. It was more intended to deal with tasks like Proof which have a very narrow definition and are written to be intolerant of non-native features. --Michael Mol 12:59, 4 April 2011 (UTC)