MurphyA/hacker-news huggingface dataset:
by latexr | 2025-10-11 09:55:19+00:00
I always thought the name AV1 was partly a play on/homage to AVI (Audio Video Interlace), but AV2 breaks that. Even if it’s meant to be embedded into other container formats such as MP4, there are files with the .av1 extension and there is a video/AV1 MIME type (and possibly a UTI?). Does this mean we now need to duplicate all that to .av2 and video/AV2? What about the AVIF file format?
by nchmy | 2025-10-11 09:57:29+00:00
I'm extremely interested in this sort of use case and am regularly disappointed to find that very few others are. And even fewer are interested in doing it in a hypermedia-first way.

There's two ways this could be approached.

1. Just cache the backend-generated html that has datastar attributes in it, and serve it from a service worker. Datastar library in the main thread won't know or care whether it came from service worker, edge worker or your backend.

2. If there's a need for dynamic data/templating (eg user-specific into), you can do so in the service worker - if you've stored the templates and data already. But that has little to do with datastar - you'd have to do that in any case.

However, service workers have limitations with regards to things like dynamic script imports, using es modules etc. You can send messages to a dedicated web worker which handles rendering and returns the html, but it does get complicated. Sharedworker would be even better but android chromium still doesn't support it - but they're finally trialing it and hopefully it'll be available in 6 months.

The only datastar-specific consideration is if you want to do something like stream sse events from the "backend" to the datastar library in the main thread/dom. The TypeScript/JavaScript sdk works just fine in the service worker as well, and can maintain a long-lived connection to periodically stream new messages. Of course, service worker lifecycle is somewhat of a black box and out of your control, but that has nothing to do with d*.

So, overall, yes you can use datastar offline. But it comes with all the issues that you'd face with another approach.
by Nevermark | 2025-10-11 09:58:02+00:00
> the dodgy GenAI calculator image

It appears human beings are already forgetting the even more dodgy images some of us created before AI allowed us to reduce said dodginess. Or actually get a picture we could post without too much shame. :)

And in this case, IMHO, the image has a significant amount of dodgy vintage tech charm.

Not every use of AI replaces a professional artist.
by zevon | 2025-10-11 09:58:20+00:00
Good time to bring it back. You used to have to sideload the iOS app for years and the new app makes using an old Pebble with an iPhone so much easier. :) I've been using the app for a few weeks and it generally works well but not everything is already functional. No voice replies, no health tracking, no canned messages, yet, for example.

Here's the changelog: https://ndocs.repebble.com/changelog
by gusgus01 | 2025-10-11 10:00:35+00:00
The OP said "relevant individual on the left calling for violence".

I guess we can quibble about "relevant", but none of those examples really fits the criteria as it stands.

"Many People" - anyone relevant? And were they calling for violence?

The Democrat who wished a political opponent "two bullets to the head" did so in personal texts 3 years ago. Not exactly calling for it, let alone nationally on television.

"Cheering for Luigi" - again relevant people who did? And called for violence?
by M95D | 2025-10-11 10:00:43+00:00
You can safely bet agains any large scale war like WW2. We no longer have the money or resources for that. We can't build hundreds of thousands of airplanes, tanks, ships, guns, etc. This doesn't include nukes. We have lots of those. But any nuke war will be very very short, over in a day, not like WW2.
by rendall | 2025-10-11 10:03:25+00:00
The article is no more about transistors or literal frame-pointer hardware than a discussion about the QWERTY keyboard layout is about the metallurgy and mechanics of typewriter arms.

It's about how early design choices, once reinforced by tooling and habit, shape the whole ecosystem's assumptions about what’s "normal" or "efficient."

The only logical refutation of the article would be to demonstrate that any other computational paradigm, such as dataflow, message-passing, continuation-based, logic, actor, whatever, can execute on commodity CPUs with the same efficiency as imperative C-style code.

Saying "modern CPUs don't have stack hardware" is a bit like saying "modern keyboards don't jam, so QWERTY isn't a problem."

True, but beside the point. The argument isn't that QWERTY (or C) is technically flawed, but that decades of co-evolution have made their conventions invisible, and that invisibility limits how we imagine alternatives.

