We’re testing a new format of event for Clash of Code: Clash Wars. It’s a tournament of Clash of Code with one limitation: all players compete with the same language!
The first event will happen next week on Tuesday 10 of December at 8pm CET for one and a half hour of fun with Java (yes, it’s possible ). Winners will be rewarded with XP.
you don’t have to wait for all players to end your current clash to start another one.
by design, players will play different clashes and probably not the same amount
ranking is TrueSkill-based like the current COC leaderboard
all modes available. We could consider restricting the modes too in future Clash Wars events.
I don’t fear the trend of stockpiling solutions will grow with these events. Beside the relatively low amount of XP winnable (I could lower it), it’s structurally the same as public CoC. I see Clash Wars as an opportunity for the community to meet at a certain moment and have fun with a certain language.
Thanks for the questions.
Let’s make CoC great again
Shortest mode in a constrained language (that happens to be Java, for crying out loud) does not seem to me like a reliable way to make CoC great again.
I will not participate but Java is not the issue. For me the main issue of CoC is still the same, a player on an unknown CoC has no chance against a player knowing this CoC. And i assume the Clash Wars will not check this case.
Many java coders have been complaining for a long time for the unfair result in CoC because of the long-winding declare-everything language structure, when compared to most other scripting languages.
Me: I got an email from Thibaud!
Me (thinking): Oooh it might be about the next spring contest, or even better, maybe it’s a Christmas gift and Unleash-the-geek will be available in multis!
Me (reading the email subject): CWs mini CoC tournament
But, yeah I hope this format will be successful and quoting Thibaud:
an opportunity for the community to meet at a certain moment and have fun with a certain language.
If people say Java is not a golfing language because it is more verbose as others, that it irrelevant when you compete against other Java solutions. As always in golf, there are still tricks both in algorithms and in syntax that can help you save the few characters that will help beat the competition. You could perfectly well golf in COBOL as well (when is COBOL coming to CG, by the way? )
Any language is/can be a golfing language. Especially when everyone is stuck to the same one.
That doesn’t take anything from the fact some languages are a lot less fun to golf in. Or from the fact there is no opt-out from golfing clashes, despite numerous requests. (ironically not from me, since I usually consider clashing a polyglot activity, but hey I’ll take arguments where they are)