MurphyA/hacker-news huggingface dataset:
by capitainenemo | 2025-06-21 14:00:51+00:00
That sounds pretty foolproof so long as your black box fill method doesn't fill with a 99% opacity, or a flood fill leaves behind a few invisible anti-aliased pixels, or the merge operation of the black box doesn't result in some multiplication leaving a few bits of difference. Even if you erased the layer below, then filled above, I've had erasures vary in the bits outside the alpha channel messing up games using the texture info.

Overall, I kind of understand the paranoia even though in principle it does sound pretty foolproof.
by Quarrelsome | 2025-06-21 14:00:54+00:00
I think some of the most harmful misinformation is organic in nature, it might be fuelled by propaganda but normal people are entirely willing to seek out and believe in information that supports their prejudices or opinions, irrespective of its truth.

As the good Prokhor put it:

> Man's unfailing capacity to believe what he prefers to be true rather than what the evidence shows to be likely and possible has always astounded me. We long for a caring Universe which will save us from our childish mistakes, and in the face of mountains of evidence to the contrary we will pin all our hopes on the slimmest of doubts. God has not been proven not to exist, therefore he must exist.
by tialaramex | 2025-06-21 14:02:01+00:00
One thing that's fun about this is that BeOS isn't going anywhere.

If you decided to do this for, say, Windows, Microsoft is going to release a new Windows version with new stuff you can't do and too bad.

But BeOS itself is dead, and the Haiku project (to basically make BeOS again, once named "OpenBeOS") is about a quarter of a century old yet seems barely closer to releasing anything. A lethargic snail could sleep walk to the finish before Haiku ships version 2.
by b0a04gl | 2025-06-21 14:02:02+00:00
tbh that's not the flex. storing 100PB of logs just means we haven't figured out what's actually worth logging. metrics + structured events can usually tell 90% of the story. the rest? trace level chaos no one reads unless prod's on fire. what'd could've done better be: auto pruning logs that no alert ever looked at. or logs that never hit a search query in 3 months. call it attention weighted retention. until then this is just high end digital landfill with compression
by Hercuros | 2025-06-21 14:02:13+00:00
The specification proves a property about an algorithm/function, namely the equivalence between a more complicated memoizing implementation and a simpler direct recursive implementation.

It is also true that no numerical reasoning is happening: the memoized version of any recursive relation will return the same result as the original function, assuming the function is not stateful and will return the same outputs given the same inputs.

However, it is not true to say that it does this by exhaustion, since there are infinitely many possible outputs and therefore it cannot be exhaustively checked by direct computation. The “n” for which we are “taking the proof” is symbolic, and hence symbolic justification and abstract invariants are used to provide the proof. It is the symbolic/abstract steps that are verified by the type checker, which involves only finite reasoning.

Of course, the symbolic steps somewhat mirror the concrete computations that would happen if you build the table, especially for a simpler proof like this. But it also shouldn’t be surprising that a program correctness proof would look at the steps that a program takes and reason about them in an abstract way to see that they are correct in all cases.
by heisenbit | 2025-06-21 14:02:47+00:00
AWS features may be expensive to replicate 100% but what if one only needs 80%. One also needs to consider the effort involved in configuring AWS and maintaining the skills for that. Then there are opportunity costs of using e.g. AWS dashboards vs. better ones with grafana etc..

I guess a lot depends on size, diversity and dynamics of the demand. Not every nail benefits from contact with the biggest hammer in the toolbox.
by collingreen | 2025-06-21 14:02:52+00:00
Nice, sequential flow charts are easy to understand and pitch and they also make it nice for the folks at the front to say they did their part and any issues are now someone else's fault.

