- Feature Articles
- CodeSOD
- Error'd
- Forums
-
Other Articles
- Random Article
- Other Series
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
Frist of all, even valid UUIDs may be represented in different ways (braces, parentheses, hyphens) and not all of them may end up as 36 chars. Second of all, why not just parse the thing.
Edit Admin
What percentage of WTFs do we think are caused by stringly typed data?
Edit Admin
@Dragnslcr.
You beat me to it. ALL of this is due to using stringly-typed data as the main way we pass data from client to server. In an era when client-server and HTML is WAG 90% of the total new code space and much code is written in auto-converting typeless language whos value-handling reminds me of nothing so much as GW-BASIC with longer variable names.
Yes, there are libraries and protocols to abstract (some of) that away. Good luck finding one all your devs can / will use that will fit all your use cases, all your endpoints, and that you can count on still being there for the decades-long lifecycle of commercial software.
Edit Admin
Longer variable names (although GW-BASIC variable names were limited to 40 characters, not just two(1)) without the type suffixes... $ = string, % = integer, ...
(1) This was why the GW-BASIC parser didn't recognise keywords that weren't separated from variable names by a space on both sides. In
FOR I = Y*(X+1)TO-Z
, the space betweenFOR
andI
was necessary, but it wasn't necessary to put spaces aroundTO
.