skysight-inc/HackerNews huggingface dataset:
CPU Single Thread Rating

Name pts Date
Intel Core2 Duo E7600 @ 3.06GHz 1,270 Q2 2009
Intel Core Solo T1350 @ 1.86GHz 413 Q1 2009
Intel Core Solo U1300 @ 1.06GHz 340 Q3 2009
Intel Atom D425 @ 1.80GHz 320 Q1 2011

These Atoms were quite gutted to have a low die size and low TDP, and the first things what were cut are cache and branch prediction. You can see how D425 from 2011 is on the same level as two year earlier and a almost a half GHz slower U1300.

> In the Bonnell microarchitecture, internal micro-ops can contain both a memory load and a memory store in connection with an ALU operation, thus being more similar to the x86 level and more powerful than the micro-ops used in previous designs.[3] This enables relatively good performance with only two integer ALUs, and without any instruction reordering, speculative execution or register renaming. A side effect of having no speculative execution is invulnerability against Meltdown and Spectre.

https://www.cpubenchmark.net/compare/948vs579vs593vs609/Inte...

https://en.wikipedia.org/wiki/Bonnell_(microarchitecture)
This is the video that got me to really understand the uncertainty principle 4 years ago.
> Users of the PyTorch stable packages are not affected by this issue.

But the packages they ask you to uninstall have the same names. How does one install the nightly package? If I just installed "torch" can I assume that I don't have the nightly version?
Sorry to mislead you; I don't work for a protection service but my company has had contracts with a handful of them and I've tested a handful more.
Women overinvesting in education? Evidence from the medical profession (2012)
> If we're going to be objective, technically the Chinese Communists are the greatest success for humanity

That ‘success’ came largely from western investment and western consumption, and at the cost of ~100,000,000 lives under Mao.
It's not memory bandwidth entirely. Modern superscalar Out-of-Order CPUs rename architectural registers with some number of physical registers to make larger OoO windows useful. To accomplish the same thing on a stack based architecture, you now have to rename memory addresses so that otherwise independent instructions can be reordered. The tags for registers are maybe 8-9 bits in a modern CPU, whereas full 64 bit tags would be needed for a stack based CPU (maybe you could get away with 48 bits on x86-64). That means more bits to compare in critical CPU blocks, which means more area and more power.

You could relieve that pressure by doing register windows (like SPARC or ia64) that aren't in "memory", and those architectures did have performance benefits for certain workloads (I remember working on i960 where interrupts were shockingly fast for the number of registers it had), but those architectures never really took any significant share of the mainstream market. Architecture matters far less in modern CPUs so long as it doesn't do anything that makes it "too hard" to build a good superscalar OoO core.

All that said, nobody has ever invested the kind of money put into x86 and ARM to make a stack based CPU go fast, so maybe the problems above are not insurmountable. But that's not the universe we happen to reside in.
The lakebed footprints securely scotch that timeline, and Cerutti blasts it to smithereens. The most that could be left of it is that these late migrations somehow wholly supplanted earlier populations.

Either the earlier pop. died out before the later crew arrived, or ... well, genocide is a demonstrated human behavior. It is hard to carry out continent-wide without microbial assistance, but they could have had that.
I just cannot even agree more with this. When I use Windows, I put FreeCommander on it at once. And File Explorer is far, far worse in Windows 11 than Windows 10. Finder is crap, but it makes sense, in the way that every other single-pane file explorer on Linux makes sense. Path Finder is better, though its buggy, and worth the money.
Little command to check if you're affected (from TFA):

