Jump to content

Talk:Strange unique prime triplets: Difference between revisions

m
→‎added a stretch goal: added more comments.
(→‎added a stretch goal: added some comments.)
m (→‎added a stretch goal: added more comments.)
Line 40:
:::: a run of 10_000 takes <37 secs for the Python code. (I suspect the sieve library may be written in C). I am fine with the 1_000 limit as it stands --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 13:07, 11 March 2021 (UTC)
 
::::: Extending the limit based on one's own favorite computer programming language &nbsp; (or any one specific language) &nbsp; timings shouldn't be the criteria for a stretch goal. &nbsp; There are slower computer programming languages that wouldn't attempt a run of that size. &nbsp; The reason for this site is to compare (among other things) &nbsp; programming language constructs, algorithms, idioms, methods, etc, &nbsp; without having a contest to see how many numbers can be generated/produced in the shortest amount of time. &nbsp; I'd like to see less of how fast a certain computer programming language can execute/compute the results &nbsp; (for a stretch goal or whatever). &nbsp; I don't mind viewing the comparison of how fast dissimilar algorithms/methods are when using the same particular computer language &nbsp; (method '''A''' is 50% faster than method '''B'''). &nbsp; That being said, if it were me entering this Rosetta Code (draft) task, &nbsp; I would've added the stretch goal as part of the task's requirements as a "regular" requirement, &nbsp; and added a stretch goal of &nbsp;10,000. &nbsp; That would've allowed "slower" computer programming languages to try to attempt the stretch goal if feasible, &nbsp; but still show how their programming language would tackle the goal of &nbsp;1,000. &nbsp; Adding a stretch goal made it optional, &nbsp; noting that there were already existing solutions by the time I added the stretch goal, &nbsp; and very few of us (I think) don't appreciate moving targets for Rosetta Code tasks, &nbsp; draft or otherwise. &nbsp; &nbsp; -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 13:24, 11 March 2021 (UTC)
Cookies help us deliver our services. By using our services, you agree to our use of cookies.