> with UTF8 by default, or some near equivalent of it (utf8mb4?)
And you are contradicting yourself by proposing two defaults at the same time.
So 5 years from now on someone like you will complain the wrong one was chosen.
Neither HTML nor table/db/schema encodings are part of the language and magically changing their settings/headers would not only require new modules and procedures.
(Not sure if CGI.pm is even actively developed anymore.)
It would also mean magically overriding the configs of the Web/DB servers.
> I don't think it's a stretch
Well, who else thinks like you?
Which language does it like you propose?
|