The author's Stockholm Syndrome metaphor isn't claiming we can’t build other kinds of CPUs. Of course we can. It's pointing out how our collective sense of what computing should look like has been quietly standardized, much like how QWERTY standardized how we type.

Saying that "modern CPUs are mostly caches and vector units" is like saying modern keyboards don't have typebars that jam. Technically true, but it misses that we're still typing on layouts designed for those constraints.

Dismissing the critique as fighting 1980s battles is like saying nobody uses typewriters anymore, so QWERTY doesn’t matter.

Pointing out that C works fine on architectures without a frame pointer is like noting that Dvorak and Colemak exist. Yes but it ignores how systemic inertia keeps alternatives niche.

The argument that radical CPU designs fail because hardware and software co-evolve fits the analogy: people have tried new keyboard layouts too, but they rarely succeed because everything from muscle memory to software assumes QWERTY.

The claim that CPU internals are now nothing like their ISA is just like saying keyboards use digital scanning instead of levers. True, but irrelevant to the surface conventions that still shape how we interact with them.

This dismissive pile-on validates the article's main metaphor of Stockholm Syndrome surprisingly directly!
by flohofwoe | 2025-10-11 10:03:41+00:00
D3D (up to D3D11 at least) is also a "managed" API since it uses refcounting to keep resources alive for as long as they are used by the GPU, there really isn't much difference to garbage collection.

Metal allows to disable refcounted lifetime management when recording commands since it actually adds significant overhead and D3D12 and Vulkan removed it entirely.

Unfortunately WebGPU potentially produces even more garbage than WebGL2, and we'll have yet to see how this turns out. Some drawcall heavy code actually runs faster on WebGL2 than WebGPU which really doesn't look great for a modern 3D API (not mainly because of GC but every little bit of overhead counts).
by Negitivefrags | 2025-10-11 10:03:59+00:00
AI upscaling is equivalent to lowering bitrate of compressed video.

Given netflix popularity, most people obviously don’t value image quality as much as other factors.

And it’s even true for myself. For gaming, given the choice of 30fps at a higher bitrate, or 60fps at a lower one, I’ll take the 60fps.

But I want high bitrate and high fps. I am certainly not going to celebrate the reduction in image quality.
by wtallis | 2025-10-11 10:04:28+00:00
And they're achieving "acceptable" frame rates and resolutions by sacrificing image quality in ways that aren't as easily quantified, so those downsides can be swept under the rug. Nobody's graphics benchmark emits metrics for how much ghosting is caused by the temporal antialiasing, or how much blurring the RT denoiser causes (or how much noise makes it past the denoiser). But they make for great static screenshots.
by MomsAVoxell | 2025-10-11 10:05:41+00:00
Sunlight-powered computing is an idea that is very, very ripe for arrival. It needs to happen.

I sincerely hope we see, within a few years from now, e-ink laptops where one side of the screen and the underneath surface of the laptop consist of solar cells, and all one need do for a daily/weekly charge, is tilt the laptop in teepee orientation and let it charge, charge, charge.

I've already decided personally to get off the grid as soon as possible - in my case, in the form of a sailboat outfitted with as much solar panels as possible. Having a solar powered laptop has been a fantastic dream for decades - I really think it's going to happen, commercially and successfully, within the next few years.

I could already power my iPad and uConsole with portable solar and battery banks. This all just needs to get integrated, and someone is going to have a HUGE HIT on their hands ..
by amiga386 | 2025-10-11 10:05:49+00:00
Yes, and it's allowing the format to change to allow more cleverness or apply more processing power.

