There is a certain amount of capacity to produce memory. They are building new facilities but it takes a long time. They have been burned going down this route many times in the past (e.g., losing money, firms that are no longer in business).
FWIW, what you will see at times in the HF world is a firm will want to get into a strategy and build competing teams. It lights a fire under both. It diversifies the risk. You can select winner and move some people over from loser. And if they both work, they both work.
It isn't a crazy idea if the opportunity is large enough to make the larger investment required worth it.
The problem I see in applying this to products is it can be very confusing for clients.
After you wrote this, I went and read the article I also didn't see much there either. And wonder why you are getting down voted. And TBC, also not a tesla fan (the truck is dumb).
Perhaps if an ETF holds similar underlying instruments. It is unlikely this impacts Blackrock more broadly or other unrelated ETFs.
Stepping back, the idea with private credit was to move a lot of lending and credit risk taking away from the banks. Because if the bank fails, then it causes risk to the financial system. If a private credit fund does badly, you have sad investors. But the broader financial system is not imperiled.
And there will always be periods where credit does badly. It is the nature of these markets and lending.
TBC, I think the private credit guys got over their skis over the last 5 years and we'll see some sad investors in the next few years.
I'm a long way from embedded development. But I was under the impression a lot of microcontrollers these days have some ID capability built in, even some relatively low-end ones. This strikes me more as laziness than anything.
This is true, for example many stm32 series have a 96 bit unique id which is derived from the lot number, wafer id and position [1]. Even the low cost stm32g0b1 series I am using has them, but they are missing from some older series.
Moreover, on any device that is connected to Internet you already have a unique MAC address on its Ethernet or WiFi interface.
You can hash this unique MAC address, together with other data that may be shared with the other devices of the same kind, to generate unique keys or other kinds of credentials.
Surprisingly it's not everywhere. I'm very in embedded development and cannot count the amount of time I look for "unique" "id" etc in a reference manual and come up short. It's certainly more common than not, but you often have to design systems for the lowest common denominator.
There is a certain amount of capacity to produce memory. They are building new facilities but it takes a long time. They have been burned going down this route many times in the past (e.g., losing money, firms that are no longer in business).
What would you have them do instead?