Как вы можете видеть в моем профиле, однажды я был синим.

Это было 7 лет назад, я стал старше, у меня появилась своя семья, у меня нет времени на тренировки как раньше. 7 лет назад соревнования по кодированию были намного проще, но я никогда не буду использовать это как оправдание для того, чтобы не практиковаться.

Я люблю сюда приходить, потому что это место не дает мне лгать самому себе. Я могу снова стать синим, или нет, это не важно.

Language statistics on the latest div3 A problem show that around 85% of people are using C/C++ here.

This is INSANITY! You do not need C/C++.

Statistically speaking you will never reach div1 where using a really really fast language can make an edge. Statistically you can (by definition of elo) NEVER have the problem of language choice here.

Have you not noticed that all editorial solutions in your division are in the slowest language (python3): https://codeforces.me/blog/entry/120165

What is worse, using python3 in div2 and div3 gives you an advantage, because it is a simpler language, and code is shorter to type and easier to understand.

Look at this list of language popularity and think about it.

And if you must have a fast language using Golang or Java is both easier and more job profitable than C++.

Disclaimer: This ofc does not apply for people working/seeking a job in industries that require C++. And ofc this does not apply to you specifically, because we all know you are the future legendary grandmaster.

This is not why you are here, you are here to improve.

It does not matter even if 10000 people got ahead of you in a contest because they cheated.

It only means that your true level is HIGHER that much.

In the real word and in the long term, it is you who will win, and the cheaters will forever be at the bottom.

Problem D in recent div3 contest uses lcm function.

This function exists in math library in python 3.9 but NOT in codeforces python 3.8

It is of course easy to define it with gcd function: lcm(a, b) == a * b // gcd(a, b)

While golang got generics in 1.18, the standard library was lagging behind in implementations.

Example: package slices does not even exist before version 1.21. It contains such functions as generic Max, Min, Sort, BinarySearch, ...

Golang 1.19 vs golang 1.21 library is like comparing C and C++ libraries.

Thank you for your hard work MikeMirzayanov.