C# has Task.FromResult(), which is useful if you are implementing an interface that allows async work but your implementation doesn't require it. I believe the runtime will check for this case and continue execution. It's better for the cache to keep executing the current task on the current thread.
I don't really understand gp's point. From inside the code, you can't tell if there was a pause or not. Clock time or thread id are heuristics, but you can't really be sure.
I took the analogy to be about the location of the pressure and not the direction. If you allow pressure to build on the input pipe when you can't accept more, the component that is upstream in the flow is able to observe that and respond. Maybe the difference is I envisioned a series of pipes and not a single one.
You mean the culture of cutting funding from under performing schools to enforce a downward spiral and divert money to private schools? If not you should be more specific.
Let's say that each month I have an extra $1000. Should I use that money to pay down a 4% mortgage, or should I invest it in an index fund that is all but guaranteed to earn more than that?
> that is all but guaranteed to earn more than that?
say SP500 nominal avg is around 10% - no brainer, yes? but that is an avg of many 30-year windows. some 30-year windows might not be that kind to you. market crash in say first 5-6 years will hurt you a lot
so there is just no certainty here except we think (just like we expect appreciation on the house) we’ll end up on the “right” side of this.
and of course not to mention the most obvious, roughly 99.56% of people will not be investing this money to get more than 4%…
Automated accessibility testing needs to be in your loop, whether you are using an llm or not. Aria labels are easy to get right but they are also easy to forget.
There are documented ways to ensure that changes are visible across threads (e.g. locks). If these are not used, the compiler is within its rights to not go out of its way to pull changes from another thread.
Right, it's pretty inevitable given the incentives. I think it's made worse by PE for a few reasons. They are investing with relatively short time horizons because they will need to sell to pay profits. So the long term health of the business is of no interest. If the reputation of the business suffers, that's someone else's problem. Compared to an individual investor who is looking long term, they need to retain customers and reputation.
It probably still sucks in C, but the C++ DX got a lot better. Importing the idl would generate wrapper functions that made calling code look much more like a normal function. It would check the hresult and return an out param from the function. They also introduced types like _variant_t that help boxing and unboxing native types. It still wasn't fun but it greatly reduced line count.
Nah, unless talking about C++ Builder extensions for COM, in Visual C++ land it still sucks big time.
For some reason, there are vocal teams at Microsoft that resist anything in C++ that is comparable to VB, Delphi, .NET, C++ Builder ease of use regarding COM.
Hence why we got MFC COM, ATL COM, WRL, WinRT (as COM evolution), C++/CX, C++/WinRT, WIL, and eventually all of them lose traction with that vocal group that aparently rather use COM with bare bones IDL files, using the command line and VI on Windows most likely.
I don't really understand gp's point. From inside the code, you can't tell if there was a pause or not. Clock time or thread id are heuristics, but you can't really be sure.
reply