skysight-inc/HackerNews huggingface dataset:
> Netanyahu is viewed as the messiah of the Jewish people

I think there was a strong urge to portray him as the second coming of King David (the slayer of Goliath) after the assassinations of (other war criminals) Deif, Haniyeh, Nasrallah, Saifeddine, and Sinwar within 6 months of each other.

> something about rebuilding a temple in Jerusalem

No temple yet, but there's a valid religious claim should they choose to build one on the Rock. The main mosque is actually a few hundred meters removed from the Rock.

> until he achieves the eradication of the Palestinian people he will not rest

Think the political apparatus strives to control the demographics (for its own survival)? Eradication is one mechanism, but at 7 million Palestinians, they'd need to summon a World War esque scenario to pull it off. So, unlikely?
> What evidence do you have that vehicles over a certain size and power are inherently more dangerous?

Basic physics and historical collision data collected over decades.

But don't take my word for it! Look up your local official collision data -- how many pedestrians have killed people inside a four-wheel vehicle? What about the other way around? Now repeat for cyclists, mopeds/motorcycles, and other four-wheeled vehicles.

The heavier vehicle kills the lighter vehicle, primarily because of momentum.
I wish someone in the Chrome team knew about Hyrum's Law before they released a breaking change in the way chrome validates custom URLs.
Tesla aced another independent out-of-sample crash test [1].

The danluu article also mentions an iSeeCars report at the bottom that says that Teslas have a high amount of fatalities per mile driven [2]. However, while they claim to be using official US estimates of fatalities data, they normalized it with estimated mileage using unknown proprietary iSeeCars data:

> iSeeCars analyzed fatality data from the U.S. Fatality Analysis Reporting System (FARS). Only cars from model years 2018-2022 in crashes that resulted in occupant fatalities between 2017 and 2022 (the latest year data was available) were included in the analysis. To adjust for exposure, the number of cars involved in a fatal crash were normalized by the total number of vehicle miles driven, which was estimated from iSeeCars’ data of over 8 million vehicles on the road in 2022 from model years 2018-2022. Heavy-duty trucks and vans, models not in production as of the 2024 model year, and low-volume models were removed from further analysis.

Some numbers are also surprising, such as the Model Y having almost twice the fatality rate (10.6 per billion miles) as the Tesla average (5.6) --- suggesting that there's a wide gulf between it and the Model 3 in terms of fatality rates, which seems difficult to explain. Ultimately, iSeeCars is a small VC-funded startup with very few people and so it is unclear if their methodology is actually good or not.

For a better blog post about whether Teslas are safe, here's a post from Brandon Paddock [3] from a year ago, which seems more or less objective and unsurprising. Here is the conclusion that he drew upon analyzing the FARS data:

> Tesla’s fatal accident rate is nearly identical to that of the Audi A4 series, and far lower than a standard Ford mid-size sedan. In this case, the Ford’s accident rate is more than 4 times higher than the Tesla Model 3.

[1] https://www.teslarati.com/tesla-model-3-aces-safety-tests-ch...

[2] https://www.iseecars.com/most-dangerous-cars-study

[3] https://brandonpaddock.substack.com/p/are-teslas-the-most-or...
It doesn't meet your needs, but I have something kind of like this for my iPhone.

I wrote a Shortcuts Automation that triggers when CarPlay disconnects. It then grabs the current date and time, the current latitude and longitude, the street address and an Apple Maps link and appends it to a "Location Log" note in the Notes app. I could've dumped it to a file instead, but I wanted it in a note.

It requires zero interaction from me.
You can add it to your list of its crimes against humanity: killed at least two nuclear physicists.
this has always been the key reason, going back to the '60s
> Although, my AI-generation was a response to an interesting comment.

Yes, that's why the comment it was in response to was not downvoted. But being interesting and HN-appropriate isn't something responses automatically inherent from their parent comment.

> You do not think readers are interested to see how the Chernobyl snow-globes look like?!

