splawn
Joined 14 years ago
Joined 14 years ago
I understand the issue of mixing state models.. angular SPA style vs HATEOAS.
But that still doesn't answer what I was asking about mixing presentation concerns into business logic. Returning HTML means the presentation layer has to know about HTML. Why would that require the business logic to know about it?
Don't you have to maintain that separation either way? Your core/application logic shouldn't know how its result is ultimately represented. That could be JSON or HTML over HTTP, Protobuf over a TCP stream, or a custom binary protocol over a Unix socket.
Obviously those representations matter at the presentation/transport boundary, but why should choosing HTML force that concern into the business logic?
EDIT: added more specific description of what I liked about it, in an attempt to up the quality of my comment.
EDIT: I was just halfway joking when I made this comment (I vaguely knew that he sold supplements for body building)... However, I had no idea about the "Alpha Brain" supplement that he sells. And yes, the punchline is that he claims it provides "cognitive enhancement". And No.. there is no solid science behind it and certainly no doubleblind clinical trials. I only know to care about stuff like this from listening to other podcasts such as "This week in microbiology" and "Skeptoid" that perhaps did make me smarter. (at least I don't fall for supplement scams)
EDIT: Here.... let me google up an example. https://en.wikipedia.org/wiki/Great_Oxygenation_Event