Sorry, but most of us need to work to eat. This idea that our "value" is has nothing to do with the economy is an idea rooted in deep privilege, in the ability to say -- if I don't like my job, if I'm not employable, I can just retire, and the only problem will be figuring out how to live life afterwards.
Many devices are indeed locked down. But given that it's an OS company and hardware vendor, many employees have access to hardware with e.g. SoC fusing that allows them to install custom-signed firmware. It's very difficult to make an OS lock out the people whose job it is to build the platform that OS depends on.
> We would still sometimes treat for varroa, but making it easier for the bees to handle varroa how they had evolved to was the first line of defence
I thought this was very dependent on the species -- European honeybees did not evolve to deal with varroa mites, because the mites originated in Asia. Asian honeybees, and honeybees bred with them, do have better ways of dealing with the mite; you said regular Italian bees, were they really not hybridized?
I don't have any actual field experience here, just curious!
I've always had mixed feelings about Cognition. Obviously they have some very, very smart people working there (I even know a few), and they do make real products. But at the same time, they've made suspicious marketing claims more than once and even been caught making outright fabricated ones; and while they certainly seem to have shaped up from that, I still find their claims to be in a sort of grey area where they seem to avoid unfavorable comparisons and lean on their own benchmarks. Certainly when I've tried their models they have not been nearly as useful as comparable versions of Claude, GLM, etc. -- though I haven't had a chance to try SWE-1.7 yet.
If you keep studying econ you will learn that these failures are actually the norm, and thus why the only "capitalist" states to really succeed have been the ones where the state was strong enough to reign in the market.
Of course, such a state of affairs is temporary at best -- since the alternative is so lucrative!
> while the large slowdown is justified because it allows people to use existing C applications unchanged instead of rewriting in a safe language (never mind that these two claims contradict each other)
Those two claims don't contradict eachother. Many, many people use C code not because their application needs to be blazing fast, but simply because the programs are already written in C. Rewriting a program from C into another language is likely to introduce a lot of bugs, even if the rewrite does manage to achieve 'full memory safety' (which most don't, instead liberally utilizing unsafe blocks or the equivalent). So what are such users to do, simply accept that there are going to be bugs? Fil-C seems to address a reasonable need.
I want to put this charitably, but you come out swinging by saying this is "over hyped"... You clearly don't work in a role dealing with attacks from these models. They've changed the game, and for the worse. Capabilities that used to be available only to nation-state attackers are legitimately commodified, or nearly so.
No, that's not the point. This isn't a situation where you need to "guess"; bloom filters should be sized according to their capacity. This is akin to having a fixed 10-arg buffer for your program, getting a crash when someone passes 11, and saying "this is the kind of bug you only find by building the thing and measuring it". Yeah it happens and we all make silly mistakes, but it's just not true that this couldn't have been foreseen.
ML compilers in particular go beyond even the level of stability you would expect from numerical programs. Due to how the SIMT model of thread/warp divergence works, the hardware heavily punishes unstable branches. E.g. if you have 32 threads taking a branch then recoalescing on a barrier -- if they all go the same direction then they can go down the execution pipe as a single bundle, but if 1 takes it while 31 don't, then that's 2x the ex-pipe usage by default (and if you have e.g. a computed-branch, performance goes out the window). Consequently, the whole stack is built around the expectation of stable control flow, even to the detriment of performance (from a local perspective).
ML frameworks even take advantage of this to compute, ahead-of-time, how much memory will be used at different points in the program graph, and thereafter schedule memcpy's to make space as necessary. Of course this only works for well-behaved program classes, but e.g. most LLM architectures fit into that category. Interestingly MoE models don't, since they require data-dependent control flow, thus the recent push towards accommodating dynamism in frameworks (like JAX, which until ~recently couldn't handle it at all).
It's not an agreement but it is indicative of the company's position. Why do you go to such lengths to avoid assigning responsibility to a large corporation?
Hate to be a pedant, but that's really not what "zero cost abstractions" means. The idea behind those is that you get a cleaner interface to some gross machine functionality/OS API/etc. layer, but don't pay a performance cost vs. using the gross lower-level layer. E.g. Rust's Option, unlike C++'s std::optional.
What you're thinking of is "no runtime" or "lightweight runtime", which does often mean "no garbage collector".
Capital doesn't care about whether your work is "inherently valuable". That you think poor countries are somehow fundamentally different in this regard, exposed to the downsides of the market in a way that we here are not, is a defect of imagination.
It's possible that oil traders are still trading on the assumption that the war will be over Soon™, in which case the expectation is that we won't hit the bottom of our stockpiles and thus there'd be no reason to price in that eventuality. I don't know if I agree with that, and I would certainly be surprised if traders generally thought as much -- but who knows!
> AI represents a unique opportunity to enjoy a two-for-one special and both cut staff and portray themselves as leaders in the sector that's achieving massive efficiency gains.
This is not what a scapegoat is. Definitionally, a scapegoat is innocent; here, however, AI is being used as a tool of disciplining labor.