For example, changes from one frame to the next are encoded in rectangular areas called "superblocks" (similar to a https://en.wikipedia.org/wiki/Macroblock). You can "move" the blocks (warp them), define their change in terms of other parts of the same frame (intra-frame prediction) or by referencing previous frames (inter-frame prediction), and so on... but you have to do it within a block, as that's the basic element of the encoding.

The more tightly you can define blocks around the areas that are actually changing from frame to frame, the better. Also, it takes data to describe where these blocks are, so there are special limitations on how blocks are defined, to minimise how many bits are needed to describe them.

AV2 now lets you define blocks differently, which makes it easier to fit them around the areas of the frame that are changing. It has also doubled the size of the largest block, so if you have some really big movement on screen, it takes fewer blocks to encode that.

That's just one change, the headline improvement comes from all the different changes, but this is an important one.

There is new cleverness in the encoders, but they need to be given the tools to express that cleverness -- new agreement about what types of transforms, predictions, etc. are allowed and can be encoded in the bitstream.

https://youtu.be/Se8E_SUlU3w?t=242
by nerdponx | 2025-10-11 10:06:53+00:00
Serious question: how often does a sensible default configuration need to change? I think I have used the same jedi-language-server config across projects and computers since before Neovim had a built-in LSP client, with the only changes being on the Neovim side gradually migrating to new features as they appeared.

Obviously do whatever works for you. But I do feel like most LSPs shouldn't need more than a few lines that you set and forget.
by pixelpoet | 2025-10-11 10:06:56+00:00
As you can tell, I'm patient :) A very important quality for any ray tracing enthusiast lol

The ability to do irregular sampling, efficient shadow computation (every flavour of shadow mapping is terrible!) and global illumination is already making its way into games, and path tracing has been the algorithm of choice in offline rendering (my profession since 2010) for quite a while already.

Making a flexible rasterisation-based renderer is a huge engineering undertaking, see e.g. Unreal Engine. With the relentless march of processing power, and finally having hardware acceleration as rasterisation has enjoyed for decades, it's going to be possible for much smaller teams to deliver realistic and creative (see e.g. Dreams[0]) visuals with far less engineering effort. Some nice recent examples of this are Teardown[1] and Tiny Glade[2].

It's even more inevitable from today's point of view than it was back in the 90s :)

[0] Dreams: https://www.youtube.com/watch?v=u9KNtnCZDMI

[1] Teardown: https://teardowngame.com/

[2] Tiny Glade: https://www.youtube.com/watch?v=jusWW2pPnA0
by 1718627440 | 2025-10-11 10:08:12+00:00
For anybody wondering, there are 112 of them:

a abbr address area article aside audio b base bdi bdo blockquote body br button canvas caption cite code col colgroup data datalist dd del details dfn dialog div dl dt em embed fieldset figcaption figure footer form h1 h2 h3 h4 h5 h6 head header hgroup hr html i iframe img input ins kbd label legend li link main map mark menu meta meter nav noscript object ol optgroup option output p picture pre progress q rp rt ruby s samp script search section select slot small source span strong style sub summary sup table tbody td template textarea tfoot th thead time title tr track u ul var video wbr
by Nevermark | 2025-10-11 10:08:24+00:00
I assumed the question was how to achieve the proper preconditions for cooking a chicken while avoiding any animal cruelty charges.

Clearly, we could simply knock its head off with a bat, since today I learned you can physically cook chickens with bats and professional batters, via a method well suited to humanity's eminent migration to outer space.

But I expect with some years of strength training and finesse, a very hard flick to the back of the chicken's lower noggin could dislodge the first cervical vertebrate from the skull, severing the spinal cord's integration with the brain stem.

Whether actually dead, or merely in a persistent vegetative state, the chicken may now be cooked.

However, if the chicken is merely headless [0], but in good health, one should not cook it.

[0] https://en.wikipedia.org/wiki/Mike_the_Headless_Chicken
by cutandjoin | 2025-10-11 10:09:11+00:00
I rethought MP3 editing without decoding/re-encoding for today’s hardware.

Existing tools tend to focus on one action at a time, like splitting or joining files. But Cjam lets you define multiple actions across multiple files at once using scripts. So it makes it easier to create and share more complex editing workflows.

You can find some example scripts on the forum: https://forum.cjmapp.net/viewforum.php?f=9
by ndsipa_pomu | 2025-10-11 10:09:36+00:00
That's very enlightening. I'm casually interested in traffic safety and road/junction designs from the perspective of a UK cyclist and there's a lot to be learnt from the safety culture/practices of the aviation industry. I typically think in terms of "safety margins" whilst cycling (e.g. if a driver pulls out of a side road in front of me, how quickly can I avoid them via swerving or brake to avoid a collision). I can imagine that hazardous states can be applied to a lot of the traffic behaviour at junctions.
by makeitdouble | 2025-10-11 10:10:05+00:00
The contentious part from what I get is the overhead for hallucinating these pixels, on cards that also cost a lot more than the previous generation for otherwise minimal gains outside of DLSS.