When people try to diagram the actual process (closer to what you're talking about) it's just a giant circle (or "double diamond" for folks charging money for powerpoints) which isn't a tool that makes management feel easier or "on track".
by bgwalter | 2025-06-21 14:03:12+00:00
> In such a system, a human could be brought in to fix issues as they emerge [...]

To begin with, the translation software stripped the license (which for companies is probably a feature).

The output is horrible and it would take a human more time to make it readable than translating it in the first place.

As the article notes, the translated software is fairly simple and this technique is not known to work in general. Even for this example there is no proof whatsoever that the translation does not change behavior.
by StackRanker3000 | 2025-06-21 14:04:13+00:00
Did the person I was replying to say any of that? You’re putting words in both their mouth and mine

I’m receptive to various arguments here that invoke power differentials, pragmatism, even deliberately breaking the terms of a service to help affect change, etc. I’m not necessarily someone who always follows the rules, and even though I do pay for YouTube I don’t view it as a real moral failing to use the free service with an ad blocker turned on

The comment I responded to didn’t have any of that, it just boiled down to “I can do it and they can’t stop me, so they can suck a dick”. Maybe not the end of the world when it’s directed towards Alphabet, but I hope that mindset doesn’t extend to everyone they interact with
by capitainenemo | 2025-06-21 14:04:18+00:00
I kind of feel there'd be a difference between vulcanised tire rubber and my drink stopper, but I guess there might not be. Also, tires grating on road is probably a bit different a wear profile. Clearly someone needs to test microplastic shredding in container rubber.

Oh well, at least they have some in that design with cork tipped plugs. It's a bit harder to find though.
by anton-c | 2025-06-21 14:04:22+00:00
Yeah the best in the world freight industry that is being sued by every company in America for their decades long price fixing scandal. Cant find the list of plaintiffs right now but it had ford and frito lay and hundreds of others. An update from yesterday:

https://www.mlex.com/mlex/antitrust/articles/2355294/us-rail...
by sltkr | 2025-06-21 14:04:58+00:00
Right, but the claim was “GOOGLE wants you to watch ads AND pay for a subscription” and that doesn't seem to be supported by the evidence.

I get that as a premium subscriber you still see in-stream sponsored content, but that's because the creator wants that, not Google. I think Google would rather have those sponsored messages be run as regular Youtube ads instead, so they can take their 45% (?) cut of the ad revenue while letting premium subscribers skip them.
by atwrk | 2025-06-21 14:05:00+00:00
> That's how humans also learn ie. adding numbers. First there is naive memoization, followed by more examples until you get it.

Just nitpicking here, but this isn't how humans learn numbers. They start at birth with competency up to about 3 or 5 and expand from that. So they can already work with quantities of varying size (i.e. they know which is more, the 4 apples on the left or the five on the right, and they also know what happens if I take one apple from the left and put it to the others on the right), and then they learn the numbers. So yes, they learn the numbers through memorization, but only the signs/symbols, not the numeric competency itself.
by egl2020 | 2025-06-21 14:05:40+00:00
A competitive athletic program is a huge time sink: practices, weight room, travel, meets, game day. That time spent elsewhere can go a long ways to covering college costs, such as taking extra classes and finishing a semester or quarter earlier or going to a school with a good coop program. Even a low-paying on-campus job can be competitive if the per hour rates are fairly compared.
by diggan | 2025-06-21 14:05:51+00:00
ORMs love to put people and projects in the situation where it's much easier for data types in your program to match exactly with the tables in your database, but reality often requires them to be decoupled instead. That "create user" request contains "isAdmin" smells like someone mapped that exact request to a table, and just because the table has "isAdmin", the data type now also has it.
by justsomehnguy | 2025-06-21 14:06:11+00:00
Hello there, Mr. I-Only-Have-a-Left-Hand.

I use the right control keys, I use Ctrl+Ins/Del, I use "Context menu" key, when it's available. And hey, I have almost a 30 years of muscle memory for them, so when some another idiot replaces the right Ctrl with F23 (which even can't be remapped by default AND pops up the stupidest menu for selecting what F23 should do) I really what to punch him in the face.

NB: as someone up in the thread mentions, right Ctrl is extremely useful for navigating in the text.
by antisol | 2025-06-21 14:06:42+00:00
> If you saw a giant, attention grabbing billboard for something you are looking for, you wouldn't hate it.

