Written by MiguelCall it an idiomatic react/remix/redux/node/Django (whatever context you have heard this term) application, you tell, If you are a developer, I know you have crashed with this term somewhere. Here is an explanation ( clear I hope ) of what this term means.
Let’s start with the word “idiomatic” itself, according to the Cambridge dictionary i is an adjective of something that contains expressions that are natural and correct.
If we take the words natural and correct as our baseline of what is something idiomatic, we can easily conclude that an idiomatic application is a software solution that was built following the core philosophy of the framework/language in which it was developed.
Let’s see some examples :
First, what is the core philosophy of react?
In a nutshell, the core philosophy of react is centered on the concepts of composition and immutability. A React developer creates UI’s by orchestrating(composing) units called components that follow the single responsibility principle and add interactivity (UX) by pushing new states to this components , making emphasys in not mutating states but instead pushing new ones.
Therefore, an idiomatic react application is an application that is built with components that have one clear function to perform and that hold a state that is not mutated.
Following the same idea of the example above ( react idiomatic application ) we need to ask ourselves, what is the code philosophy of Remix?
Beyond buzzwords, Remix bases its best practices on web standards(fetch, form actions, etc) and a fullstack data flow . A Remix developer creates applications by integrating UX and bi-directional client-server communication in highly cohesive modules ( routes files ).
In conclusion, an idiomatic Remix Appplicacion is an application that opts to use organic browser capabilities to provide UI/UX and takes advantage of JavaScript only to enhance user experience.
