Stackless are very lightweight and can be done without stepping outside of C code, but it's a bit hacky, using either macros or generating the coroutine yourself. One big limitation is you have to yield from the originally called coroutine function and not from any function it called (because the coroutine has no stack of its own, but you could work around this, with more complexity). So besides the function and the memory required to save its local variables when it yields, no resources are required. These are great when you just want a basic generator or something. It's simple, platform independent, efficient and you can do it yourself (at least in C).
Stackful coroutines are more flexible in that they don't have the calling limitations since they have their own stack. The big downside is that they are much more complex to implement and use (understand). The code has to create and destroy stacks from scratch and switch contexts by saving and restoring the correct registers (so your platform has to be supported explicit). This may cause compatibility problems with some code. Those activities also require more resources, but still not very much. For some people they will be easier to use since you don't have to roll anything yourself.
That’s mythology: executives have no such obligation to either shareholders or the board because business decisions are very rarely unambiguous wins or losses, and a great deal of discretion is given to their judgement over any non-trivial timeframe.
Consider, for example, the number of people who thought turn of the century Apple should become a Windows reseller or, later, sell the iPod brand to a business which understood how to be successful in the phone market like Nokia. There were certainly times where that could have generated a great deal of short-term gain, and it was easy to find some analyst prattling on about why they had to do it.
In the case of Spotify, the only situation where 17% of their company is an unambiguous waste of money with no benefit to the future business should be accompanied by the CEO’s resignation because that would be an enormous managerial failure in the hiring process. Since it seems unlikely that even 1% of their workforce is that bad, it’s far more likely that this has nothing to do with long-term success and everything to do with pleasing the activist investors and consulting firms who’ve been pushing the idea of layoffs as a way to remind workers not to ask for more.
No I don't think a lot of Europeans wonder that. On the contrary I think most of us know pretty well which priorities we have made and the effect they have on our economy.
How well does it work for non-English languages? I just tried it out for Swedish and had issues finding relevant results, especially searching for things like restaurants or hospitals.
In my experience from Denmark it is not great at the local results. However I don’t experience many problems with the Danish language. It is mostly stuff like if you search for some generic term that exists in both English and Danish. Then you might want the local one. This does not work very well.
But adding stuff like site:dk helps.
