The problem some have pointed out is that these companies are such a huge portion of the market right now.
The sound advice for the past decades has been, just invest in a low-cost ETF tracking the S&P instead of picking stocks to minimize risk and invest in the market broadly.
So a huge number of people have done that, believing they're diversified, while tech makes up 40% of the index.
Yes you could sell your S&P and find things to invest in least likely to be impacted by a potential bubble, but your average 9-5'er with automated contributions to their 401k is probably not sophisticated enough to do that.
And that's assuming only these companies would be affected if there was a massive draw-down in tech/AI related stocks. We haven't really seen a situation like this before, so it's not easy to predict what effects there might be in the broader economy.
Couldn't it be a problem given the concentration of the S&P in these companies?
At this point these companies make up a huge portion of 401k's for a huge chunk of Americans. How would it affect retirees if they dropped 40-50%, likely taking the market with them?
If it didn't matter, why would they bother jumping through hoops to keep the debt off their balance sheet?
In the run-up to 2008 a big factor in the bubble forming was that poor quality loans were packaged in a way to hide the risk in those investments. I'm not expert enough in finance to know if it's the case now, but we do know that clever accounting to hide debt can lead to the incorrect valuation of assets, potentially leading to financial ruin.
Not only forests but even just tree cover. I live in Berlin and there were a few days a few years ago over 40 degrees, and I remember the difference was stark going from my relatively tree-lined street to an area of the city with only concrete.
I always felt unwrap is preferable for diagnosing issues, which makes it useful in tests. A failed unwrap will point you directly to the line of code which panics, which is much simpler than trying to trace an issue through many layers of Results.
If you use `assert` in tests, I don't understand why you wouldn't also prefer unwrap in this context.
I think it's also perfectly reasonable to use in a context like binary you run locally for private consumption, or for instance a serverless function which allows you to pinpoint the source of errors more easily in the logs.
It's not a good fit for cases where you do expect cases where the unwrap will fail, but it's a great fit for cases where you believe the unwrap should always succeed, as it allows you to pinpoint the cases where it fails.
Doesn’t rust’s static linking also have to do with the strategy of aggressive minimization? Iirc for instance every concrete instantiation of a dynamic type will have its own compiled binary, so it would basically be impossible for a dynamic library to do this since it wouldn’t know how it would be used, at least not without some major limitations or performance tradeoffs
I believe MS is trying to standardize this, in the same way as they do with DirectX support levels, but I agree it's probably going to be inherently a bit less consistent than Apple offerings
There was a rumor floating around that Apple might try to enter the server chip business with an AI chip, which is an interesting concept. Apple's never really succeeded in the B2B business, but they have proven a lot of competency in the silicon space.
Even their high-end prosumer hardware could be interesting as an AI workstation given the VRAM available if the software support were better.
I don't understand why you would need custom firmware. It seems like you could go a long way just implementing back-ends for popular ML libraries in openCL / compute shaders
I love the air form factor. I do serious work on it as well. I have used a pro, but the air does everything I need without breaking a sweat, and it's super convenient to throw in a bag and carry around the house.
I am honestly shocked Nvidia has been allowed to maintain their moat with cuda. It seems like AMD would have a ton to gain just spending a couple million a year to implement all the relevant ML libraries with a non-cuda back-end.
Molten VK is amazing. When I started working with it, I was expecting a lot of caveats and compromises, but it's shockingly similar to just using Vulkan that you can easily forget that there's a compatibility tool in play.
Probably you can squeeze a bit of optimization out of using Metal directly, but I think it's a more than viable approach to start with Vulkan/MoltenVK as a target, and add a Metal branch to the renderer when capacity allows (although you might never feel the need)
> It’s become “grind leetcode” which is clearly a failure mode.
I have no insider knowledge, but I always wondered if those kinds of cultures had a hazing / blind-leading-the-blind aspect to them. I.e. the people who got hired were the ones who jumped through some arbitrary hoops, so they doubled down on those hoops being the right hoops to choose the best candidates.