MurphyA/hacker-news huggingface dataset:
by icemanx | 2025-08-23 09:41:51+00:00
Definitely vibe code, and I agree with the others - please mention it in the README if you want people to use AI generated code. You are not the mind behind it

Update: Looking through your code, I already found within 5 minute flaws, since it is obvious that you have not written it (looking at your past work, I doubt you even understand what it does), I will not even point the issues out.
by littlestymaar | 2025-08-23 09:42:46+00:00
The key problem with Zig nowadays is how much of its community and adoption is driven by anti-Rust sentiment. As a result, while Rust puts beginner onboarding and documentation at the center of its culture, as opposed to the “C neckbeard”'s culture, Zig is going the other way around.

(Loris Cro being a key community figure isn't helping in any way, and it's a good remainder that if you don't clear up your community from bullies from the beginning, they will turn your entire community to a miserable place. And that's a shame because from what I've seen, Andrew Kelley seems to be a very cool guy in addition to being very smart).
by hexfish | 2025-08-23 09:44:34+00:00
Re: the bank apps: that really depends on the bank and the country. I live in a eu-west country and there are afaik no apps that do not run on Graphene (which did suprise me I must admit).

Whatsapp can work if you use sandboxed Google Play (I still use a Google account, I just don't want gplay to have effectively root on my device).

Depending on the level of integrity check your app might just work. Gory details: https://grapheneos.org/articles/attestation-compatibility-gu...

And like others said: no contactless payment, but I dont use that personally anyway.
by em500 | 2025-08-23 09:46:04+00:00
California GPA average is about 3.0 with 1.5 standard deviation. A 6.4% SD improvement would be a 0.1 point improvement in GPA. Certainly not an overwhelming result, compared to the subjective reactions how phones and screen are “obviously” destroying kids lives/attention spans/ability to hold a conversation, etc.
by Telaneo | 2025-08-23 09:46:39+00:00
He's doing a video about a format, not about video itself. How much of this video is comparisons of video itself? None that I could see. He's already done that video way back with his Betamax vs. VHS comparison.

All the cases of him comparing the form factor, that is, the size of the casette, with something else, are easily shown with either pictures or diagrams.
by simonask | 2025-08-23 09:46:41+00:00
I mean, there's no question that Zig, also in its current state, is vast improvement over C or even C++ - for the "small stuff". It is much more pleasant to use.

But there is still the "big stuff" - the things that have a fundamental, architectural impact. Things like: Will my program be multithreaded? Will I have many systems that interact? Will my program be maximally memory-efficient? Do I have the capacity (or money) to ensure correctness if I say "yes" to any of that?

The most important consideration in any software project is managing architectural complexity. Zig is better, yes, but not a paradigm shift. If you say "yes" to any of the above, you are in the same world of pain (or expenses) as you would be in C or C++. This is the reason that Rust is interesting: It makes things feasible/cheap that were previously very hard/expensive, at a fundamental level.
by maxbond | 2025-08-23 09:46:42+00:00
> I like math but showing someone a giant graph isn’t always the best approach. :)

Agreed. 3Blue1Brown has, by making their videos, publishing Manim, and critically by fostering a broader community of math YouTubers instead of trying to hoard the audience for themselves (through SoME), moved mathematics pedagogy forward immensely. (Sal Khan also deserves credit here.) He's created a genre that makes math feel like an exciting and approachable journey, rather than a process of memorization and symbol manipulation.
by afavour | 2025-08-23 09:46:58+00:00
> The GP asked for a citation for XSLT support going behind a flag in the next version of Chrome

> Add flag to disable XSLT

Two very different things. OP is talking about XSLT support going behind a flag, you’re citing XSLT deprecation going behind a flag. The default state matters (and the default state is undeprecated)

It makes sense that the Chrome team would do what they’re doing, otherwise it’s very difficult for anyone to assess the impact of XSLT deprecation.
by Vespasian | 2025-08-23 09:47:45+00:00
As others gave said the UK left the EU 10 years ago.

Chat control (which isn't (yet) a thing) would not in fact lead to the outcome you describe.

Any company would be forced to comply or get the boot from EU market. Apple and Google will happily enforce that and that's probably good enough initially.

US Vendors could also decide to create an EU only version of their services.
by defrost | 2025-08-23 09:49:33+00:00
> My grandfather did welding for Bethlehem Steel as did my father.

A company from 1857 that scarcely advanced it's Health & Safety practices.

> And that's not to mention just the baseline damage from lugging and hauling and hefting heavy pieces of metal.

Exactly - modern metal fabrication workers, fitters, turners, machinists, et al use forklifts, overhead cranes, eye protection, breathing rigs that filter out toxins and cool the face, and essentially work smart .. and that's been my experience since I first TA'd in a mining locomotive shed back in the late 1970s.

You can see examples of this in the heavy industry repair domain here:

https://www.youtube.com/@CuttingEdgeEngineering/videos
by jjani | 2025-08-23 09:49:34+00:00
> Here's the catch. Because of these constraints Korean conglomerates don't create as many jobs.Korean software or services industry is almost non existent or heavily constrained to Korea.

What? Korea's software jobs per capita is one of the highest of all wealthy (let's say top 30 HDI) countries. Please stop claiming this sort of stuff without being familiar with the country.
by bsder | 2025-08-23 09:50:44+00:00
So, your hands have no oil or dirt on them after working a welding shift? Wow, I'd love to take a tour of your workplace.

Even if you've got protection on, you still get exposed little by little. If someone is welding next to you on a site, you get exposed. If you have slag, you are breathing vaporized chemicals and heavy metal ions unless you a wearing a closed system breather. Any solvents or fluids tend to be some level of toxic. etc.

Welding is more than just putting rod to metal. You cut things. You grind things. You apply chemicals in preparation. Nobody is dressed in an environmental hazard suit all day--lack of mobility and peripheral vision is its own industrial hazard.

If you're covered in grime at the end of the day, well, all that crap is toxic to some degree.
by JimDabell | 2025-08-23 09:51:14+00:00
> My point was that they could have simplified the parser logic and implementation buren by dropping that. But they didn't.

You’re right, and I think this is possibly the biggest mistake the HTML5 standards process ever made. They got that one badly wrong. Strict XML-based parsing was the clearly correct solution informed by many years of Postel’s Law constantly fucking the web up with incompatibilities and security vulnerabilities.

> So dropping XSLT support here is purely because they don't want to put the effort in implementing their own XSLT engine

That’s not the whole answer; they think the benefits don’t justify the effort, and I agree with that.

> And dropping XSLT goes against why HTML 5/LS was originally created, which was to support all existing HTML and web content no matter what they looked like.

That wasn’t why HTML5 was created. That makes no sense; you don’t need a new format to preserve the status quo.
by olaulaja | 2025-08-23 09:51:47+00:00
It can be rather difficult, mostly due to the occlusion calculations having to be conservative (must count visible things as visible, allowed to count invisible as visible, or things pop) and latency (must account for every possible position within max move speed * max latency, or things pop)

The naive raycast from player camera to other player would be fine for perf but may count partially visible as invisible, so its unacceptable. You'd have to raycast every pixel of the potentially visible player model to stay conservative. With movement + latency this expands to every pixel the player model could potentially occupy during your max latency period, and you need to consider the viewer moving too!

In practice this expands to a visibility test between two spheres with radius max_latency*max_movespeed + player_model_radius. Now, you could theoretically do a bunch of random raycasts between the spheres and get an answer that is right some of the time, but it would be a serious violation of our conservativeness criteria and the performance would get worse with more rays/better results. Also keep in mind that we need to do this for every single player/player pair a few dozen times per second, so it needs to be fast!

To do this, you need a dedicated data structure that maps volumes to other volumes visible from said volume. There are a few, and they are all non-trivial and/or slow to build well. (google for eg. potentially visible set, cell-portal graph + occlusion). You also trade performance for precision, and in practice you walls might become 'transparent' a bit too early. With all this being done, we can actually "do occlusion calculations server-side".

There's just one problem with this that I still don't know a solution for, namely precision. With fast players and imprecise conservative visibility, things you care about are going to count as visible pretty often, including stuff like enemies peeking from behind a corner (because they could have moved at full sprint for 100ms and the end of the wall is rounded away in your acceleration structure anyway) so all this complexity might not get you that much, particularly if your game is fast paced. You'd prevent some wallhacks but not the ones that really matter.

TLDR yes, it's actually hard and might not be good enough anyway
by flohofwoe | 2025-08-23 09:52:08+00:00
> already has an engine for building websites with Zig, but making sure that every Zig library has docs

Tbh, this sort of auto-generated docs from source code is not all that useful, since you get that same information right in the IDE via the language server.

The important documentation part that's currently missing is how everything is supposed to work together in the stdlib, not the 'micro-documentation' of what a single type or function does. And for this sort of information it's currently indeed better to look at example code (e.g. the stdlib's testing code).

IMHO it's way too early for this type of high-level documentation, since things change all the time in the stdlib. Putting much work into documenting concepts that are discarded again anyway doesn't make much sense.
by MutableLambda | 2025-08-23 09:52:16+00:00
I actually wanted to try webtop for a long time, and did it only recently. I could not figure out these selkies for the life of me. It wanted a bunch of ports, was complaining about something all the time (don't remember, it's been a month). Might be a skill issue, but I've been using docker for the past 10 years. Moreover they want root access to the host system, which kind of defies one of the reasons to use containers. Is there a video that explains the benefits in a good way? I mean, if it's for gaming only, I can understand the use-case, but say you just want to run something like Gnu Radio in a container, why would I need 60 fps and root permissions for that.
by Hilift | 2025-08-23 09:53:56+00:00
The person who leaked the video worked in a police dispatch center. Those personnel aren't supposed to leak information. Would it be ok for an EMS tech to leak videos? How about a surgeon? The incident occurred in public view with many existing videos and eyewitnesses and other telemetry information. It wasn't like this guy was swinging for the fences to get the Zapruder tape to us.
by vasco | 2025-08-23 09:54:10+00:00
When computers get much better at doing stuff I'd think more people would want to work with computers, this to me seems obvious. There will be even more computers and more people needed to deploy them and operate them. And by the time that is automated, most other jobs that require physical jobs will have robots doing them anyway, so it really is hard for me to understand that as computers get better people predict less people will work with them. Better tool = more of that tool. Paperclip would also say that over a long period of time all of our energy and available space would go to more and more compute. It's hard to think anything else is safer than computer.
by perihelions | 2025-08-23 09:54:44+00:00
> "They're right to point out that laws like this are primarily motivated by government control of speech. On a recent Times article about the UK's Online Safety Act:"

Err, BlueSky is enthusiastically complying with that one (as you read by clicking through to their corporate statement),

> "We work with regulators around the world on child safety—for example, Bluesky follows the UK's Online Safety Act, where age checks are required only for specific content and features... Mississippi’s new law and the UK’s Online Safety Act (OSA) are very different. Bluesky follows the OSA in the UK. There, Bluesky is still accessible for everyone, age checks are required only for accessing certain content and features, and Bluesky does not know and does not track which UK users are under 18. Mississippi’s law, by contrast, would block everyone from accessing the site—teens and adults—unless they hand over sensitive information, and once they do, the law in Mississippi requires Bluesky to keep track of which users are children."

https://bsky.social/about/blog/08-22-2025-mississippi-hb1126

It's bold of them to attempt to shift the Overton Window in this way ("OSA is actually moderate and we should hold it up as an example of reasonableness to criticize other censorship laws against"). That happened fast.
by kristoff_it | 2025-08-23 09:54:46+00:00
> I think the argument is that it is also extremely difficult to write low level libraries in Zig, just as it is in C.

This has been not my experience at all in the ~6 years I've been writing Zig. I started having very little experience writing C (<1000, lines all written while in university) and since day 1 Zig has been a tremendous improvement over it, even back when it was at version 0.4.0.
by mvdwoord | 2025-08-23 09:55:33+00:00
- 4x NVIDIA RTX 6000 PRO Blackwell Max-Q (384GB total VRAM).

- 8TB of NVMe PCIe 5.0 storage.

- AMD Threadripper PRO 7975WX (32 cores, 64 threads). - 256GB ECC DDR5 RAM.

- 1650Watts at peak (runs on a standard 15Amp/120V circuit).

For training, AI research, and deploying models locally. A datacenter-class AI rig you can keep under your desk.

We are planning to make a limited number of these a16z AI Workstations.
by bsder | 2025-08-23 09:56:10+00:00
Erm: https://youtu.be/NZf-fTK7q7E?t=592

Sure, he has eye and ear protection. But he's just inhaling the dust from that stuff.

Even worse, he's using old school stick welding that's actually been banned in multiple places because it was so stupidly toxic.

All your video did was reinforce that, yeah, industrial work looks exactly like what I expect it to look like and it still sucks.
by zelphirkalt | 2025-08-23 09:56:14+00:00
People state these things about Rust's own implementation (or one of the other gazillion safe langs) potentially not being safe all the time, but the difference to unsafe languages is, that once any bug is fixed, everyone profits from it being fixed in the implementation of Rust. Everyone who uses the language and updates to a newer version that is, which often goes without code changes or minimal changes for a project. Now compare that with unsafe languages. Every single project needs to "fix" the same kind of safety issues over and over again. The language implementation can do almost nothing, except change the language to disallow unsafe stuff, which is not done, because people like backwards compatibility too much.
by meander_water | 2025-08-23 09:56:18+00:00
Great advice all round.

> Take time with learning

But this one in particular stands out. We are being constantly pushed to ship code at faster and faster rates. AI has only hastened the process.

If you want to learn anything new you have to slow it down, push back against all the forces urging you to do more, ship more, make more money.

If you're using AI tools, do the opposite of what everyone else is doing. For every piece of generated code you accept, scrutinize every line, ask clarifying questions, ask for alternate implementations, ask what the tradeoffs are.

Just be curious.

This will be slow, but that's the point.
by flohofwoe | 2025-08-23 09:56:47+00:00
> Zig is better, yes, but not a paradigm shift.

But it doesn't have to be and it shouldn't. Rust also isn't a paradigm shift, it "just" solved static memory safety (admittedly a great engineering feat) but other languages solved memory safety too decades ago, just with more of it happening at runtime.

But in many other areas Rust copied too many bad ideas from C++ (and many of those "other things" Zig already does much better than Rust - but different people will have vastly different opinions about whether one solution is actually better than another - so discussions about those features usually run in circles).

There shouldn't be a single language that solves all problems - this will just result in stagnation, it's much better to have many languages to pick from - and even if they just differ in personal opinions of the language author of how to do things or entirely subjective 'syntax sugar' features. Competition is good, monocultures are bad.

> The most important consideration in any software project is managing architectural complexity

No language will help you managing "architectural complexity" in any meaningful way except by imposing tons of arbitrary restrictions which then get in the way for smaller projects that don't need much "architecture". We have plenty of "Enterprise-scale languages" already (Java, C#, Rust, C++, ...), what we need is more languages for small teams that don't get in the way of just getting shit done, since the really interesting and innovative stuff doesn't happen in enterprise environments but in small 'basement and bedroom teams' :)
by solatic | 2025-08-23 09:58:33+00:00
Welding is supposed to be future-proof? At $90+/hour for unionized labor? Don't make me laugh. Look at the work Boston Dynamics has already done with neural networks and tell me that we're not going to see robots doing perfect welds in any space a human could reach, 24/7 around the clock without any need for rest breaks.

https://youtu.be/HYwekersccY?si=p5BZaGOUQJsqd1f_

What's the case for optimism here?
by frou_dh | 2025-08-23 09:58:38+00:00
Well it is quite literally writing, and fairly often starting with a blank page (file) and then doing a lot of editing.

---

Talking of pages, I quite often write down on a physical notebook what I'm trying to accomplish. Because if I just dive straight into hacking code I sometimes get a frenzied feeling, as if I'm just bouncing around like a pinball in an undisciplined way.
by porridgeraisin | 2025-08-23 09:58:47+00:00
I am still in the market for a laptop that a) has good linux drivers b) has a big battery ~80wh or more c) metal build d) good touchpad, screen, keyboard, e) strictly no dGPU. I genuinely don't care about the CPU, all of them are good enough for me. Although I suppose if I'm going to be spending on a laptop in 2025, I will be looking for one with 24 or 32GB of RAM instead of 16GB.