Some [0] are seeing 20 to 30% drop in actual frames when activating DLSS, and that means as much latency as well.

There's still games where it should be a decent tradeoff (racing or flight simulators ? Infinite Nikki ?), but it's definitely not a no-brainer.

[0] https://youtu.be/EiOVOnMY5jI
by rickydroll | 2025-10-11 10:10:53+00:00
There are multiple kinds of dead zones. The Gulf dead zones are caused by a lack of oxygen. Iron fertilization, afaik, works in a dead zone that lacks nutrients. A hypothesis for why the dead zones exist is whaling. What poop fertilized the ocean waters, boosting plankton populations, which made whale food. This observed cycle leads to the conjecture that iron is a necessary core nutrient, but you need other nutrients found in whale poop, leading to the creation of synthetic whale poop.

https://www.vice.com/en/article/scientists-are-dumping-fake-...

We do have evidence of iron fertilization boosting algae growth from the Australian fires' iron-rich smoke.

https://nicholas.duke.edu/news/australian-wildfires-triggere...

The big but is whether the iron-based fertilization will grow the right algae or not. Whatever works, we need boatloads of this stuff stat
by nchmy | 2025-10-11 10:12:21+00:00
Not at all, for many reasons.

HTMX doesn't do any client side interactivity. You need something like alpinejs for that. And alpine doesn't have signals, which are super useful (when used judiciously)

Datastar uses sse rather than websockets, which is simpler and more compatible http,web standards etc. Htmx can use either sse or ws, but both are a separate plugin.

Consequently, datastar does much more than htmx+alpine+ws/sse, in a fraction of the js size.

Htmx (and alpine, I think) introduces it's own html attributes whereas datastar uses spec-compliant data-* attributes (hence the name)

Htmx's api is much more complicated due to all of the extra attributes. Datastar is more concise.

Datastar has backend SDKs for all popular languages, to make it easy to send html fragment and signals updates via sse.

There's lots more as well. Very worth checking out.
by cutandjoin | 2025-10-11 10:14:10+00:00
Actually, I posted before using the main site link, and HN doesn’t allow posting the same URL twice, so I used the GitHub link this time.

https://news.ycombinator.com/item?id=43883180

And yes, Cjam is quite similar to mp3DirectCut. It’s like managing several mdc instances together in one list.
by Kon5ole | 2025-10-11 10:16:53+00:00
>The powerlines, transformers, etc. have to be paid for. These are not new costs, they're existing, ongoing costs.

That's true but powerlines exist to transport high voltage power from power plants to consumers far away, and transformers convert that to usable voltages.

Residential solar does not require any such powerlines or transformers, because the low-voltage power is consumed locally, where it's produced.

There was a story here recently about balcony solar installations in Germany. Basically a small solar panel adds power to your house through the house's existing wiring.

Rooftop solar works the same way, but is large enough that sometimes your surplus can be consumed by your neighbor as well, and when more people get solar it expands to the next neighborhood, and so on.

This is handled by the utilities already, since the effect of adding solar to your house is basically the same as if you stop using your stove or stop charging your car.

So it's kind of perfect initially - no new technical solutions are needed and no heavy investments since it just works with existing infrastructure.

Of course this becomes a problem eventually and will require storage solutions first of all and eventually also high voltage transmission. But not yet.

The real problem here is that large corporations live from the profits of selling electricity. They will protect that profit at all costs, so when demand drops - due to solar or anything else - they will increase the prices.

Note that they are not necessarily using that profit to properly maintain any infrastructure:

https://www.wattstrialfirm.com/powerful-results/historic-13-...
by nchmy | 2025-10-11 10:19:52+00:00
There's literally no ad hominem where you claimed there was. That itself is ad hominem.

