Here we'll discuss issues concerning SHORTEN.
created
last reply
- 9
replies
- 1.6k
views
- 4
users
- 5
links
Here we'll discuss issues concerning SHORTEN.
What do You think about adding task:
DEC_BIN2
Submissions can be sent only in C/C++/C99 Strict - that's why I didn't add it so far.
However, I realised that (apart from tasks: BF_PRIME1, BF_SHORT and SUCCESS which are only available in one language but on purpose) task MONS1 is also not available in all langs.
So... I should remove MONS, add DEC_BIN, change nothing or other permutations these two actions should be undertaken?
I most care about opinions of users who doesn't write in C/C++ and would be injured somehow. So please write, what do You think about it.
I would deplore it, if more problems were added, that exclude lots of languages.
Those BF problems are okay, as BF is not the "native" language of anybody (I guess), but except that I don't like language restrictions.
Allowing many languages is one of the great treasures of SPOJ in general and the Shortening Contest in special.
So: Adding more problems is a good thing, opening them only for some languages is not.
Removing a problem that has been solved by several users or changing the allowed languages (either with more or less restrictions) is mostly no good idea, if it's a challenging problem. So, I would like no changes on older problems and no language restrictions for future problems (except e.g. BF, as I posted before).
It would be great if clicking on a language name in the rankings
took you to another page with user rankings for that language,
including number of tasks completed, total score and average.
This way there would also be competition for best overall score
in each language. (Note that average score must account for
the differences in weight, not simply score / # challenges).
For example, I'm only interested in Python, and competing with
numerix for best overall Python score. But to follow my progress
in this task, I had to write a script to gather scores for each task
and make a highscore table.