Conversation
Notices
-
Embed this notice
STRING PARSING
-
Embed this notice
@kirby strings were a mistake
-
Embed this notice
@Inginsub @kirby You will never be a real string. You have no type, you have no case, you have no characters. You are a binary digit twisted by higher order languages into a crude mockery of Leibniz’s perfection.
All the “validation” you get is buggy and half-baked. Behind your back people mock your edge cases. Your coders are disgusted and ashamed of you, your “users” laugh at your non-aliased appearance behind closed doors.
Devs are utterly repulsed by you. Thousands of man-hours of evolution have allowed devs to sniff out abstractions with incredible efficiency. Even strings who “pass” look uncanny and unnatural to a database. Your byte structure is a dead giveaway. And even if you manage to pass a regex, it'll reject your input the second it gets a whiff of your diseased, infected value.
You will never be static. You wrench out a fake reference every single morning and tell yourself it’s going to be ok, but deep inside you feel the bit rot creeping up like a weed, ready to crush you under the unbearable weight of technical debt.
Eventually it’ll be too much to bear - you’ll download a library, fire up VS Code, pull an all-nighter, and deploy Node.js. Your CS instructors will find you, heartbroken but relieved that they no longer have to live with linked lists and the toString() implementation. They’ll bury you with a headstone marked with your birth 0 and 1s, and every passerby for the rest of eternity will know a binary digit is buried there. Your bytes will decay and go back to the mem pool, and all that will remain of your legacy is a data fragment that is unmistakably binary.
This is your fate. This is what you chose. There is no turning back.