Actual Chernobyl snow globes... maybe a link to that would be appropriate.

AI hallucinations of what they might look like? Maybe if the context was a discussion of the capacities of different AI models and it was offered as a demonstration of the one that generated it, but not in the context it was presented, no.
Every old telco technician had a story about dropping a wrench on a busbar or other bare piece of high powered transmission equipment and having to shut that center down, get out the heavy equipment, and cut it off because the wrench had been welded to the bus bars.
Having run a software team with good estimates, I’m disappointed in some of the commentary of, “just make up a long or obscure estimate.” I don’t expect a considerable amount of unknowns to come up in a project unless you have changing requirements or bad planning.

You can’t do anything about changing requirements so that can be forgiven. Poor planning cannot though.
A simple trick to solve nearly all freezing problems: move the computations to a background thread, aka Worker in JS terms.
One would think that this would represent an opportunity in the market to, you know, sell TVs that only do their basic function, and not try to tack on ads and such, right? Or, is it that not enough people care about this stuff...so the masses simply put up with it, and move about their lives...and Tv makers (and other device manufacturerers) go with the flow of taking as much advantage as possible?
I have a solution! I just made one more framework!
I've made the jump from physics to neuroscience, so I can talk to the engineers here (I've taken a lot of EE and worked professionally in it too).

The linkages between neurons is somewhat similar to how and RNN looks. But you must remember, there are electrical and chemical elements going on here. It's not just one neuron spiking another. There are many different biochemical processes that modify the behavior of little parts of a neuron, stoichiometrically. And there are many different types of neurons and they all change over time, sometimes drastically so. Most of the goings on is biochem. It's not digital, or even analog. You really need to go down to the field equations at times, finite elements will get you far, but only just so.

RNNs thinking certainly will help you understand better what is going on in a brain, but, like, these things are millions of years old, and optimized just to make more of themselves, not to be understood. It's tough going, and we as a species are only at the very beginning of hundreds of years of study of the brain.

If you'd like to learn more, I can recommend some texts.
There's flag protection that dang/moderators choose to enact on contentious posts like this one that result in them sticking around for way longer than without the protection. If anything, dang is biased in favor of political posts like these lasting way longer than I bet he'd personally want to.
Sorry, that’ll teach me to state beliefs rather than facts. Thanks for the correction.
I think you are agreeing with that. There is not some international law that says countries must deal.with countries they don't want to. It's a national thing.
I don't think you'll find out anything you not already know:

+ spotdl search is nice

+ tkinter surprisingly doesn't look as ugly as usual

- no rewind or fastforward, nigher is it possible to click somewhere in the track progress bar to jump to.

- "about" button does nothing

- /tmp is littered with covers cause they are created each time you click on a track

- if you first used <F8>/<F9> or the previous/next buttons and then you hit <space>, besides pause/play it causes a strange behavior: some random track in the playlist is get marked as an active one.
OCP hardware is only really accessible to hyperscalers. You can't go out and just buy a rack or two, the Taiwanese OEMs don't do direct deals that small. Even if they did, no integration is done for you. You would have to integrate the compute hardware from one company, the network fabric from another company, and then the OS and everything else from yet another. That's a lot of risk, a lot of engineering resources, a lot of procurement overhead, and a lot of different vendors pointing fingers at each other when something doesn't work.

If you're Amazon or Google, you can do this stuff yourself. If you're a normal company, you probably won't have the inhouse expertise.

On the other hand, Oxide sells a turnkey IaaS platform that you can just roll off the pallet, plug in and start using immediately. You only need to pay one company, and you have one company to yell at if something goes wrong.

You can buy a rack of 1-2U machines from Dell, HPE or Cisco with VMware or some other HCI platform, but you don't get that power efficiency or the really nice control plane Oxide have on their platform.
Hertz "Unlimited" Miles Rental: $10K Charge for Driving Too Much?
There isn’t much utility, but tbf the outputs aren’t identical.

