3,655 karma · joined June 23, 2017
The spec on your GitHub says: "Two simultaneously-live resizable values never share a stack."
So I surely can't have a dynamic array of dynamic arrays share a single stack? That's an unbounded number of resizeable values sharing a stack?
You could make it work on a single stack but that would involve having non-contiguous memory for each inner array since you can add to any array in any order.
The spec implies that we need one stack per element of the outer dynamic array which would let you have contiguous memory for each inner array, but you wouldn't know how many stacks you needed at compile time.
I'm a bit confused about how you could decide the number of stacks at compile time. I can see you could see how many arrays are lexically in scope. However if the code puts one dynamic array inside another dynamic array I can get to an unbounded number of total stacks without ever needing more than two in lexical scope at once. Do you also add stacks at runtime? Like a stack of stacks?
How are you deciding how many stacks to use?
Also I guess this is the final nail in the coffin of Tensorflow.
There was a time when CERN would have been establishing partnerships with US labs. The US is not a CERN member but has provided a lot of funding in the past despite it's observer status. These days funding is getting cut, the US is not as trusted as a partner anymore and a European partner is seen as important. This is sad.
That said I'm happy for Mistral and I'm sure they'll be a great partner for CERN.
It's perhaps a face saving thing to pretend you'll charge the same. Let's see if it actually happens.
Sam Altman is much more dangerous because he is occasionally able to come across as human.
The biggest differentiating factor seems to be compute. I know most Chinese labs would really like more compute. Google and xAI too, but largely because they sold compute to their competitors.
Knowledge has been available just by asking Google for decades now. The LLM makes it easier but it's a difference of degree not of kind
Until the models are 100% reliable knowledge will be required in order to quickly spot issues and work efficiently with the model to address them.
You are right that most work gets published in mid tier journals. These are still peer reviewed. The difference is that they have a lower bar for impact. The bar for correctness is still very very high however.
I am pretty sure that journal publication is the norm. I do know mathematics although I am not one myself. The mathematicans I know want/need journal publications as unpublished research isn't counted in their research output. I know Arxiv is typically used for preprints while awaiting review but publication is always the aim.
Don't take it from me though. zbMath did a study finding 60-70 percent of arxiv papers on math end up in peer reviewed journals. https://ems.press/content/serial-article-files/47210.
In fact we already follow exactly this process for human papers and have done for a very long time. Publications without peer review are treated with great suspicion. This is how we end up with journals of varying levels of prestige and rigour.
The process isn't flawless and there are huge problems with retractions, as well as weird financial incentives and rent extraction but there is definitely an increased level of trust in a paper published in Nature.
This can and should erode our trust in every single proof OpenAI published. The model is clearly faliable despite the lean proof, and clearly the output was't actually checked properly before release. Once these proofs are peer reviewed and published in a journal we might be able to trust them again but until then they are just slop, sadly.
I think OpenAI actually did the right thing by sharing everything with the whole community right now but I also hope that some significant credit will now go to the reviewers who confirm these 'proofs" actually work.
I played a few editors picks. "Westbound Frontier" is a kind of RTS. On mobile all the windows open on top of eachother and the text is very hard to read. The amount of resource required to build the first building after town hall was way too high by and you had to wait ages to do anything. There was an infuriating AI sound track singing "ooo-wee-ooo". 0/10 from me, broken and not fun.
Next I tried volcano run, a 3D infinite runner. Not my kind of game but a nice aesthetic and it actually worked. After about 30 seconds though the graphics changed to a really low contrast mode (night?) and I couldn't see the rocks I was supposed to dodge. 2/10.
Honestly genuinely a bit shocked Google launched this. It's obviously not ready, the "Editor" who picked these games should have known that. I am not sure if this is some kind of set of skills for Gemini or a fine tune or just a prompt but it certainly feels very low effort and embarrassing.
I'm not actually sure Tesla is a great company from any perspective so should be easy to find another sick burn for them.
Google is going to be a little more difficult. Maybe say something nasty about advertising? Or go for the monopoly angle.
A lot of European companies now want a model the US can't cut off, but also lack trust in Chinese models.
Some of these will self host Mistral but most will pay them by the token. It's not going to be a huge market or a huge margin within that market but probably it'll be enough.
Investors looking for them to make monopoly profits are going to be disappointed The premium they can extract from consumers for their models will be capped. Tokens are likely to remain close to the cost of compute, a cost which is high but falling fast.
Also, yay Europe! Although the comparison between this and mimo 2.6 is not flattering...
You certainly don't do it when you are just behind the frontier. Instead you wait until you are ahead on a lot of benchmarks.
So, if Google release a new frontier model, the chances it's ahead on most benchmarks are statistically about 100% because if it isn't yet then they won't release it.
The problem is the rendering is wrong. Gates which are connected to two distinct inputs according to the text description which pops up when you click on it are rendered as having both inputs connected to the same wire. It's a bit of a shame.