The reasons are the same. They described them very well and I have nothing to add so far.

Olen samaa mieltä kohdan 1 ja motivaation kanssa.

Kohta 2 olisi myös minulle parempi, mutta toisaalta ylimääräisten sanojen aiheuttama harmi on hyvin pientä, ja liika valinnaisuus käyttäjillä aiheuttaa kasvavaa työtaakkaa ohjelmoijille. Niinpä ehdotan, että vaikka tiiviimpi käyttöliittymä olisi mukavampi, ei ehdotus kaksi luultavasti ole pitemmässä juoksussa toteuttamisen arvoinen.

Just to be clear, I was not asking you those questions in defense for keeping the new design as it is. We will always try our best to provide the best possible user experience for everyone. But to do so, we need to understand how people use Tatoeba.

Users tend to go straight off saying "I would like things to be this way" or "Is is possible to implement this", but that is not helpful to us. We don't make changes just because someone prefers things to be a certain way.

Unless you are a trained UX/UI designer, you will not necessarily think of the best possible solution for a UI problem. You will suggest solutions based on your own habits and your own biases and the things you suggest may have a negative impacts on others without you realizing it.

The best thing you can do to help us provide you, and everyone, the best possible user experience, is to describe how you use Tatoeba, a little like you are telling a story. You can always provide a solution, but without the story behind it, it doesn't help us figure out the best course of action. That's what my questions were aimed to do: to extract this story.

Now more concretely, you shared this bit of story:

> I've stumbled upon some real gems there a few times, something
> I would have never found if I was trying to search for something.
> I would occasionally translate them. Now it works super weird - I add
> 3 Ukrainian translations out of habit, only to realize 20 seconds later
> it already had Ukrainian translations, they were just hidden.

So this is useful information to me. It is a lot more useful than hearing you say you want to be able to have all translations expanded by default.

It explains why you prefer to have the translations expanded and it also explains why you prefer to have a more compact design. And it helps me understand where precisely are the problems.

Now what I can say is that having the translations expanded by default isn't great if you have tons of translations. The more translations, the more effort for you to spot the existing Ukrainian translations.

For that specific problem that you described, a better solution, in my opinion, would be that whenever you select the translation language, it displays the existing translations in that language.

Having all translations expanded does solve that problem but it is not a solution that will scale in the long run. It works only because at the moment, most sentences don't have more than 10 translations.

But one day, if Tatoeba continues to grow (which I hope it will), we may have 100+ translations on the majority of the sentences, and displaying them all is not exactly usable. There's still time until we get to that point, which means if expanding all translations is the cheapest solution, we can still go for that solution. But that shouldn't stop us from trying to figure out better ones.

For instance we could make an option to allow users to choose how many translations are displayed by default. We chose 5 arbitrarily, but some people like you may need this limit to be higher, perhaps up to 20 or 50 even. We have a similar option for the number of sentences per page (we chose to have 10 by default, but users are able to increase it up to 100). I think that would be longer-term solution than keeping the "expand all translations" option.