Post number #704402, ID: e9847d
|
use utf8mb4!!!! why would anyone even use utf8 nowadays
Post number #704416, ID: a72f3e
|
>>704402 utf8mb4 can eat my fucking shorts. Unnecessary bloat.
Post number #704428, ID: 90747a
|
I think each language should have it's own encoding, and that software should be configured to handle multiple encodings. Consider someone who often uses armenian and serbian, but no other language. Obviously only one national encoding won't suffice, but unicode is overkill.
Post number #704435, ID: a72f3e
|
>>704428 Handling multiple encodings is gonna be a PITA to manage, though. Especially if your app is used internationally, how do you know what encodings to use? Or do you just add new ones constantly when the demand appears? Maybe I just misunderstood you, please elaborate.
Post number #704695, ID: bbbceb
|
Please for the love of burg, do not listen to OP. Just keep it all the way it is.
Post number #704707, ID: c0f596
|
>>704695 Do you really think that using a fucking DEPRECATED character set is a good idea?
Post number #704787, ID: 175d64
|
>>704783 No. Fuck pref and his 3-byte utf8.
Post number #704813, ID: 59df57
|
>>704787 Fuck yo/u/ instead.
Post number #704818, ID: 1b693e
|
Just use ASCII Anything else is bloat
Post number #704821, ID: 2953ee
|
Only allow dots, dashes, forward slashes, and spaces. We shall communicate via Morse from now on. Anything else is bloat.
| use utf8mb4!!!!
why would anyone even use utf8 nowadays