Re:In MySQL, use “utf8mb4” instead of “utf8” (2016)
by dimitrios1 on Wednesday January 12, 2022 @03:05PM
(#29912066)
It is perfectly reasonable to continue to use EOL software, but you have to assume maintenance costs in that case. It would be irresponsible to continue to use EOL software as is. EOL is a perfectly natural concept. Nothing in this world lasts forever, including our machines, electronics, cars, batteries, lives, and yes, software.
[ Parent
| on HN ]
Re:In MySQL, use “utf8mb4” instead of “utf8” (2016)
by rkagerer on Wednesday January 12, 2022 @05:49PM
(#29913849)
If software lasted a lifetime, life would be so much easier.
Re:In MySQL, use “utf8mb4” instead of “utf8” (2016)
by kortex on Wednesday January 12, 2022 @07:36PM
(#29915156)
For the end user, not the maintainers. Who's gonna sign up to keep that ENIAC, PDP-11, ALGOL 58, python2.3, win3.1, etc, code running, stable, and not a source of exploits?
Or do you mean in the abstract, fairy-tale ending sense?
Re:In MySQL, use “utf8mb4” instead of “utf8” (2016)
by dimitrios1 on Thursday January 13, 2022 @03:00PM
(#29926007)
I think they meant in the tongue-in-cheek sense.