Talk:Element-wise operations: Difference between revisions

Content added Content deleted
(near-duplicates vs duplicates.)
No edit summary
Line 14: Line 14:
::RC does have tasks that are ''near'' duplicates, especially at the more mundane level. RC also tries to categorise those tasks and flag/remove duplicates. Speaking as just one member of a community, I personally wouldn't vote to try and remove the tasks you mention and replace them with a composite task. I might however vote for a rename of ''some'' to Matrix/Multiplication, Matrix/Transposition, Matrix/Exponation operator; which can make things a little tidier. (Like the Sorting algorithms/... tasks)
::RC does have tasks that are ''near'' duplicates, especially at the more mundane level. RC also tries to categorise those tasks and flag/remove duplicates. Speaking as just one member of a community, I personally wouldn't vote to try and remove the tasks you mention and replace them with a composite task. I might however vote for a rename of ''some'' to Matrix/Multiplication, Matrix/Transposition, Matrix/Exponation operator; which can make things a little tidier. (Like the Sorting algorithms/... tasks)
::Often tasks are kept small to encourage new contributors and contributions: people have a finite time to spend and might feel prompted to contribute whole examples if the task encourages short examples. --[[User:Paddy3118|Paddy3118]] 00:58, 11 June 2011 (UTC)
::Often tasks are kept small to encourage new contributors and contributions: people have a finite time to spend and might feel prompted to contribute whole examples if the task encourages short examples. --[[User:Paddy3118|Paddy3118]] 00:58, 11 June 2011 (UTC)
:::Then it leads back to my "using vector instead of matrix as example is better" argument, doesn't it? I don't really care how others would implement their matrix system, but if I want to write the tasks, having to do the same thing at four different places gets very tiresome. --[[User:Ledrug|Ledrug]] 02:16, 11 June 2011 (UTC)