Yes, I would. When I'm looking for something, I search for it until I find it, and then after that I'm not looking for it anymore. I don't go for a drive through the countryside in the hopes that system76 have put up a billboard which blocks the view of the countryside but shows me the specs for their latest laptop model.
by felineflock | 2025-06-21 14:07:31+00:00
There are 3 primary undesirability aspects of ads:

1) ads as irrelevant intrusions (in spite of all data Google collects, ads are mostly irrelevant for any person)

2) ads as ugly or blockers of beauty

3) ads as thieves of attention or downright theft (scam ads, illegal products)

Then, should we pay to get rid of ads or not? Two opposite opinions:

1) paying YouTube support creators

2) paying YouTube rewards the "shitification" of the platform

But even for those who pay there are issues: the content creator's own sponsorships, shorts, the risk of account banning by Google.

Then how about compensating creators directly? (Patreon or PayPal for example)

What I don't get is the questioning on the morality of ad blocking. No one should be obligated to watch an ad in one's own device, regardless of whatever "Terms of Service" (which is not a contract). It may be unfair to the content creator who relies on that revenue though.
by michaelt | 2025-06-21 14:08:05+00:00
> The much more logical explanation is someone approached a low level employee at the MEAF who turned over a USB stick with the governments org charts and payroll records in exchange for their kids getting a full ride to a prestigious foreign university.

If there are spies in foreign countries going around offering life-changing sums of money for USB sticks, which people are accepting

is it not also plausible that folks at google/samsung/apple/aws/cloudflare/microsoft are getting offered life-changing sums of money for leaving their work-from-home laptop unattended for 5 minutes?
by nchmy | 2025-06-21 14:10:37+00:00
Would it be a good thing if a million unemployed devs were employed to just dig a big hole? Or, worse, cut down forests with axes?

Job creation for the sake of it isn't a good thing. What matters is whether it creates actual value, and does so efficiently.

The thrust of this, and many similar articles, is that it JS frameworks were largely a very inefficient, ineffective solution to a nonexistent problem.

The fact that they're ALL now SSR-first - without the robust and comprehensive functionality of longstanding ssr frameworks, cms etc - proves this.
by bryanlarsen | 2025-06-21 14:10:45+00:00
The only place I've ever gotten stuck in the snow is in my own yard, and I've been driving in snow for over 40 years.

But every single time I go out in the winter I have a plan for what I'll do if it does happen. Because it happens to people, good drivers and bad, snow tires or not.

> Also why I'm not trusting an electric car in -40 when there's no cell service for ~200 km spans.

You shouldn't be trusting any vehicle. Both an electric car and a gasoline car might let you down when you need it. The gasoline car is more likely to let you down, though. I presume you have a proper winter kit in your vehicle so you don't have to trust your vehicle.
by HelloNurse | 2025-06-21 14:11:40+00:00
My idea is that a reusable ledger, as a service or library, would be too distant from actual needs to provide much value.

Consider the example database state in the article:

Transfer ID Description ┃ user receivables available 1 order created ┃ -$10 $10 2 payment received ┃ -$10 $10 3 partial refund ┃ $5 -$5

A real application cannot go very far with this kind of "description": every type of transaction needs specific data, whose complexity dwarfs the double-entry ledger mechanism.

For example "order created" transactions need a reference to an order with details of what has been ordered, "payments" need a reference to a collections of debts that they are meant to pay and details of how they have been paid, "refunds" are actually many types and need a reference to what they are refunding.

Real accounts are also much more complex than a history of changes and a computed balance: for example, some of them need to be included in accounting calculations and reports in various roles, with largely arbitrary relationships and accounting criteria, while some are linked to real-world persons.

