> Java's reliance on traditional OO means that only a small subset of business domains naturally map to the language's constructs.
In my career I worked on a really wide range of business domains and have not even noticed the problems you are talking about.
The problem of mapping certain types like unsigned int that you mentioned is rather rare integration scenario. There’s not that many domains where numbers with the most significant bit are important, but MAX+1 size numbers are not.
> In my career I worked on a really wide range of business domains and have not even noticed the problems you are talking about.
How many other programming paradigms have you explored in depth and built solutions with?
Back when I did OO in Java and C# I didn't think twice about it, converting things to an OO paradigm was second nature, but once I stepped outside my comfort zone and learned of other modeling techniques, I realized that I had been jumping through extra hoops to get to where I wanted.
In my career I worked on a really wide range of business domains and have not even noticed the problems you are talking about.
The problem of mapping certain types like unsigned int that you mentioned is rather rare integration scenario. There’s not that many domains where numbers with the most significant bit are important, but MAX+1 size numbers are not.