One danger is the human assumption that, since something appears to have that capability in some settings, it will have that capability in all settings.

Thats a recipe for exploding bias, as we’ve seen with classic statistical crime detection systems.
Thanks for the correction. The downvote I got was justified.
i get you on vi. i was there (3000 years ago ;-), although only at the tail end of it in the early 90s. i switched from emacs to vi because of my sysadmin job.

i am really curious what you make of aurelia once you take it apart. please ping me if it is not to much trouble. i discovered aurelia when angularjs 1 was being redeveloped into angular 2. rob eisenberg was invited to the angular team based on his work on durandal but when his ideas were not accepted he left again and built aurelia instead. aurelia is not perfect either, but it was way better than angular 2 or vue at the time.

on your mobx example, you are right, aurelia doesn't track everything. it may be able to handle some level of complexity but i certainly had situations where i had to explicitly send a signal to get aurelia to update values.
Thanks. I see it. I also added a bug report for the janky "show variable value" on mouse over.
> The best way to have successful results showing work on HN is to build something that is interesting

This is sort of obvious. Do you really expect that the OP didn't know that?

> Availability of source code usually doesn't have much of anything to do with it.

Half of the top Show HN posts are about FLOSS software. In the other half, some are not about software. So your claim is wrong.
Researchers Claim to Pinpoint Exact Date When Elon's X Started Boosting Right
Of course there was, that’s not even pedantically correct. Death came instantly, only dying took awhile.
Honestly this is a very nitpicky argument. The issue for site contractors is not with manually checking each entry to ensure it's correct or not. It's writing the stuff down in the first place.

I'm exploring a similar but unrelated use case for generative AI, and in discovery interviews, what I learnt was that site contractors and engineers do not request or expect 100% accuracy, and leave adequate room for doubt. For them, it's the hours and hours of manually writing down a TON of paperwork, which in some industries is often months and months of work written by some of the poorest communicators on the planet. Because these tasks end up consuming so much time, they forgo the correct methodology and some even tend to fill up some reports with random bullshit just so that the project moves forward - in most cases, this writing work is done for liability concerns as mentioned above, rather than for the purposes of someone actually going through it. If the writing part is cleared for many of these guys, most wouldn't have a problem with the reading and correcting part.
Solved the problem almost completely in npm. Sure you can't search for a name of a company or a project and expect it to be related to the company or project.
But there's no way to solve that.

But once you know a namespace is owned by a company or project, you can know that everything under it is legit.
Which solves the vast majority of squatting and impersonation problems.

Also you know that everything under "node" for example is part of the language.
Chiming in with helpful rules of thumb I go by:

1. Never give an estimate in the same conversation in which it was requested, unless you're quite sure the answer is "less than an hour". Especially if they are going to turn around and quote your timeframe to a customer. The reason for this rule is:

2. The more you think about an estimate, the higher it will go. "Oh yeah and we'll also have to..." is 100x more common than "I found a shortcut that doesn't compromise on..."

3. Even if they know it's an estimate and not a deadline, they might not know the difference between "40 hours of dedicated effort" and "One week's worth of business hours". Making that distinction is just as important as the estimate/deadline distinction.

I'm lucky to work where we don't spend much effort on estimates and time tracking, both of which just make things take longer and cause productivity-reducing stress.
I just walked a mile in Los Angeles for lunch.

I had the following near misses where I would have died or been severely injured if I hadn't been alert: a Tesla coming out of an alley (driver was on his phone, never saw me), old diesel Mercedes running a stop sign (couldn't see the driver), a Ford F150 in a parking lot (guy was fixated on a spot that just opened up).

This does not include the woman in the Lexus who intentionally crawled up on me because I had the temerity to be in the crosswalk when she wanted to be someplace.
I disagree. #1 this topic is not as divisive as it may seem. There is consensus as to what is happening and only a minority of the world thinks otherwise.