Macbook Pros satisfy b), c), d) and e). I currently have an HP laptop that satisfies a), c), d), and e). But is just 43Wh (now 36Wh after a few years).
by oblio | 2025-08-23 09:59:03+00:00
I like Zig, but if we look at the numbers, the difference is probably more to do with funding that anything:

Zig (programming language) - First appeared 8 February 2016; 9 years ago

Rust (programming language) - First appeared January 19, 2012; 13 years ago

Also, Zig at this point isn't really a brand new language anymore. I have comments on their issues dating back to 2018, so it's been a very active language since at least then.
by imtringued | 2025-08-23 10:00:24+00:00
The bitter lesson type of strategy would be to implement heterogeneous experts inside an MoE architecture so that the model automatically chooses the number of active parameters by routing to experts with more parameters.

This approach is much more efficient than the paper of this HN submission, because request based routing requires you to recalculate the KV cache from scratch as you switch from model to model.
by sgt | 2025-08-23 10:00:31+00:00
Sure but once you have WAL logs, you suddenly have a more heavy weight setup. Backing it up you'll want to back up those WAL logs to achieve proper point in time recovery, and so on. My point is, you're now bolting on extra stuff on it to do things that Postgres can do (which can be pretty light weight). Not disrespecting SQLite, still one of my favorite DB's.
by adithyassekhar | 2025-08-23 10:01:44+00:00
Depends on whether you are working for someone or building for yourself.

