Then you aren't paying attention. It's heavily used for money laundering and dark purchases. Yes the ledger is public, but there is almost no verification of the principals. It's nearly completely anonymous if you aren't a complete fool in how you setup the shells. Anonymity is the core of high volume laundering. You should do just a tiny bit of research of you think most of the major cryptocurrencies aren't massive laundering vehicles.
It's almost like a for profit health care system creates a bunch of really bad downstream effects that are a net negative to the total long term economy.
So your response to him pointing out that the author talks in absolutes, and tries to shit on any tech he doesn't like...is to talk in absolutes and shit on tech you don't like, with little jabs and dumb in jokes? Very convincing.
Read my comment again and you will notice there's not a single comment against or in favour of tech. Not even an adjective next to tech, only to people.
The comment is exactly that some people can't tell the difference between two completely identical techs, just because they buy the marketing of one of them, despite it being a brand on top of the first.
Perhaps I'm misunderstanding your point, but hasn't AMD proven this wrong at this point? With a correctly architected interconnect you can absolutely do chiplet based general computation processors.
Again, I may be misunderstanding your point...but I think the chiplet future is here on some level.
And I may be wrong, and for sure chiplets are proven (for now) to be a very good way of doing things, but those chiplets in AMD chips are relatively decoupled[0]. They're very large and connected within themselves already. They can be expected to operate substantially independently[0]. While they do have to talk to each other to get memory, probably a lot, DRAM access is so slow that it swamps the overhead of inter-chiplet communication[0]. Shared L3 cache, that's another matter I dunno.
I took it you meant like much smaller components, like ALU from this supplier, DRAM controller from that supplier, cache from another supplier etc, all on separate chiplets, each having to go off-chiplet to speak to the others. I am sure[0] that would cost much power and performance.
[0] serious risk of n00b arse-speak happening here, beware.
Not trying to be mean, but you really don't make any sort of case for doing this here. You just note you did it because you've become more comfortable with the front end. It also seems like you're designing and implementing an entire system by yourself in which case you can do whatever you want. When dealing with a team, and an API layer that has to be used by more than just your client, I don't see any compelling case presented here to start designing API's specifically for UX use cases.
The techniques are not mutually exclusive, it depends on the context.
When you don't have a clear idea of the requirements starting "front to back" helps to understand and gather them while building something that validates them.
For your example "back to front" sounds like a better fit.
That's not true at all. The Spanish flu outbreak had a ton of impact on the modern world. Health codes, science around vaccines, economic effects, etc. To act like the Spanish flu had no long lasting effects shows you didn't pay much attention in middle school social studies.
I didn't. But it doesn't mean the books did it justice either. Anyway, I was trying to illustrate GP's point of getting back to normalcy, albeit vaguely.