Comparing the two ledger implementations that the article references is instructive: Pgledger has simple ID columns for accounts and transfers, and it is up to the application to use them as foreign keys from the interesting tables, while TigerBeetle also offers some generic "user data" and "code" columns with arbitrary data and suggests having a separate "control plane" database.
by jerf | 2025-06-21 14:11:56+00:00
There's a lot of good information in here, but if you think this is a time to go all language supremicist about how much better your language is and how this proves Go sucks, you might want to double-check the CVE database real quick first. A lot of these issues are more attributable to plain ol' user error and the fundamental messiness of JSON and XML than Go qua Go and I've seen many similar issues everywhere.

For instance, there simply isn't a "correct" way for a parser to handle duplicate keys. Because the problem they have is different layers seeing them differently, you can have the problem anywhere duplicate keys are treated differently, and it's not like Go is the only thing to implement "last wins". It doesn't matter what you do. Last wins? Varies from the many "first wins" implementations. First wins? Varies from the many "last wins" implementations. Nondeterministically choose? Now you conflict with everyone, even yourself, sometimes. Crash or throw an exception or otherwise fail? Now you've got a potential DOS. There's no way for a parser to win here, in any langauge. The code using the parser has some decisions to make.

Another example, the streaming JSON decoder "accepts" trailing garbage data because by the act of using the streaming JSON decoder you have indicated a willingness to potentially decode more JSON data. You can use this to handle newline-separated JSON, or other interesting JSON protocols where you're not committing to the string being just one JSON value and absolutely nothing else. It's not "an issue they're not planning on fixing", it's a feature with an absolutely unavoidable side effect in the context of streams. The JSON parser stops reading the stream at the end of the complete JSON object, by design, and anything else would be wrong because it would be consuming a value to "check" whether the next thing is JSON or not, when you may not even be "claiming" that the "next thing" is JSON, and whatever input it consumed to verify a claim that nobody is even making would itself be a bug.

Accepting user input into sensitive variables is a common mistake I've seen multiple times in a number of langauges. The root problem there is more the tension between convenience and security than languages themselves; any language can make it so convenient to load data that developers accidentally load more data than they realize.

Etc. The best lesson to take away from this is that there is more than meets the eye with JSON and XML and they're harder to use safely than its ease-of-use suggests.

Although in the interests of fairness I also consider case insensitivity in the JSON field names to be a mistake; maybe it should be an option, JSON can get messy in the real world, but it's a bad default. I have other quibbles but most of them are things where there isn't a correct answer where you can unambiguously say that some choice is wrong. JSON is really quite fundamentally messier than people realize, and XML, while generally more tightly specified at the grammer level than JSON is, is generally quite messy in the protocols people build on top of it.
by tomhow | 2025-06-21 14:12:38+00:00
Please don't post insinuations about astroturfing, shilling, brigading, foreign agents, and the like. It degrades discussion and is usually mistaken. If you're worried about abuse, email hn@ycombinator.com and we'll look at the data.

https://news.ycombinator.com/newsguidelines.html
by toss1 | 2025-06-21 14:12:41+00:00
Yup, but the analysis is wrong

The way they analyze it is: "Here are the zones where people feel comfortable driving faster — so let's go there and write more tickets!"

The right way to analyze it is: "Here are the zones where people feel comfortable driving faster — do those zones have any more than the background rate of accidents, or less? If more, then how do we redesign the road for better safety and so people tend to drive less fast, or if less or same accidents, we should raise the speed limit"
by colechristensen | 2025-06-21 14:12:54+00:00
Blockchain tech _is_ useful though, but mostly not to consumers unless they're trying to circumvent the law.

Private blockchains between semi-trusted entities that need to keep accounts between them are great. It really is just a shared ledger, a shared database with the mechanics for keeping accounts in a way that's mathematically trusted so no one party has to own the ledger. This is good for banks settling accounts between each other which they very have to do nightly for a variety of reasons.
by divan | 2025-06-21 14:14:01+00:00
Bad explanation from my side. As generic headphones/mic they are perfect for chatting with ChatGPT in voice mode (that's how I use it most of the time, in fact). As comment above explained, they have their own "Hey Meta," listening feature and I would love to switch it to ChatGPT (or other voice AI).

In a way, that's similar how you can't change iPhone/AirPods to stop responding to "Hey Siri" and trigger ChatGPT instead. So I still label my take as weird )
by atoav | 2025-06-21 14:15:23+00:00
You know who outpaces you 100% of the time as you walk down the stairs? The guy jumping out of the window. Just because it is faster does not mean it is the right economic strategy. E.g. which contractor would you hire for your roof, that old roofer with 20+ years of experience or some AI startup that hires the cheapest subcontractors and "plan" your roof using a LLM?

