A constructor can't be async so now I need to restructure my code to use async factories instead of constructors
It sounds like you’re trying to do OOD/OOP. In js that’s usually not the way to go. You might want to restructure into a more functional architecture anyway.
From browsing your other comments on this thread I understand that you are in a context where you can’t await, that you expect the invocation to take very little time, and that the library offers no complementary sync interface.
As far was I know you’re stuck in this case. I consider the stubborn refusal to add “resolve this promise synchronously right now” a major flaw in js.
Unpopular opinion: the only vendor that does sleep right is Apple. The only reason they can is the tight vertical integration of the platform where they control all the hardware, all the drivers, and can exercise control over all the applications in the App Store.
The key here is “better performance at similar price points”. There are absolutely amazing 2.5 drives made for server applications, but they cost so much money you’re better off getting SSD these days.
Amazingly, no. I had to follow a few links before I found out because apparently the fact that she’s a woman trumps all the other news, but she is, in fact, not a fascist.
There’s some serious bad blood in the AI academic world between the old farts that toiled thanklessly all through the thirty years of the AI winter, proving all sorts of fundamental theorems, only to get steam rolled by (relative) newcomers with big tech backing the very second tech started catching up to the math.
Things got pretty heated with accusations of academic malpractice, and generic assholery.
Yann is one of the main participants in this drama. The other is a Swiss professor that is about equally friendly.