I understand that to be the "emergent abilities" which are spoken about. There are correlations in the dataset that are strong enough for it to seem to have an understanding which wasn't obvious it would have from simply "predicting the next word".
Maybe irrelevant to your point, but I'd argue they were really good already in May if one used the right workflow (planning etc.). They've become better, but they're not saving me significantly more time now than they did 12 months ago.
Agreed, async function coloring makes for better structured code because it incentivizes keeping IO code near the edges while having a synchronous core.
I doubt it, the difference between someone slightly inefficient and someone extremely efficient isn't big enough to matter compared to how much they cost in salary.
That doesn't make it not true though. Markdown generally supports HTML (though oftentimes only a subset), and is typically styled using CSS. Using a web view makes complete sense to me.
> But are we really saying that the primary motivation for async/await is performance?
Of course - what else would it be? The whole async trend started because moving away from each http request spawning (or being bound to) an OS thread gave quite extreme improvements in requests/second metrics, didn't it?
I agree. Managing many http requests or responses was a motivating problem.
What I question is whether 1. Most programs resemble that, so that they make it an invasive feature of every general purpose language. 2. Whether programmers are making a conscious choice because they ruled out the perf overhead of the simpler model we have by default.
That is why we have the function colouring problem and a split ecosystem in the first place - if it were obviously better in all cases, we'd make async the default, and get rid of the split altogether (and there are languages, like Erlang, that fall on this side of the fence)
I haven't made a ESP32 design, but I recently learnt KiCad and PCB design enough to do a RP235x board with a non-reference design choice (1.8v VDDIO). I only used the official hardware guide + LLMs for questions, and had it work on the first try - it wasn't too hard!
But dependencies are part of a website? It literally says "Still here when the internet isn't." - but I can't go on there without an internet connection?
Service Workers can cough up this stuff even without a connection, provided you already visited the site once before. This is how sites like Twitter still load their bones even without a connection.
I use Claude for work and Codex for private use due to already having a Plus subscription.
I can't say that I have noticed that 5.3-Codex is much better, but it's definitely on par with Opus 4.6, and its limits for $25/months is comparable to Max x5 at 1/4th of the cost (not to mention pay-per-token which we use at work). Claude Code is generally a much better experience though.
What’s going to have the faster latency? Memory chiplets on the same substrate as the cpu cores or memory dimms sitting in a housing a few inches away?
I’m sure there’s more than a few factors making latency faster for those chiplets.
Edit-but I don’t think this question is about latency exactly. If you’re editing a large file that fits in 196gb ram all at once then those edits should benefit by apparently an order of magnitude higher bandwidth. It’s going to be able to address all of its ram several times per second while the i9 will take much longer (roughly). That and similar speedups from the whole systems engineering should make up some for not having more ram. Think how 8 gig of ram in the m1 was widely reported to be more usable than expected when announced.
Memory chiplets on the same substrate as the cpu cores or memory dimms sitting in a housing a few inches away?
Where are you getting this information on the memory latency? What is the actual number?
I don’t think this question is about latency exactly.
You were the one the brought up latency
those edits should benefit by apparently an order of magnitude higher bandwidth
Most software is not written well enough to be memory bandwidth limited, even graphics software. It is mostly games that end up actually needing the memory bandwidth.
reply