Interesting initiative, too bad there is no english alternative with the same format (the linux parts are not that useful) since knowing mandarin is not that common.
Thinking is scary. No one (among non-thinking colleagues) is going to criticize you for using de-facto standard services like kafka, mongo, redis, ecc... regardless of the nonsensical architecture you come up with.
Yes, I also put Redis in that list. You can cache and serve data structure in many other ways, for example replicate the individual features you need in you application instead of going the lazy route and another service to the mix. And don't get me started on Kafka... money thrown in the drain when a stupid grpc/whatever service would do.
Part of being an engineer is also selecting the minimum amount of components for your architecture and not being afraid of implementing something on your own if you only need 1 of 100s features that an existing product require.
After this, the common ground can only be that they translate something else. Overriding human translations for some crap done with LLM that is obviously inferior... are they ok?
So, they had people working for free for years and didn't think to involve them in a process where they could have been stil "useful"?
But I think they already clarified how much they care about people doing translations since they defaulted to the robo-translation. Which to me is complete nonsense considering how superior the human translations must be. As a human with a brain, I would have just translated automatically the missing pages leaving to them the option of replacing/fixing them. Also they should have been thanked many times for all their hard work.
Like conspiracies, it works only on the most fragile and on people that already have an adjacent set of beliefs. AGI/ASI is all bullshit narratives but yeah, we have useful artifacts that will get better even if they never become A*I.
Like "parmesan" the cheap versions you find easily has no relationship with the actual thing, even if decades ago maybe the actual thing was initially imported with no local alternative.
The UI element is a scrollable table with a fixed size viewport window, memory shouldn't be a problem since they just have to retrieve and cache a reasonable area around that window. Old data can just be discarded.
Implementations varies, no one forces the third party to use message types 100% as intended.