Talk:Padovan sequence: Difference between revisions

As it is
(As it is)
Line 22:
::(and possibly a bit-counter-productive from the perspective of the hostile party – it probably just increases the readership of the ''generic anamorphism'' variant).
:: My instinct would be to delabel, and just leave the flat sequence of alternative drafts intact. [[User:Hout|Hout]] ([[User talk:Hout|talk]]) 12:05, 28 February 2021 (UTC)
 
As I stated on your talk page Hout, and without the personal attacks; One could write a lisp interpreter in Python and create examples for Lisp and a very similar example for Python that would pass a linter, but would not be idiomatic Python.
You have ignored this and claim victimisation and bullying.
 
Your Python examples use functions that are standard in languages such as Haskel but are not mentioned as part of the standard Python distribution, (the style, as a whole was put to the community and rejected). You seem to do similar for Applescript in this task.
 
You could write similar libraries for concatMap, foldR, unfoldR, ... in C++, D, in fact in many languages and provide the same similar solution that passes a languages linter - which you know does not equate to a check for being idiomatic code, '''especially''' in these circumstances of how you write the code.
 
RC should not be filled by write once, translate by the same person to many language examples done on some treadmill, whilst ignoring how things are normally done in the target language. "It passes the linter" is a poor defense as I have pointed out, and you have ignored.
 
The idea of the site is to show idiomatic code examples for different languages. Hout, you flout that repeatedly.
 
I will, again, add the "improve" template to your Python submission, ''in the hope that you will refrain from pushing Haskel idiomatic code as idiomatic Python''.
 
An aside: A large part of Raku's entries and updates where in getting the Raku style right - how Raku does things. That was great to see
- I enjoyed other languages too because they showed off their languages quirks and idiosyncrasies. That is lost if they all just implement concatmap etc and adopt the Haskel-functional way - Which Hout is doing in Python, definitely; and possibly other languages too.
 
In short, some functional languages use an idiomatic style similar to that of Haskel. Python is not one of them. Many languages might compile or interpret this Haskel-esque style and pass their linters. This would not necessarily make the code idiomatic for that other language. Rosetta Code should strive for idiomatic examples in general - Hout is ''systematically'' attempting to pass off non-idiomatic Python in many tasks, not just this one.
 
--[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 11:24, 19 March 2021 (UTC)
Anonymous user