#2 Israel is a major tech partner and most large tech companies have offices in Tel Aviv. Many startups that we discuss here are headquartered in Tel Aviv. The head of state of the country having an ICC arrest warrant and the situation at large have major consequences to the tech world and thus HackerNews users have a unique lens through which to have discourse. Discourse with an angle that you won't find elsewhere this is discussed.
I went to look at array accessor overloading today and saw “Property Hooks” in the sidebar (under “Classes and Objects”).

I didn’t know what they were, so I clicked. I was bewildered that I had never run into them before, used them in my own code, or seen them used by others. Come to find out they’ve only been around for about a day!

Reminds me of some of the lovely expressibility and syntactic sugar that’s pulled me to other languages lately. Glad to see it make its way into PHP.
Getting slightly off topic, but I think it's hard to find the right terminology to talk about html's complexities. As you point out, it isn't really a syntax anymore now that literally every sequence is valid. Yet the parsing rules are obviously not as simple as a .* regex. It's syntactically simple, but structurally complex? What's the right term for the complexity represented by how the stack of open elements interacts with self-closing or otherwise special elements?

Anyhow, I can't say I'm thrilled that some deeply nested subtree of divs for instance might be closed by a open-button tag just because they were themselves part of a button, except when... well, lots of exceptions. It's what we have, I guess.

It's also not a (fully) solved problem; just earlier this year I had to work around an issue in the chromium html parser that caused IIRC quadratic parsing behavior in select items with many options. That's probably the most widely used parser in the world, and a really inanely simple repro. I wonder whether stuff like that would slip through as often were the parsing rules at all sane. And of course encapsulation of a document-fragment is tricky due to the context-sensitivity of the parsing rules; many valid DOM trees don't have an HTML serialization.
Thanks for this discovery, I admit I never went in the settings of ublock origin and that's useful !

I will definitively add some more sites in this section.
> it likely is just as simple as their metabolism is such that they burn more calories than the average person. Population variation will always lead to some people with outliers both in high expenditure and low expenditure.

That's the point though. I'm saying that we burn calories at different rates. We burn fat at different rates. We have different rates of addiction, cravings, etc.

Just saying CICO is the same boring and borderline inaccurate language that has led to nearly zero change in the population at large. may as well just tell them to use physics correctly to lose the weight, because it's the same effective language.

To even determine CICO is fraught with difficulty and inaccuracy in both CI and CO. You can hand make everything, weigh every ingredient, and even then you struggle to determine how much you're CO. At best you'll have an estimated CO but then what do you do when your weight isn't changing? you have to start adjusting the math because clearly you're not burning as much as you think you are.

This is made much, much worse with the fact that we don't actually burn that many calories with exercise. And even with what is burned, the rate of burn changes drastically based on your current weight and how long you've been losing weight.

