MurphyA/hacker-news huggingface dataset:
by baron816 | 2025-07-23 20:11:31+00:00
Employee to CEO pay ratio is such a meaningless and distracting measure. Imagine there is a hedge fund that has only a handful of very highly paid employees. Compare that to a very large multi-national corporation that employs hundreds of thousands of low skilled laborers (something like Walmart). Let’s also imagine the CEOs of both companies have identical pay packages. All else being equal, the hedge fund that only employs a few people is much better for society than the company employing many many more people. I don’t think anyone here would agree with that.

One thing we absolutely don’t want to do is disincentivize companies hiring people at the lowest end of the socioeconomic ladder. If employing those people lowers how much executives are allowed to get paid, what do you think is going to happen?
by megaman821 | 2025-07-23 20:11:36+00:00
It would make getting a Birkin-like bag as easy as any other but not a Birkin Bag since Hermes owns and controls the distribution of those. You can already get a Birkin quality bag for a fraction of the price and you can get a Birkin looking bag for an even smaller fraction. Owning a Birkin bag has very little to do with its utility as a purse, but as a signal of your status since you can both afford and get invited to purchase one.
by dfabulich | 2025-07-23 20:11:42+00:00
Honestly, I can't believe you're asking me this! You're so far in the weeds of the WASM component model that you have no idea what the problem is. It's really silly to ask what the "most important blockers" are, as if it's a list of bugs that can be fixed.

But, sure, in good faith, here's the problem.

Today, if you take a UI-focused DOM-heavy web app that makes lots and lots of DOM API calls (i.e. most JS web apps ever written) and try to rewrite it in Rust, you'll have to cross the boundary between JS and WASM over and over again, every time you use a DOM API. Every time you add/remove/update an element, or its styles, or handle a click event, you'll cross the boundary.

The boundary is slow because every time you touch a JS string (all CSS styles are strings!), you'll have to serialize it (in JS) into a byte array and send it into WASM land, do your WASM work, transfer back a byte array, and deserialize it into a JS string. (In the bad old days you had to copy the byte array in and out to do any I/O, but at least we have reference types now.)

And it's not just strings. All JS objects that you need to do actual work with have to be serialized/deserialized in this way, because WASM only knows about bytes, arrays, and opaque pointers. DOM elements/attributes, DOM style properties, DOM events (click events, keyboard events, etc.), all of them get slow when you transfer them in and out of WASM land, even with reference types, because of serialization/deserialization.

WASM interface types will make it easier to call JS from WASM, but as long as you're still calling JS in the end, rewriting in Rust will never make a DOM-heavy web app faster than writing it in JS.

That's why this sucks! Rewriting a Node.js app in Rust (or Go or Zig, etc.) normally yields huge performance gains (at huge developer effort), but rewriting a JS DOM-heavy web app in Rust just slaps Rust on top of JS; it usually makes it slower.

The only fix, as Daniel's article explains, would be to standardize a low-level DOM API, one that didn't assume that you can use JS strings, objects+properties, exceptions, promises, etc. This would be an unimaginably large standardization project.

You couldn't use WebIDL at all; you'd need to start by defining a new "low-level WebIDL." Then, you'd start standardizing the entire DOM API, all over again (or at least the most important parts) in low-level WebIDL, and then browser vendors could start implementing the low-level DOM API.

Then WASM could start calling that API directly. And maybe then you could rewrite web apps in Rust and have them get faster.

Until then, WASM is only faster for CPU-intensive tasks with I/O at the beginning/end, and otherwise it's only good for legacy code, where you don't have time to make it faster by rewriting it in JS.