I'll go further this time - not only do you not understand open source licensing or ecosystem even slightly, but it's genuinely concerning that you think that someone sharing some code somehow creates "a relationship" with anyone who looks at it. The point of free software is free software, and the good to the world is whatever people make of that.

Again, the only people who seem to be truly bothered by any of this are people who don't use datastar.

Don't use it. In fact, I suspect that the datastar maintainers would prefer that you, specifically, don't use it. Use it to spite them! We don't care.

I also retract my statement about you having good intentions/communicating in good faith. I won't respond to you again.
by tarasyarema | 2025-10-11 10:20:46+00:00
We use PW for the interaction with the browser, but really how we represent what to do is in a custom format (could be executed in other frameworks too). So the PW we could generate would be a subset, where the more interesting parts (custom functions) are not really implemented in PW.

Also part of our format is specially finding deterministic way of running steps, with automatic healing when failed. And we also build the whole system in a way that is self-hostable, so in the cases you mention you could be able to have control over what is run and where.
by PaulRobinson | 2025-10-11 10:21:10+00:00
The context you're missing is that Ryanair have routinely declared fuel emergencies in the past, and it seems an operational tactic - they want to carry less fuel to burn less fuel, and then have to regularly mayday to jump the stack on inbound, saving cash. That's not covered in the article, but you can sure as hell expect the CAA are going to take another look at them and their operations planning.

On this one, they did 3 attempted landings at Prestwick. [Edit: I now see that the third attempt was at EDI] What happened between the first and the second landing that made them think on their second go-around that a third attempt was more likely to succeed than the previous two? Was the wind dying down, or was the captain just feeling a bit braver or stupider? [Edit: I'm still curious as to what information they gathered that landing conditions were significantly different at EDI to make that diversion, given its relatively close and so likely to have similar weather].

Why was their final reserve Manchester when there were literally dozens of closer suitable airports, at least some of which are likely to have had better wind conditions by virtue of lower gusts, or more aligned to runway direction so not dealing with a strong crosswind?

There are many reasons I won't fly Ryanair, but not least because they have been shown over and over again to make reckless planning and operational decisions, and they are fortunate to have not had hull losses as a result. Time is ticking down, variance will catch them one day, and a sad & tragic catastrophe is only a matter of time. People will go to prison as a result, because this pattern of behaviour shows that this isn't "bad luck", it's calculated risk taking with passenger and crew lives to save money.
by jsheard | 2025-10-11 10:22:02+00:00
AFAICT it's not really different, they're just calling it something else for marketing reasons. The system described in the Sony patent (having a fixed-function unit traverse the BVH asynchronously from the shader cores) is more or less how Nvidia's RT cores worked from the beginning, as opposed to AMDs early attempts which accelerated certain intersection tests but still required the shader cores to drive the traversal loop.
by latexr | 2025-10-11 10:22:38+00:00
I’m not the person you replied to, but I believe you misunderstood OP’s point and are focusing on too narrow of a view regarding (what I perceive to be) their point.

> is that really a bad thing and is it as big a problem as you’re making it to be?

Yes, and yes. As way of example, I’m familiar with a particular subreddit which is used to promote far-right ideology in a specific country. They do it by grabbing news from anywhere in the world in which an immigrant has done anything “wrong”, no matter how small, and use it to stoke xenophobia in the subreddit’s country. They are making it seem these events are more prevalent than they really are, when they aren’t even happening in that country. It is a transparent tactic which nonetheless works.

> Supply chains are global and what happens in one corner of the world will most certainly have an impact on your local economy.

The overwhelming majority of news have nothing to do with supply chains and don’t affect them in the slightest.

> And besides, you don’t have to care. The news are just out there, free to be ignored.

The news live off ads and are made to be addictive. That’s why everything is reported with an insane sense of urgency. Most people consume news and social media the same way, without realising when it’s harming their mental health.

Even if you personally don’t watch the news, your fellow countrymen do and they act in response to them. You are affected by the news either you consume or ignore them.

> be aware and be moved by the struggles of other humans on the other side of the planet.

That’s not what most news are. Most are sensationalist garbage to get you to stay hooked. They are neither important nor urgent and they certainly aren’t designed to get you to empathise.