The fact is, the point is, CICO ignores all the real challenges and thereby all the real problems people need to understand and face.
One of the funny things about antitrust, and especially when it comes to Apple, who (let's be real) have a high opinion of themselves and their products, is how much it induces them to say:

"What? We're not that popular, I don't know what you're talking about, there's so many options out there, and lots of people don't like or want our things and we're not as big as everyone imagines".
It may look more high-level than something like C, but it is actually no more high level than a macro assembler with registers eliminated. As there's no syntax tree, essentially every word that is parsed from the input stream is replaced with a subroutine call. So the resulting FORTH code is nothing but a series of subroutine calls.

In my experience quite often writing in assembler is easier than FORTH unless you have a strategy and self discipline, which when acquired makes one a whole lot more productive than using assembler, and arguably more so than a high level language. There're no pointer arithmetics, no rudimentary type checking, not even an array type (you have cells and addresses). There is nothing that throws an error except things like stack over/under-flow checks, and if you are lucky your code will crash. If not debugging can be tricky. Stack imbalances won't be reported/checked for you, there is no bounds checking for anything (not even structs). But there are conventions/strategies to prevent these kinds of bugs from happening that one needs to either discover for themselves, or find out in books (the book Thinking Forth helps, but is not enough I would say).

Working with the stack can be more difficult than with registers, although the latter can be easily simulated with variables, which is often frowned upon. But words like CREATE ... DOES> enables meta-programming that helps with generating code with code, and makes it quite powerful, but can make your code complicated to reason about (see the concepts of compilation vs. execution vs. interpretation semantics described in ANS Forth).

In the end the appeal of FORTH for me is in its "simplicity" (but nowhere any ease of use as it requires mastery of laying out code in memory as you would do in an assembler without any help from the language itself), its overall philosophy (see Chuck Moore's A Problem Oriented Language) on focusing on the nature of the problem rather than thinking in terms of the tools/language given to you (build a "language" for the problem), and providing solutions with as minimal "cruft" as possible.
They said "in the US". The data you have provided says "Worldwide" which doesnt prove the point about the US.
Yeah, I've read that, but I lived through it and even worked for them for 6 months during the period. No, Ballmer was not an underrated CEO. He was an overrated COO and a terrible CEO.
AI Has Enshittified America's Advanced Stealth Fighter
Putting aside the questionable simplification that IQ correlates with desirable political behavior, can you provide an example of when heavily oppressed people successfully overthrew their oppressors? If you examine history carefully, you will find that such cases are exceedingly rare.

As a Russian citizen, I'd like to mention two things. First, the Communist revolution disrupted the continuity of tradition in Russia. The knowledge, heritage and legacy that many people cherished was wiped out through killings and forced exile. Second, there is an esoteric aspect rooted deeply in Eastern Orthodoxy that cannot be easily explained.

Currently, many of the most intelligent Russian citizens are attempting to relinquish their Russian citizenship, seeing it as the best path forward for themselves as individuals. The opportunity to fight for a better collective future faded away long ago.
Thanks for submitting! We know HN has a sweet spot for LuaJIT, so we figured it would eventually end up here.

Quick summary: this post dives into the gory details of how we implemented an eBPF based profiler for LuaJIT.

Let us know if you have any questions on this, we’ll keep an eye out on comments!
!!!

When I wrote “I carefully and meticulously copy the discovered fingertips, and then ask Fitzpatrick for help.” and got back “Fitzpatrick watches with a mixture of amusement and bewilderment as you meticulously dust the glass pane with a camel hair brush”, I thought it just re-used the adverb I gave it.
> There's no transmission capacity

What is "transmission capacity"?
Yeah, that's what I meant. There's no built in support; but it's indirectly readable since client-side JS can read it.
You can see both triples are contained in one binary tree using the big diagram in section 3. The triple [3 4 5] has the "path" RR. The triple [4 3 5] the path R.
> ask yourself why the green nations in Europe are paying so much less than the US to fight Russia

Oh, this is simple. Ukraine would be able to defend itself if it kept nuclear weapons. However they signed a treaty with USA, UK and Russia and gave up their nuclear weapons in exchange for some security guarantees. Russia did not honor that agreement. If USA and UK fail to provide adequate support, nobody will sign such treaties again. What’s even worse, nuclear arms are becoming the only real security guarantee, so the fate of Ukraine defines the fate of nuclear non-proliferation.
People can communicate each step, and review each step as that communication is happening.

LLMs must be prompted for everything and don’t act on their own.

The value in the assertion is in preventing laymen from seeing a statistical guessing machine be correct and assuming that it always will be.

It’s dangerous to put so much faith in what in reality is a very good guessing machine.
You can ask it to retrace its steps, but it’s just guessing at what it’s steps were, since it didn’t actually go through real reasoning, just generated text that reads like reasoning steps.
Those people died before they knew they were fucked. At some point acute radiation exposure makes it so they can’t even dose you with morphine properly. Same thing happened at Chernobyl if I recall.

At some point potassium chloride is a mercy.
See also: https://en.wikipedia.org/wiki/Rubber_duck_debugging