(It should sound insane to anyone that taking C++ and rewriting it in JS would make it faster, but that's how it is on the web, because of this WASM boundary issue.)

So, what's the most important blocker? (gesture toward the universe) All of it??
by pmarreck | 2025-07-23 20:11:57+00:00
It doesn't prevent the error, but it also won't take down your server when malicious users (or just lots of normal users) start to bang on that input with the problem, and your non-BEAM VM pool starts to run out of available preloaded stacks... You get a new Erlang process in well under a millisecond on modern hardware

It WILL log the error, with a stacktrace, so you have that going for you

Note that even with typing, you cannot avoid all runtime errors

Also note that this tech was first battle-tested on cellphone networks, which are stellar on the reliability front
by jojomodding | 2025-07-23 20:12:00+00:00
Interestingly enough, Rust does not allow you to access undefined memory, not even if you do not care about the value stored there. People have been proposing a `freeze` operation that replaces uninitialized memory with garbage but initialized data (i.e. a no-op in assembly).

But there is tension about this: Not allowing access to uninitialized memory, ever, means that you get more guarantees about what foreign (safe) Rust can do, for instance.
by mindslight | 2025-07-23 20:12:08+00:00
Have you not been paying attention for the past several decades? Trump is unprecedented in audacity, crassness, and degree of harm. But the overall trend is right in line with what Republicans have been doing for thirty+ years (at least as long as I've been paying attention). And no, the destruction does not cause people to vote Democrat in response. People become more desperate, more reactionary, more quick to blame their fellow citizens, and more easy to lead towards supporting even more destruction - this is exactly how we've arrived at Trump in the first place. When the Democrats do get back in office, they effectively act as controlled opposition. Even if they try to undo the damage, most actions are sabotaged by a few "moderates" that have been captured by the corpos just like the Republicans. And then the Republican machine goes to work projecting - pointing to the Democrats' failings as open corruption, inability to do anything, fiscal irresponsibility as price inflation finally appears from the Republicans' profligate spending, etc.

Personally I'm not really worried about the "no more elections" panic narrative, because I think the real answer is that there isn't going to be much of a federal government left to take the reigns of.
by jki275 | 2025-07-23 20:13:02+00:00
The US government does issue life insurance for all military personnel. It's a nominal cost (20 bucks a month IIRC) for something like 400k of coverage. It's been around since 1914[1].

As far as I know all of the astronauts were military at that time, so they probably would have been covered by this program. There could be any number of nuances I'm not aware of though.

[1]https://benefits.va.gov/benefits/infographics/pdfs/timeline_...
by jesse__ | 2025-07-23 20:13:08+00:00
I kinda did post results at the end of part 4 .. I beat the SOTA by 1.8x

There's a benchmark utility here: https://github.com/scallyw4g/bonsai_noise_bench

Fastnoise2 is a high quality library. Can't speak to fastnoiselite .. never looked at it.
by reactordev | 2025-07-23 20:13:10+00:00
>Wrong. You need to let it slide up and then slide back down.

This is correct. Pulling the meat early means it will continue to cook while resting until the temperature comes down. It may slide up, but what you absolutely shouldn’t do is pull it early, wait 5 Mississippi, then cut into it. It needs to cool down at least 20 degrees C. 50 degree F. Still hot but won’t burn your fingers if touched. Put on some latex gloves, and cut away…
by Applejinx | 2025-07-23 20:13:17+00:00
The scientists I know have been pretty loud about there being no good way to repair what's been broken. Stuff can't just be turned on again.

I do expect more than just flipping off a switch: at some level there'll be outright sabotage, of data systems or physical hardware or both, for the purposes of destroying what is being made to go away.

This is because that's why it's being done. Budget concerns were never the point. It's the wholesale destruction of American soft power and indispensable systems. That's why I expect physical sabotage under cover of 'decommissioning'.
by adastra22 | 2025-07-23 20:13:29+00:00
I actually worked in the same building as the people organizing this research. Now I'm drawing on decade-old memory, and the program may have changed in the interim, but at that time the research that would become the X-59 demonstrator was absolutely about eliminating the sonic boom. There is no law of nature that says you have to have a sonic boom when you break the sound barrier--there are in fact a lot of assumptions wrapped up in that outcome.

A sonic boom is what you get when a traditional solid, largely flat-ish airfoil pushes air smoothly through the transition to supersonic flight. Very ELI5, but during the transition the energy/noise being put into the air basically stops dissipating from the aircraft at the point of transition, and so all that noise clumps together into a shockwave.

The shape of the X-59 makes it such that the transition doesn't happen uniformly over the air surfaces of the plane at the same time. It does get a little noisier around the transition, but it not a shockwave at all.
by sunflowerfly | 2025-07-23 20:13:32+00:00
We once were. We built canals, a massive railroad system, then our interstate system. Likely a sign of our slow decline to a has been country.

Today we should be building subways, a hub and spoke high speed rail system, and an automated hub and spoke freight system that uses trucks only for first and last mile. And maybe a tunnel at the Bering straight.
by andrewflnr | 2025-07-23 20:14:05+00:00
The article makes (or at least repeats uncritically) the same point about letting temperature come down. Ctrl-F "vapor pressure". It's just not in that exact sentence you picked out (where it's arguably still implied, since you're not going to eat meat still at cooking temperature). As for the second point: it's not a strawman. The version I heard years ago was the one about needing time for chemical changes that soak up the juice in the muscle fibers or whatever, not plain temperature.
by m463 | 2025-07-23 20:14:09+00:00
> The transparency, blur and contrast issues are stupid but so obviously stupid that I assume they’ll be fixed.

lol

I thought the same when ios 7 came out - hidden menus requiring multiple taps, touch targets that don't look like touch targets, small targets, terrible contrast, silly unreadable fonts, on and on...

but not only didn't this get fixed, the SAME designs leaked into the rest of the world.

for example, the tesla car UI adopted ALL the same deficiencies. Hard to read center display? critical functions that require multiple taps? all while you're driving... wow

sigh
by magicalhippo | 2025-07-23 20:14:37+00:00
In a case like this, they usually call ahead to let customs know, and follow up with the declaration ID once it has been sent.

Apart from that, customs is very tight lipped about what triggers manual processing of a declararion.

Though for example a large discrepancy between weight and value typically would lead to it getting flagged for manual processing, as I understand it.
by int_19h | 2025-07-23 20:15:27+00:00
This particular approach has been tried many times before. I remember back when Microsoft introduced Aero transparency effects in Vista, and then had them dialed down substantially in Win7, in the same exact way ("frosted glass") that Apple seems to be speedrunning through in iOS betas right now.

So yes, it will be fixed, and the fix is easy. They just have to accept the fact that the "liquid" part needs to be strongly de-emphasized in favor of readability. It would be nice if they just did that and saved us all the grief, but worst case we'll just end in the same exact spot moving there step by step.
by opo | 2025-07-23 20:16:18+00:00
>Basically, in 1919, Henry Ford sought to reinvest the Ford Motor Company’s profits into raising employee wages

I don't actually see any reference in the wikipedia article that Ford was saying he wanted to use the dividend money to raise wages:

>...Henry Ford, sought to end special dividends for shareholders in favor of massive investments in new plants that would enable Ford to dramatically increase production, and the number of people employed at his plants, while continuing to cut the costs and prices of his cars.

And as usual in these cases, there are other unstated reasons that might actually be more important to the decision maker:

>...Ford was also motivated by a desire to squeeze out his minority shareholders, especially the Dodge brothers, whom he suspected (correctly) of using their Ford dividends to build a rival car company. By cutting off their dividends, Ford hoped to starve the Dodges of capital to fuel their growth
by tptacek | 2025-07-23 20:16:19+00:00
It's kind of a counterpoint to it! Meathead actively advocates against resting; Gritzer argues for a cooking method that relies on carryover time and thus resting to slice at target temps. Both Meathead and Gritzer agree that moisture retention is not the reason to rest, and since there's a lot of pop science out there (complete with animations and physical models) for why moisture loss demands resting, it seems worth writing about.

Gritzer actually ran a relatively serious tasting experiment for this article, though I'm not sure how much it mattered to the point he's making.
by joaohkfaria | 2025-07-23 20:16:23+00:00
Creating all of this is cool, but I don't know, it looks like a gimmick.

The whole argument is: "Every other page I find myself on now has an AI generated click-bait title, shared for rage-clicks all brought-to-you-by-our-sponsors–completely covered wall-to-wall with popup modals, telling me how much they respect my privacy"

Well, you'll still need content outside your friends group. Even with the "Promised LAN" you'll continue having the same experience.

And what for? What are the use cases? Exchange files? Jokes? Chatting? The examples given: "It’s incredible how much network transport and a trusting culture gets you—there’s a 3-node IRC network, exotic hardware to gawk at, radios galore, a NAS storage swap, LAN only email, and even a SIP phone network of “redphones”."

Ok, fun. But you'll still need WhatsApp/Facetime to talk to your mom, the whole internet to search and learn, sometimes social networks to communicate or to get a job, etc etc etc.
by 0x457 | 2025-07-23 20:16:40+00:00
Uhm, having a weather api is probably the easiest thing to implement because of how catchable it is. Any public api accidental can be prevented by tiered rate-limiting:

- uber low limits for anon access

- low, but reasonable for register free users

- Up-to-you for paid users

You might say: well, proxies are cheaper than paid plan, and solution to that - charge reasonable price.
by throw0101b | 2025-07-23 20:16:50+00:00
> https://gizmodo.com/republicans-project-2025-would-end-free-...

John Oliver did an episode on this during Trump 1.0:

* https://www.youtube.com/watch?v=qMGn9T37eR8

* https://www.imdb.com/title/tt11110660/

* s06e26: https://en.wikipedia.org/wiki/List_of_Last_Week_Tonight_with...

* https://old.reddit.com/r/television/comments/dhmo0c/weather_...
by lotsofpulp | 2025-07-23 20:16:50+00:00
Fair is undefine-able. Is it a set volume of water per person? Or is it a set volume of water per person per kilogram? Is it different by gender? By age or physical ability?

For the purposes of distributing a limited resource, it seems a power law formula is most fair, with a sufficiently steep curve to keep total consumption within resource limits.
by kelnos | 2025-07-23 20:17:12+00:00
No, the conclusion is that the specific act of resting has no bearing on juiciness. The juice spillage depends on the temperature the meat is when you slice it.

Resting of course does lower the temperature, which reduces juice spillage, but a) that's a secondary effect, and b) blind tasters turned out to not know the difference between meat that lost more or less juice due to cutting at a higher or lower temperature, so it probably doesn't matter.

Carryover cooking is what matters, and we should care much more about what temperature we allow the meat to rise to after removing heat, because we will overcook the meat if we allow it to come to the target temperature (or even within 10-15F of it, depending on meat/cut/thickness) before removing heat. The article advocates for removing heat much earlier than most people probably do.
by reaperducer | 2025-07-23 20:17:48+00:00
I once rebuilt an internal employee directory tool, and added the ability for people to add an emoji below their name.

Before that, hardly anyone used the internal directory, which is probably why I inherited it (I was the stig). After the feature was added, people went nuts and used it all the time. I feel bad for the guy who runs it now, as I understand he is bombarded with feature requests from the employees.
by caseysoftware | 2025-07-23 20:18:46+00:00
I think you're off by about 80 years:

> Twenty-five years ago, Bill Clinton campaigned on an idea for limiting excessive pay for American CEOs: Cap the tax deductibility of top executives' compensation at $1 million, and companies, not wanting bigger tax bills, might reel in their pay. In his 1993 budget, advisers suggested a compromise: Companies couldn't deduct CEO pay over $1 million unless it was "performance-based."

> But many believe the loophole had the opposite effect, driving companies instead to pay more in stock options and certain performance-based bonuses, which actually supercharged the growth in CEO pay. In 1989, according to the left-leaning Economic Policy Institute, the median value of annual CEO compensation was $2.7 million. By 1995 it was $6.6 million, and it reached $13 million in 2016.

Ref: https://www.washingtonpost.com/news/on-leadership/wp/2017/11...
by Workaccount2 | 2025-07-23 20:18:53+00:00
Probably not, since you can't pay rent or buy groceries with shares. If the company is private this is even more of a headache as you may not see any money for years and the actual value wouldn't be firm until the sale is finalized.

If the company is public...you can just buy shares like anyone else (well depending on your position you might need approval).

Equity isn't a magical thing that prints millions. There are ample people on this forum that could tell you endless stories about "equity" and "getting rich"...
by BrawnyBadger53 | 2025-07-23 20:19:04+00:00
The current form of the system we practice is massively different from the one that put us so far ahead. We tried many things trying to push it to be more successful. This gap change is a result of some of that. We now need to evaluate whether that change was actually better. This gap may be short term worth it but with trends like quiet quitting, we probably should think about whether these changes will slowly cause larger long term losses in productivity at the lower ends of these hierarchies.
by swores | 2025-07-23 20:19:13+00:00
If that's so then apologies, my bad - I didn't see any details in this NASA news so just assumed it was similar logic to Boom Aerospace, whose strategy I believe is to somehow make the boom noise aim away from the ground (partly directly, and partly by figuring out a way to make sure that sound waves heading downwards bounce off the atmosphere back upwards, so that the boom exists just not audible to people at ground level).

And TIL I learn that it's even possible to break the sound barrier without a boom of some kind (assuming NASA haven't found otherwise and adopted Boom's strategy in the years since you were hearing about it from them). Cheers for the interesting comment!

Edit: although I hope somebody can answer sroussey's original comment of «What happens when there are 1000 flights over land all having sonic booms, and 1000 reflecting sonic booms, and the 1001 plane flies through all the sonic booms?», since if Boom are successful I assume they're more likely to have thousands (or at least enough to have overlapping flights at times) of planes in the air than NASA. Unless, I guess, NASA do such a good job of demonstrating that you can actually get rid of the boom rather than just redirecting where the sound waves go that Boom change their strategy to that and/or get outcompeted by rival companies doing the NASA way. ("Just" is a little unfair, since Boom's technique seems incredibly clever to me.)
by kulahan | 2025-07-23 20:19:32+00:00
Luck isn’t real anyways. It’s actually all about getting yourself in front of opportunities as often as possible, learning to recognize when they show up, and acting on them ASAP. That’s all it is. I consider myself extremely lucky, but that’s just another way of saying I’ve seen a lot of the opportunities in my life and consciously decided which to chase, rather than floating through the river of fate aimlessly.
by throw0101b | 2025-07-23 20:19:37+00:00
Yeah:

> "The Pentagon ... announced that we are eliminating woke climate change programs and initiatives inconsistent with our core warfighting mission," [Chief Pentagon Spokesman Sean Parnell] said.

* https://www.defense.gov/News/News-Stories/Article/Article/41...

See also "Pentagon Starts Purging Climate Change Measures":

* https://www.scientificamerican.com/article/trump-pentagon-pu...

But from 2021 (during Biden), "Climate change is a risk to national security, the Pentagon says"

* https://www.npr.org/2021/10/26/1049222045/the-pentagon-says-...
by demetris | 2025-07-23 20:20:29+00:00
Trixie is SUPER for desktop use!

I’ve been on sid for the last 10 months for my laptop (old T450s) and my secondary desktop, and it is really fun.

There are annoyances but they are not related to Debian itself.

FIRST

I decided it is time to switch to Wayland. Now my favorite run-or-raise app (Kupfer) cannot do run-or-raise. But there is a really nice extension to do run-or-raise on GNOME without the aggressive disruption of the Activities overview: Switcher. The other thing that is difficult on Wayland is text expansion. I have not found a solution for that part.

SECOND

The annoying to infuriating things that GNOME likes doing sometimes. But that is a constant. Nothing new.

Congrats and thanks to all the Debian people!
by cess11 | 2025-07-23 20:21:06+00:00
I like Manticore. It's easy to setup, lean on resources and quite fast. I use it when I want to quickly pour a lot of semi-structured text into a database for exploratory browsing and prototype web applications.

The auto-bolding of query terms in responses is quite convenient and has allowed me to skip annoying little regexes many times. Maybe other engines have it too and I never noticed?
by 01100011 | 2025-07-23 20:21:17+00:00
Same year here. Actually the battery charging issue left us stranded a few times but only once in public. It was the faulty fuel gauge firmware that left us stranded on the side of the I-5 freeway in the middle of CA.

The CVT sort of sucks. Mostly ok but we have a long lag between reverse and drive which causes the car to jerk forward if you try to accelerate before the forward motion starts. The turning radius is amazing though.

My father in law is a Toyota mechanic and warned me to get rid of the car before 100k miles though as more recent subies are as reliable as they used to be.