You must not live in the US or have very odd patterns, I'm positive a majority of the US population have free credit monitoring due to the multiple SSN data leaks.
You're right and I struggled with the idea to add more in the first post, but I've decided to leave the more interesting stuff (Functors!) for the next part.
As far I understand, the difference is that in OO you normally transform data as you jump from layer to layer, here what do you have assembled is a simple program that will be interpreted by the lower layer
But then, "copy the style elements of classic designs while ignoring the rules that governed those designs" will make it automatically bad, and IMHO many aesthetic trends started like that
Exactly my thoughts. If we give FLW, modernist, and postmodernist architecture a pass on those criteria... why not to the McMansions? After all, they weren't designed in the 19th century... The problem might be the lack of coherent design, the cookie cuter approach, and the cardboard construction, but I don't really buy this critique ...
But category theory has direct application to programming: (ignoring non-termination), types and functions form a category and most of the concepts are directly applicable. Functors/map are of everyday use and other CT results are commonly used.
Even JavaScript is getting functional, so CT is getting more relevant and practical everyday
> Frankly, I'm voting for Trump because the working class desperately needs a pay raise or I'm afraid we'll eventually have a revolution. Moreover, I think the income inequality is what's driving our general economic malaise. We need to improve the job prospects of the working class for everybody's good.
But that's an argument to vote for somebody on the left!
For 1 and 4, is not for runtime exceptions (div by 0, out of memory, etc) that you need to bubble up to the top, is for "logic"/checked exceptions where you want to use code to deal with the failure case.
For 3, that totally defeats the purpose, the whole point is to have a single error type (it can capture the details of the error anyway) then you can have
If you consider subtyping, Bottom is a type
IIRC, In the category with types as objects and subtyping relationship (a->b if b is subtype of a) as morphisms, Any is the initial object and Bottom is the final object of the category
sure, that doesn't really help the low skill domestic labor pool (and the lack of a social security net makes it worse in the US), but in some cases, it might help the economy overall (at the expense of the low skilled domestic workers) e.g. in your example, by reducing the inflationary pressure of the minimum wage.