Talk:Old Develop activity: Difference between revisions
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
== Feedback on Translation of keywords == |
|||
There is a drawback if keywords are translated to one's native language. People will want to share code snippets. Although translation is feasible in the IDE, it is not obvious online. Using custom translations are even more of an issue. The IDE could translate the snipped based on its original language but this would require extra effort by the user. |
There is a drawback if keywords are translated to one's native language. People will want to share code snippets. Although translation is feasible in the IDE, it is not obvious online. Using custom translations are even more of an issue. The IDE could translate the snipped based on its original language but this would require extra effort by the user. |
||
Line 8: | Line 8: | ||
Multi/dynamic language comments on the other hand is beneficial, especially in example code etc. |
Multi/dynamic language comments on the other hand is beneficial, especially in example code etc. |
||
--[[User:80.201.17.119|80.201.17.119]] 05:10, 20 December 2006 (EST); |
|||
WeBToR |
Revision as of 10:10, 20 December 2006
Feedback on Translation of keywords
There is a drawback if keywords are translated to one's native language. People will want to share code snippets. Although translation is feasible in the IDE, it is not obvious online. Using custom translations are even more of an issue. The IDE could translate the snipped based on its original language but this would require extra effort by the user.
There are much less keywords than methods provided by the standard libraries. If people need to learn the meaning of 'httplib' etc., then learning the meaning of 'string' and 'if' is not much more extra effort. How many native English speaking people automatically associate the word 'string' to a bunch of characters? ;-)
I think learning some keywords initially is more valuable in the long term. Multi/dynamic language comments on the other hand is beneficial, especially in example code etc.
--80.201.17.119 05:10, 20 December 2006 (EST);