Stringly Typed

I learned a new software development term from Scott Hanselman: "stringly typed". Scott describes "stringly typed" as follows: [whenever] you are passing strings around when a better type exists. An application is "stringly typed" when type information is available, yet you're calling other systems or functions based on strings or stringified data. Unsurprisingly, most API calls are "stringly typed" because request and response bodies are often stringified JSON data. const response = await fetch ( "https://example.org/subscribe" , { method : "POST" , body : JSON . stringify ( { username : "..." , password : "..." } ) , } ) ; const user = await response . json ( ) ; JavaScript is a weakly typed language without much type safety, so the type loss wasn't a big deal for me so far. And because most APIs speak JSON, the possible types are limited to strings, numbers, objects, arrays, booleans and null anyway. We've all gotten used to this state of affairs, haven't we? Let's flip thing ... Read full article.