Nope, that's not how WoW works. It might feel close enough for you but if that's the case then you aren't careful enough with the analogies you make. Think harder, aim for more clarity.
If you read the article and considered the argument it makes, you'd see that, in fact, it is not redundant at all. This is indeed the point of the article!
From a data compression/language efficiency standpoint, both sentences in both languages actually rely on a (potentially large) amount of unstated context to sort out these ambiguities. In some languages, this context can be totally unspoken and merely known to both the speaker and the listener. This absolutely MUST be accounted for if a truly correct translation is to be made.
For instance, your assumption that the definite "the cat" is being used idiomatically like so: this sentence, used in the manner you offer, might be used in conversation might occur in a farmhouse somewhere between an old man and woman who have lived together in this house for a long time, i.e. American Gothic. There's a vast amount of shared information and a perception of very little ambiguity held by both the speaker and the listener (whether correct or mistaken!). Any of those might fail. Furthermore, to use this sentence in English unadorned by context requires that both the speaker and listener have a shared reference to _what_ cat is being referred to by the definite article, "the". This very well might come with an unambiguous default in other languages!
> Note: my file manager even identifies the mime type without extension. That is how it should be, changing the extension should not make the file harder to use. To this day, AFAIK, windows file manager still uses the extension to identify file type, thus allowing the user to easily change it may break expectation. GNOME's nautilus, KDE's Dolphin and even Apple's finder do it right: press f2 and you can rename the file without changing the extension, unless you go out of you way for that.
You've just confounded two different concerns: filetype identification by file managers and the interface to rename files. If you're not just cribbing some bad Intro to UX course, you'd know that Windows Explorer has always gone out of its way to howl bloody murder when you accidentally changed the file extension, and since Windows XP most rename file controls preserve the file extension. Your thinking was very sloppy here.
Identifying files by heuristics is a VERY dangerous game. Different systems have implemented it differently over the years, classic Mac OS in particular offering a fascinating alternative to file extensions.
> Also, once it is in the kernel, whoever change any internal api will fix every driver code to keep it working, so things that work once will work for a very long time.
Sometimes. Not always. Don't blindly worship code you haven't read.
> App Store/Google Play/Windows Store/macOS Store are not and never have been curated for software the user can trust, only things that do not harm the perceived interests of their owners. They are not trusted sources.
Amen. The proliferation of knock-off apps, shovelware and spyware was not the future we wanted but it's exactly the one we built for ourselves. If you explore this conflict of interest between users, OEMs and developers, you start to reconsider your enthusiasm for the whole cloud computing era.