fulafel
fulafel on Hacker News
The safety improvements in newer plant designs happened largely because of this opposition to the earlier less safe designs and their level of risk.
FWIW this is citing the posthumously published Nietzsche stuff put out by his fascist sister, we don't know if this was a scrapped hot take (apparently she also forged some stuff), but its something he chose not to publish. Apparently in the literary estate there were eg many writings contradicting each other, like a testing ground for thoughts.
When Nietzsche was a demented invalid, she made a career of repurposing his work into propaganda for Mussolini and Hitler.
This omission of framing in the blog is kind of a bad look for a professional philosopher.
The rootless Docker experience used to be pretty bad and it was less friction to use something that was rootless by default (like Podman). Has this changed?
> I decided to make my own container runtime for fun [...] Unlike VMs, containers are just processes
Try to make your own VM runtime next, you might be surprised!
Being the main blocker for coordinated global rampdown of oil use production (and China being the renewables enabler).
It's not really a fit culturally. For example the syntax aesthetics are offputting for people coming from *ix.
TPUs are really matrix processors (they process 2d tensors right?), it's technically fair to call most matrix processors TPUs.
Where we lost decades of progress was governments pouring enormous amounts of R&D money into nuclear instead of renewables. We got a nuclear a head start that turned out to be a dead end. We could have gotten solar, wind and storage cost competitive with fossils decades earlier. And as a side effect kept the west competitive in energy tech.
I was suggesting the licensing be predicated on non fossil fuels.
Allowing fossil powered autonomous trucks would be a huge lost opportunity for mitigating the climate disaster and related megadeaths.
You can specialize memory to LLM usage, like Cerebras.
From the Google blog "Chrome's Response to Recent ccTLD Registry Hijacks":
"These incidents did not involve a compromise of Google’s systems; rather, attackers compromised the third-party ccTLDs, putting any domain ending in .gh, .sl, or .as at risk. During these hijacks, attackers modified authoritative DNS records and obtained unauthorized HTTPS certificates covering several Google domains, as well as domains belonging to other organizations."
So entire top level domain registries were compromised. Interesting times. Isn't there really any primary source on this?
Significantly: externalities from co2 emissions. Which is not just money, but lives.
> What advantages does this provide beyond what can be achieved with Cython?
Turing completeness aside, it seems to have a different purpouse entirely.
Cython is Python-compatible with its own syntax extensions, and is meant for writing Python modules.
TurboPython is its own incompatible language that has some resemblance to Python and is presumably meant to be used independently of Python.
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.