Talk:Element-wise operations: Difference between revisions

no edit summary
(near-duplicates vs duplicates.)
No edit summary
 
(2 intermediate revisions by 2 users not shown)
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)
::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)
::::''"I don't really care how others would implement their matrix system"'' <br>Then you would miss out on useful comparisons with those languages which have different levels of support for single and two dimensional arrays. Perl and Python for example have lists that are straightforward when used to ape 1D arrays, but 2D structures can be done in more than one way - I've used dicts of tuples as well as nested lists in the past. Heavy array users might turn to add-in libraries such as numpy for Python. <br>I guess RC ''is'' about caring about how others might view things to some degree. I've found it useful in day-to-day life too. --[[User:Paddy3118|Paddy3118]] 07:54, 11 June 2011 (UTC)
:::::Oh please. I don't care about how people implement matrices around here, because I can write the same ad hoc stuff myself for demonstrations, and it's as unsuitable for real work as anyone else's. I don't care how LAPACK implemented matrices even though I use it on clusters all the time, because I only need to know how to use it, not reinventing one. It's not like many Python users know how the dictionary hash function works or how a .pyc corresponds to the code in a .py, is it? You sure they are missing out much? --[[User:Ledrug|Ledrug]] 08:34, 11 June 2011 (UTC)
Anonymous user