fulafel

Many are actively harmful (fex. bringing about the climate catastrophe).

Directionally correct, but rather: the process moniker became disconnected from the feature size.

Sounds like they controlled for it: "The researchers then examined mortality across occupations, separating out radiation-related and non–radiation-related cancers"

Current state of the art in feature sizes is 20 nm metal pitch / 45 nm gate pitch.

Did anyone at and point say it's technically impossible? There's been computers in space since the 60s after all.

It's just far out research experiment like another commented quoted from the text: https://news.ycombinator.com/item?id=49834746

You can use Pyodide for that, no need to stoop to JS.

Github personal access tokens are security footguns. This is an apparently old and forgotten image containing a token from 2023 and it the token gets you admin acces to their repos.

Broadly it's true that historically there was this idea for ethernet networks at least. It was always optional though. Even in that long obsolete rfc2464 it's described as the way to do SLAAC which was optional even in 1998.

This kind of thing doesn't normally count as violation of layering though. In protocol design its common to leverage identifiers from lower layers for addressing. For example many workings of the internet would be hard to imaging with the rule that you could not use IP addresses and ports in upper level protocols (like DNS, P2P protocols, etc)

CGNAT makes all ISP users appear to come from one v4 address, so blocking by v4 address becomes unworkable.

Apparently it's not good to require the router to start a new multicast address resolution on seeing unknown sources. It could be spelled out more but the text "This is particularly relevant for anycast and proxy addresses, where more than one node may be capable of responding" says that in some circumstances a lot of link local addresses might correspond to a single global address, and there could be a lot of traffic generated. So it's better to have the host opt-in to the prepopulating of the STALE entries.

"STALE allows the router to use the information it has already learned without requiring a new multicast address-resolution operation. The router can subsequently verify reachability using the normal Neighbour Discovery mechanisms."

edit: actually the RFC goes over this option as well and the reasoning there is slightly different than above (and maybe even the blog post) - see 8.9 at in https://datatracker.ietf.org/doc/rfc9131/ . Also notable that the RFC is from 2021.

I'd argue most people would consider it scheduling only if there's some attempt to arrange order of execution to improve throughput. Idling the other execution units when they could be executing instructions is not scheduling, at least not good scheduling.

In estabilished computer architecture terminology, scheduling is decidedly a OoO execution term. (At least if you're talking about processors. There's also static scheduling, which means the compiler does it and the hardware doesn't.)

Transparent scheduling of superscalar execution was a later advance in microprocessors, termed out of order execution. Apart from micros both did come out around the same time in the mid-1960s.

In the x86 microarchitectures superscalar came in Pentium and OoO got introduced in Pentium Pro.

(Superscalar is just having >1 pipelines, which at its introduction meant needing to manually schedule your code very carefully to take advantage of it absent the OoO execution. For example the frequently posted-about Doom optimizations and talk of the u and v pipes are about this. The scheduling didn't happen transparently in early superscalars, at best the cpu automatically stalled, and some archs (eg MIPS, i860, TI C3x) even visibly punted hardware detection of pipeline hazards and required the code to just not go there, see load delay slots and branch delay slots. )

What browser are you using an what does the back button do for you instead of going back?

Population-weighted, the country is more European (80% of pop on Europe side). That 80% counts towards population of Europe.

Seems incoherent. What exactly is the bad idea and why? Are they rediscovering "don't run stuff needlessly as root"?

128k tokens is about 12-20k lines of code/prompt right? Or more than an average novel. And you don't need all the source code or entire files in the context after all.

I wonder what the approximate context window of a human programmer is... less than 12k lines I'm sure.

Isn't context size one of the central motivations of the whole agent / orchestration business - fanning out increasingly detailed work to a tree of subagents. Orchestrator vs worker, hierarchical multitier trees, etc.

I guess this smaller context but faster llm engine could be good to develop your harness on to get faster results and faster iteration.

There have been recent attempts. Apparently not.

What are the best benchmarks/leaderboards that compare task completion time between provider+model combos?

Yes it's chronological but no it doesn't have unresolved items nearer the present:

The last 5 ones in the list read "Wrong" and seem reasonable. The first thing after the list is "After this point, most further predictions that I saw were either non-falsifiable or resolve in the future".

I thought in the post Ed was being evaluated based on all his predictions, and it turned out all of them were wrong.

Most people will read the post as going over all the falsifiable predictions and none of them panning out, since after the chronological prediction list it says "After this point, most further predictions that I saw were either non-falsifiable or resolve in the future".

If Dan is reading maybe he can clarify?

Data retention still sounds bad: "Claude Fable 5.1 and Claude Mythos 5.1 carry 30-day data retention and aren't available under zero data retention unless expressly authorized by Anthropic."

Anyone know who the ZDR special treatment is available to?

Can you run several MkLinux kernels (one concurrently with a Darwin kernel) at once?

Also several other places: https://en.wikipedia.org/wiki/District_cooling

Async ruins everything, as usual.

It has been a prominent "next major shift" idea in computer architecture since the 90s, to deal with the memory wall. Eg David Patterson advocating it in the 1990 and 1997 articles. or CRAM [1].

[1] https://www.eecg.toronto.edu/~stumm/Theses/Elliott-PhD98.pdf

What % of global electricity production is in too small markets? Seems to be working well in EU at least, markets and grids being multinational.

I'd guess many places in Africa could be potential markets that have underdeveloped grids but growing economies and populations. Hence the SMR industry in South Africa since the 90s I guess.

Where are their users coming from? Besides the few manually putting 1.1.1.1 in their settings.

And IPv6.

Microsoft has many products that people hate but are still the reason why they exist (eg Windows, Teams, Sharepoint etc).