Enough! JavaScript had us in its grip for long with its foot guns.

Immutability, the cornerstone of functional programming, has many facets.

Not every (mainstream) language supports all the facets; at least not per what each facet stands for. That’s what I will talk about today. The various facets of immutability from a theoretical perspective, and briefly show how some of the mainstream languages have adopted and support these facets in their own way.

A great deal of thought goes into language design. Eric Lippert’s posts is a living testament, at least for C#.

Earlier this year, I wrote about publishing C++/CLI Primer on LeanPub.

Problem Reduction is what I call when a given problem can be expressed in terms of or solved using a solution to an alternate problem.

Take for instance, the word distance problem: Find the shortest distance between two words in a given set of words. Following is an unanimous solution, I suppose:

semantics¹ | /sɪˈmæntɪks/ | noun (functioning as sing)

1. the branch of linguistics that deals with the study of meaning, changes in meaning, and the principles that govern the relationship between sentences or words and their meanings
2. the study of the relationships between signs and symbols and what they represent
3. (logic)
   • the study of interpretations of a formal theory
   • the study of the relationship between the structure of a theory and its subject matter
   • (of a formal theory) the principles that determine the truth or falsehood of sentences within the theory, and the references of its terms

---

Semantics is ever more important in programming.

A typical business application is composed of several flows or use-cases. Also, these flows consist of logical ones like a transaction that spans several flows. Take for instance an e-commerce application which consists of user registration/login, product lookup, and one of the most important interactions in an e-commerce application – the shopping cart, and much more. Although these application flows might appear to be discrete and independent of one another, it is after producing a working solution that we realize that these flows are inherently interrelated for one reason or another. The idea of designing stateless application flows is many times confused with the relation between the flows.

Yes, there is a difference. Although both produce the same end effect, an iterator is not the same as a generator. The difference is in the way it is implemented and also consumed.

New things are not always instantly accepted. Beyond skepticism, new things challenge the comfort people are accustomed to. JINQ wasn’t particularly welcomed. It was either discarded as unknown angel or worse … ridiculed. However, JINQ still promises expressive succinct code.

I am not a *nix commands expert … but a professional?