python3 -c "import pathlib;import importlib.util;s=importlib.util.find_spec('triton'); affected=any(x.name == 'triton' for x in (pathlib.Path(s.submodule_search_locations[0] if s is not None else '/' ) / 'runtime').glob('*'));print('You are {}affected'.format('' if affected else 'not '))"
I like the simplicity and design of the Slow (https://www.slow-watches.com) watches mentioned in the first list you link in your post.

It reminds me of the Botta Design Uno 24:
https://www.botta-design.de/en/products/uno-24-plus-titan

I appreciate the clear delineation between "day" and "night" sides of the face, the meaningful position of the date complication, and a hour hand design that makes it possible to see down to ~5m increments.
As I recall, "register" was already a no-op in C compilers by the 90s or so (maybe except for embedded? I just don't know enough about that).
I used to think that too, until 2020 happened and I started a new job where I didn't have any casual connections to any of the people I had to work with. Now I think about teambuilder events the way I think about going to the dentist; I don't want to do it, but later on I'll be glad that I did.
I did this.

Start with getting some work, any work, with small / mom & pop type businesses, updating their website, fixing their printer, whatever they need. Possibly freelance, part-time, after hours, etc.

The next job could be something like a full-time (maybe in the "I.T department") of a small, privately owned, local company of 50-100 people.

After that, move up to a bigger company of maybe 1000+ people, multiple locations.

After a few years there... you can now be taken seriously as a candidate for BigCo.

It is true, companies do want an out of the box solution to hiring and are very risk averse, so a series of small steps, each one only a small stretch from the previous, is one way to get there.
Try FreeCommander. Not just with quicklook (Ctrl-Q) but dual panes as well.
Any proof-of-software-certification blockchains out there? In which "mining" is a trusted party reviewing code & posting content integrity hashes of all derived bits.

Then npm/pypi/cargo/whatever are given a list of the parties you trust and the number of certifications each bit needs before it can be downloaded.

Edit: of all the responses, none provide any mechanism for the software-verifier to be compensated. Says a lot about how much we value that kind of work as an industry.
Any self-contained logical system that shows some objective reliability, or objective point of conceptual unification with known principle, seems to arrive at this point eventually. "Did we invent this or did we discover this?"

What's interesting to me in the first place is that there are multiple, overlapping systems of varying scopes--_with_ their associated contradictions--in which this is a thing. Mathematics is just one of those systems.

The second thing that's interesting to me is that this is just one question which could offer insight toward further leverage, and yet the question itself hasn't seemed to offer much leverage so far. If you were to rank the questions that are "worth the time spent on them," I really wonder where this invented/discovered question would be in the list.

Does it matter whether we know the answer--whether we know if this thing was invented or discovered?

And if so, how much does it matter? Or, in what ways does it matter?

And, is it possible that it matters more that we can hold both of those possibilities in the same organizational mindset at the same time (invented AND discovered), and from that point consciously leverage them both?

That last question I really wonder about, because I've seen amazing & simultaneous results levered from both ends of such dichotomies.

> If this imagery looks intelligent, in some way formulated, where's the formula?

There are also some interesting gaps here, i.e. intelligence == formulaic; the question-model of "where is it" vs. the possible model of "I don't know where it is," (therefore?) and so on.

Nevertheless a fascinating topic in lots of ways, thanks for posting.
> And likewise, Jethro Tull's obsession with designing a machine that could replace the workers his father and grandfather had worked with.

And who would have thought that he could win a heavy metal award with a flute? The man was a true innovator.
FOSS as infrastructure doesn't mean every piece of FOSS is. And infrastructure can be incidental. While we're using analogies tortured beyond all meaning, a goat path in the forest is infrastructure if I ride my bicycle on it to get somewhere, but the goat herder was just herding their goats. If you want to rely on something (code, forest path, whatever), you should probably take steps to ensure the longevity and security of that thing, especially if you depend on it to make money. If I really need my goat/bicycle path, I could do path maintenance on it or try to get the government to do it, but complaining that I'm late for work because the goat herder didn't clear a fallen tree that their goats can jump over but I can't bike around is both foolish and obnoxious.
Let'sEncrypt is still a third-party entity.
As already noted, any connection to Hiawatha crater was only ever conjecture. Evidence that Hiawatha was not coincident with the YDB obviously tells us nothing at all about YDB events.

A recent survey article is Sweatman,

The Younger Dryas impact hypothesis: Review of the impact evidence

https://www.sciencedirect.com/science/article/abs/pii/S00128...

The remaining controversy is how much the strike contributed to the Younger Dryas development and other coincident events, particularly extinctions. To me, it is ludicrous to blame those on Clovis people, or on a climate hiccup smaller than they had weathered easily many times before. Now that we know people had already been there for 10+ millennia, the sudden wipeout idea gets much sillier.

The idea that the strike triggered the YD is appealing, but the record shows several other such cooling periods with very similar profile and duration in the past 100ky. It seems unlikely they were all triggered by comet strikes. But they could have been: we now know our records of comet strikes are woefully incomplete, having detected a very recent one only by enormous effort.

See also Wendy S. Wolbach et al.

Extraordinary Biomass-Burning Episode and Impact Winter Triggered by the Younger Dryas Cosmic Impact ∼12,800 Years Ago.

https://www.journals.uchicago.edu/doi/10.1086/695703
The talented Mr. Santos: A congressman-elect’s unraveling web of deception
thank you, if I ever finish my book I'll let you know : )
I suspect this has more to do with the lack of first-class sequence comprehensions in the syntax. If you had to write imperative style, but all loops were HOFs, it would hardly be ergonomic, either. OTOH a good query language is much more readable.
> It’s true that coastal elites harbor a lot of resentment toward “rednecks” for things like the recent abortion ruling

Nah, the abortion ruling is a product of coastal elites; there aren’t any rednecks on the Supreme Court.
If you access the domain that data was being sent to, h4ck.cfd, a message is given:

>Hello, if you stumbled on this in your logs, then this is likely because your Python was misconfigured and was vulnerable to a dependency confusion attack. To identify companies that are vulnerable the script sends the metadata about the host (such as its hostname and current working directory) to me. After I've identified who is vulnerable and repoterted the finding all of the metadata about your server will be deleted.

I of course don't believe it, but interesting to see something like this.
Exactly. The whole point of soft delete is data recovery, as it’s not sufficient for anything else (like auditing).
Recurring time blocks like this have been an absolute game-changer for me, I'd highly recommend it!

An hour in the morning and an hour-and-a-half around lunch have made it so much easier to stay sane, and provide nice cover to decline meetings by pointing to a calendar conflict.
Thank you for reading through it and summarizing. I disagree with your conclusion however.

It's not possible for someone to completely trace upstream dependencies in a SLSA compliant manner. No company can sanely expect that. What can be done is to say "we have some code from outside. How can we attribute it to upstream and make sure it has not been altered?" You can use signatures from the maintainers, version it, even reference a git commit. I don't think that anything additional from maintainers should be required, it's on the company to figure out how best to do so.
> The binary’s file upload functionality is limited to files less than 99,999 bytes in size. It also uploads only the first 1,000 files in $HOME (but all files < 99,999 bytes in the .ssh directory).

That’s… not great.
If you think that was good, just wait until you hear about Chris Columbus.
It would have been interesting to see a superscalar ia64.

The biggest problem with ia64 is that virtually every generation shipped late. Very late. We had working first generation CPUs years before anything shipped publically. The first ia64 had a huge amount of die space wasted by a worthless Pentium III core (if my memory is correct), which would have been far better used on cache.

For some workloads ia64 was fast. Networking benchmarks on my development machine were impressive because of having gobs of memory bandwidth and fast interrupts. The asynchronous register window engine really helped some things. Sadly, once em64t took off, it was a dead architecture. x86 is the only platform that gets the real resources at Intel.
I'll just second this based on my experience with software engineers. Most places I've worked your looking at at least 6 months before someone is starting to get enough familiarity with everything involved in the internal ecosystem (both technical and non) to really be productive and probably a year before they're starting to reach the productivity of their peers. So if someone leaves at 2 years you've probably gotten one of something resembling their full productivity. Less than that and there's a good chance your better off hiring the slightly less impressive candidate who will stick around for a few. Less than 6 months to a year you may be better off hiring no one.
Ok, even if we could all agree on a single trusted auditor, that would still put us in a very bad position. You would be limited to only use that baseline trusted set of software, which I guarantee won’t be sufficient for all the things you need as software grows and develops.
the version numbers are different, even though the package names are the same.
A stable version will have a version number such as `1.13.0`, where as a nightly version will have the date in the version number, such as `2.0.0.dev20221230`. You can check this either with `pip list | grep torch` or via `python -c "import torch; print(torch.__version__)"`

If you installed `torch` via the instructions to install the nightly version specifically, then you get the nightly version.
By default, you get the stable version of `torch`.
When the compiler can see both the callee and the caller (the most common case), why should it even matter? If you pass by value, but don't actually do anything that mutates the copy, and there are no aliasing concerns, surely the compiler can make it by-ref under the hood?

(The other direction is trickier, since by-ref implies the desire to observe aliasing, even though that's usually not expected in practice - but the compiler cannot tell.)
I know there’s methods for transmitting solar from orbit to ground, but this made me think about the sci-fi idea of orbiting mainframes that transmit the data to simple terminals.
I may have missed it, but it does not look like Meister Singer makes a version with a 24h dial, is that correct?

I think that would be the main draw of a single hand watch for me.
A PS1 or PSX would be helpful in the title. I too expected a retro game implementation. PS4 and Dreams is indeed, also very cool though.
I don't know much about this, but by-copy sounds nice. I'd rather own stuff and be happy.
> If 20% of the population wants something, 10% opposes it, and 70% doesnt care if it passes

That isn't the hypothetical I'm using to make my point. Obviously if you change the hypothetical you come up with different results, but then it isn't the scenario I'm using as an intuition pump.

Like, what I'm getting at is that there are sometimes policies you want your government to pass, even though more people oppose it than support it and nobody being truly undecided. Not all policy choices are equally important, and not everyone considers all policy choices equally important. A referendum is structurally incapable of enacting policies with minority support, for good or for bad. It's usually for good, true, but there are circumstances where you can do better by making sure that people think that the important policies are implemented, even at the cost of the majority not getting their way on relatively unimportant matters.
A lot of what you have listed is more about knowledge of local ecosystems - not "civil engineering, surveying, agriculture, navigation, mathematics, etc.".

As to some of the more general science knowledge though, subsequent societies could certainly replicate the scale and precision of cities like Angkor Wat or Tikal. Likewise, later ocean navigators had far more sophisticated navigation methods, using such tools as the compass and the kamat. As to qanat and wind-catcher architecture, it wasn't ever really lost...

I'll grant you that knowledge of public health has been very uneven, though it has generally been on the upswing in the past couple centuries (as objectively measured by life expectancy and the burden of communicable diseases), nothwithstanding certain missteps (such as adopting droplet theory which was less accurate than miasma theory).
This is not accurate. There’s a JS bridge to a lot of non native elements. You can get acceptable performance out of RN if you know what you’re doing but it will never match true native code.
The malicious package uploads your ssh private keys to it's server. This is extremely concerning to people that may have accidentally installed.

Judging from the package installation stats this was installed around 2,500 times
Wow... I don't know whether to laugh or cry.

Apart from your absolutely incredible take on my character - my business area has really profited from the war:

https://www.ft.com/content/7a70cee3-2891-4012-a22d-36363fadd...

"Woodside said that its revenue increased to $5.9bn in the September quarter, up 70 per cent from the previous quarter and a significant jump from the $1.6bn that the Perth-based company reported in the same quarter last year... ...Oil and gas companies have enjoyed a streak of record profits thanks to soaring energy prices caused by Russia’s invasion of Ukraine."
> How does one install the nightly package?

This is documented on the installation page, assuming you instead by their method. You specify a different source URL when invoking the package manager, so you would need to deliberately install the nightly release rather than get it accidentally. If you installed it by other means (perhaps you OS's package manager) this is also likely to be the case.

> If I just installed "torch" can I assume that I don't have the nightly version?

Probably, but it depends how you installed it, if you are using your OS repository then check with their documentation. The linked page for this thread includes a section entitled "HOW TO CHECK IF YOUR PYTHON ENVIRONMENT IS AFFECTED" (their capitalisation), follow the instruction there if you are not 100% sure what version you currently have installed.
Can someone ELI5 (or at least ELI20): Why does Forth do better on a different CPU architecture than other languages? Or, why does Forth do worse on the architecture that most other languages do fine on?
So that's including ssh keys?
"172." "There are only 168 hours in a week." "We expect your family to put in some hours also."
> For requests which are "reading" you just serve content, unless for some reason you only want human eyeballs to see your content.

I was going to cite the LinkedIn case where, last I had heard, the courts had decided that scraping was legal...

Headline [0] from April:

> Court rules that data scraping is legal in LinkedIn appeal

> LinkedIn has lost its latest attempt to block companies from scraping information from its public pages, including member pages.

... but upon googling it, I found a more recent [1] ruling :/

> LinkedIn prevails in 6-year lawsuit against data scraper

> The U.S. District Court for the Northern District of California sided with LinkedIn in its six year lawsuit against a firm that scraped data ...

So that sure puts a nail into the argument I was going to make. But still, while I think your use case lines up with the spirit of this kind of system, I think the reality is that it also would be used by every single site with a signup wall to kill off the archive.ph's of the world.

0: https://www.zdnet.com/article/court-rules-that-data-scraping...

1: https://iapp.org/news/a/linkedin-prevails-in-six-year-lawsui...
Data is a little old, but it does not appear that CA and New York are really ahead- https://www.jsonline.com/story/money/business/2017/04/17/how...
Show HN: Daystamp – like timestamp but for storing days (of birth, etc.)
> Maybe there’s some crazy alternative way things could be done

"Branchless programming" is an umbrella term for techniques in existing programming languages to avoid branches.
It’s accurate. That’s a marketing page for a DDoS prevention service so it’s not an unbiased source, and it’s especially important to remember the distinction between traffic hitting something like an edge node and actually reaching the target and causing harm. I see attacks fairly regularly (politics) but in most cases it means I see 15M block events for “GET /“ in Cloudflare’s dashboard but no actual impact on the service because they’re dropped quickly at locations around the world or, if they faked real browsers, they got a bunch of cache hits.

In other cases, people try more sophisticated attacks (e.g. posting random terms to a search page to avoid caching) and that’s more of a problem but it’s probably like 1% of the total traffic because it’s moved out of script kiddie territory into something where you need to have more skills and people don’t generally do that without a way to make money from it. One challenge with a DDoS in that regard is that it’s not subtle so your ability to wage an attack goes away relatively quickly without constant work replacing systems which are taken offline by a remote ISP.
> lower the standard of living in these countries

Where?

> Germany such that it cannot use EU membership

Germany is in a minority position. Not even 20% of the EU population and small member states have larger voting power.
I’ve learned woodworking at a level that will allow me to rapidly produce inexpensive but sturdy caskets for people who can’t afford one for cremating their loved ones (you could also be buried in it depending on the state).

The global situation is exhausting, attempting to focus more locally. Do what you can where you are with what you have.
So....Tor
I have some pretty terrible teeth, and freezing doesn't always work for me. A trip to the dentist is something I refer to as building up a resistance to physical torture.

What I can't decide is whether that makes the analogy more accurate or less.
I am curious… what percentage of FOSS work for the most critical systems is done by people working for free verse people on a company payroll? I feel like most big FOSS projects have corporate sponsors.
It seems you should be able to do it fairly straightforwardly with dynamic sql with this structure, but, I don’t know why you wouldn’t just use proper history tables, rather than story only deleted records, but lumping them all into one table.

I’ve never encountered a database where I needed to know about non-current records but only ever the last-before-deletion state of deleted records, whether for data recovery or any other purpose.