The latter may be cheaper, sure. But too cheap can become very expensive quickly.
by immibis | 2025-06-21 14:15:50+00:00
Because of the Bretton Woods system and the subsequent Nixon shock. The combination of these meant the USA can print much more money than anyone else, give it to whoever it likes (it always ends up at shareholders), and the resulting inflation is the whole world's problem. Because the USA prints so much money that ends up at shareholders and some at bondholders, the rest of the world buys US shares instead of the rest of the world's shares. The US ownership class basically ends up with so much money and not enough things to do with it, and some of it gets put in these risky technology bets. Other side effects include low wages, since US owners don't have to pay workers to make good products as much as they do in other parts of the world, preferring to just siphon off the endless free money stream, and high non-financial asset prices (e.g. houses), since there are so many wealthy owners to sell to instead of workers.

And the Bretton Woods system is basically a side effect of the fact that Europe had World War 2 and the USA didn't.
by mbeex | 2025-06-21 14:15:57+00:00
Did this for 30 years. Two years ago I finally took the time to acquire the whole thing.

There is no way back. Relaxed posture, no UI elements stealing my focus unnoticed, parallelism (partially): continually "big-picturing" text; speaking with people while typing. The rhythm of this motoric skill and his quite specific form of memory alone, strangely decoupled from and coupled to the other mental processes at the same time, the interplay is simply marvelous.
by oldmanhorton | 2025-06-21 14:16:05+00:00
There is a ton of tools and custom logic used by/with/for the GN ecosystem in chromium that I imagine would be difficult to port.

This tool is substantially less complex than Bazel, nor is it a reimplementation of Bazel. Ninja's whole goal in life is to be a very fast local executor of the command DAG described by a ninja file, and siso's only goal is to be a remote executor of that DAG.

This is overall less complex than their first stabs at remote execution, which involved standing up a proxy server locally and wrapping all ninja commands in a "run a command locally which forwards it to the proxy server which forwards it to the remote backend" script.
by lcnPylGDnU4H9OF | 2025-06-21 14:16:13+00:00
However, it is about bottle caps that are designed to go exclusively on glass bottles. I guess the headline could have read “Bottled drinks with caps that are designed to go on glass bottles ... ” That doesn’t seem like it would be misleading; it would also be less ambiguous than “bottle caps” which could suggest any cap to any bottle. (And it would be a rather obtuse way to phrase it.)

Regardless, the headline seems to be literally accurate. Microplastics are indeed found in larger quantities in glass-bottled drinks than in plastic-bottled drinks. Those microplastics in glass-bottled drinks come from the paint on the designed-for-glass-bottles bottle cap.
by b0a04gl | 2025-06-21 14:16:15+00:00
> “it's time to retire the just slime’ metaphor”

hits hard. we’ve used that phrase to downplay life’s complexity, but statistically, life is the anomaly not the default. the blog nails it: we’ve only found life in one corner of one planet, under a very narrow set of conditions. framing it as mundane is a denial. we’re surrounded by sterile rock and radiation and somehow expect slime to be obvious
by diggan | 2025-06-21 14:16:30+00:00
> You can do it to any change in the repo and everything gets automatically rebased downstream of it

So does `git rebase -i $commit^1` and marking the commit with `edit`, any commit afterwards (which I think you mean by "downstream"?) also gets rewritten since you've changed a commit in the middle.

I'm not sure if you're selling it a bit short, or if `jj` just have a target audience that I am not a part of, both are of course ok :)