If you work for someone, you are essentially plumbing, you will still find faults with their ideas and inform them. But you don't make the call to change that idea, nor do you have the burden of living with the finished product. It doesn't have your name attached to it. No one will call it, siva7's crm, you will move on to the next project.

Now, if you are building something for yourself, you are the creative writer. It's your call, it's your want, it'll have your name attached to it. You can move on, but in everyone's mind and your own, it's your creation.
by MortyWaves | 2025-08-23 10:03:06+00:00
All the examples I see is there’s a network unit file, a cron unit file, etc all for one application. It would be nice to colocate.

Then there is composition of multiple applications too.

With docker compose I have a single file for running all my services.

With systemd it has to be N number of files for each service too.
by dghf | 2025-08-23 10:03:21+00:00
The difficulty in navigating to arbitrary locations in file open/save dialogs.

I wanted to attach a build log to a Teams post (maybe we shouldn't be using Teams on Mac, but it's a corporate decision that's out of my hands), and I could not for the life of me figure how to get the file-selection dialog to look at the relevant folder (which was somewhere under /private/). In the end, I had to use iTerm to copy the file to somewhere the dialog could find.
by simonask | 2025-08-23 10:04:48+00:00
I think you are moving the goal posts. You use the `memmap2` crate, or the `libc` crate if you want to be reckless about it. The question was how the standard library gets in your way, not whether it includes everything you need.

And I don't think that including every feature of every possible OS is a sensible position to have for a standard library. Or would you argue that it should also include things like `CreateWindowExW()`?

If all you use is the Rust standard library, you can be reasonably sure that your program works on all platforms, and memory mapping is something that is highly platform specific, even among POSIX-likes. I would not like to attempt designing a singular cross-platform API for it that has to be maintained in perpetuity.

(There are a few OS-specific APIs in the Rust standard library, mostly because they are required anyway for things like I/O and process management. But the limit has to be set somewhere.)
Ask HN: Is it possible to do great things in STEM in a not so great country?
by shivajikobardan | 2025-08-23 10:04:54+00:00
I am from Nepal. And I really wanted to do some computer science stuffs at depth level. like graphics programming jobs. But is it even possible as someone from Nepal(not a great country) to do something great in the field of Science and Technology? Migrating away is obviously not an option in 2025 and onwards. It feels like dead-end.