MurphyA/hacker-news huggingface dataset:
by wildzzz | 2025-08-20 20:39:55+00:00
Bond wires really are a thing of the past now except in niche applications or legacy chips. Flip chip designs have the die directly interface with a substrate that is then soldered to the board. With the kinds of speedy signals modern chips use, bond wires introduce impedance mismatch that degrades quality. This is related to why you don't see many new designs using pins.
by ModelForge | 2025-08-20 20:39:59+00:00
I'd say the common ones (besides educational) are

- private, on-device models (possibly with lower latency than models via web API); also edge devices

- algorithm research (faster and cheaper to prototype new ideas)

- cheap tasks, like classification/categorization; sure, you don't need a decoder-style LLM for that, but it has the advantage of being more free-form, which is useful in many scenarios; or maybe a sanity checker for grammar; or even a router to other model (GPT-5 style)
by craftkiller | 2025-08-20 20:40:14+00:00
IANAL but their official reason for the CLA seems pretty reasonable to me: https://www.gnu.org/licenses/why-assign.en.html

tl;dr: If someone violates the GPL, the FSF can't sue them on your behalf unless they are a copyright holder.

(personally I don't release anything under virus licenses like the GPL but I don't think there's a nefarious purpose behind their CLA)
by johnnyanmac | 2025-08-20 20:40:37+00:00
>But, and its a big BUT .... you can put all the donation, crowdfunding buttons that you like on your GitHub page. The reality is that will only get you so far.

I agree. Most people simply won't donate, be it individuals or companies using the tools.

>In the majority they are far more enlightened and open to contributing-back.

Ehh, it's mixed. A few companies won't mind going open source, some "open source", and many "open source but not really". Just having your code readable isn't the FOSS menality, and that's pretty much where the buck stops.

>Finally, regarding the FUD about "oh, its going to be shutdown tomorrow". That road is paved with examples where it DID NOT happen

Suvivor's bias doesn't really feel reassuring here. And just because it's not shut down doesn't mean it won't be subject to corporate rot. That's honestly worst than an honorable death.
by jimkri | 2025-08-20 20:40:38+00:00
I agree with your opinion. This statement you called out, “Reads all tokens at once.”, shows the misunderstanding, and then the document header formatting shows/proves the lack of attention used.

The headers go from numbered to having just 1 section with a sub-number. Section 3 has 3.1-3.4, and then the next section doesn't follow it.

I noticed this when doing large-scale LaTeX documentation builds if you are not explicit about the formatting. The well-scaffolded build falls apart since the token count is too high, and a proper batch process is not in place, or the prompt is vague. "Use clear headings and bullet points" is not precise. Depending on your document type, you need to state all requirements to design with attention.
by Imustaskforhelp | 2025-08-20 20:41:18+00:00
The Ai scrapers are most likely vc funded and all they care about is getting as much data as possible and not worry about the costs.

They are hiring machines at scale too so definitely bandwidth etc. are cheaper for them too. Maybe use a provider that doesn't have too much bandwidth issues (hetzner?)

But still, the point being that you might be hosting website on your small server and that scraper with its machines beast can come and effectively ddos your server looking for data to scrape. Deterring them is what matters so that the economical scale finally slide back to our favours again.
by wwfn | 2025-08-20 20:41:27+00:00
I can see "ill defined" causing problems. But isn't an explicit code of conduct more defined than none? (Assuming I'm reading that correctly from your comment.)

There aren't too many epithets floating around that offend me specifically. And I haven't heard anyone say I shouldn't/don't exist. So it's hard for me personally to feel the need for CoC and the like. But I'm all for policy that protects everyone against that kind of abuse -- which seems to be on the rise. Are there better alternatives?
by chamomeal | 2025-08-20 20:41:37+00:00
For stuff like adding generating and integrating new modules: the helpfulness of AI varies wildly.

If you’re using nest.js, which is great but also comically bloated with boilerplate, AI is fantastic. When my code is like 1 line of business logic per 6 lines of boilerplate, yes please AI do it all for me.

Projects with less cruft benefit less. I’m working on a form generator mini library, and I struggle to think of any piece I would actually let AI write for me.

Similar situation with tests. If your tests are mostly “mock x y and z, and make sure that this spied function is called with this mocked payload result”, AI is great. It’ll write all that garbage out in no time.

If your tests are doing larger chunks of biz logic like running against a database, or if you’re doing some kinda generative property based testing, LLMs are probably more trouble than they’re worth
by fabian2k | 2025-08-20 20:41:46+00:00
The entire main loop that queues jobs is then a single ForEachAsync that draws from the channel. And it just works, there are no real mistakes you can make with it.

Semaphores work well of course, as long as you don't make mistakes. Probably not an issue in your current version, but can easily happen if the code is more complex or especially when different developers later modify code like this. For example, you release the semaphore in a different class than the point where you acquire it, which makes this a bit less obvious than I'd like. If any developer later adds code that takes a different path this might break, and those kinds of bugs can be very annoying.

It's not really a problem with a simple case like this, but in general I don't use low-level concurrency primitives if there is a higher-level abstraction I can use that fits my problem.
by anktor | 2025-08-20 20:41:53+00:00
It's been mentioned but I want to add that the original idea of the post (mid size VPS hosting apache spark) might be missing that spark is ideal for distributed and resilient work (if a node fails the framework is able to avoid losing that work).

If you don't need this features, specially the distributed one, going tall (single instance with high capacity, replicate when necessary) or going simpler (multiple servers but without spark coordinating the work) could be good options depending on your/the team's knowledge
by jazzyjackson | 2025-08-20 20:41:55+00:00
email has come a long way with SPF, DKIM, and DMARC, and its cool that anyone can purchase a slice of the global namespace that is transferable between providers, but AFAIK the biggest road block to using email in a distributed self sovereign way is reputation and getting your messages delivered to google and outlook users partially because of the nonstop spam.

Do we have any new tools to prevent spam in a post-email world? Or can we just use the current email structure with some better GUI around PGP and Hashcash and force anyone who wants to send a message to burn 10 cents worth of electricity ?

I'm curious what you're looking for in an email standard ?
by skalidindi3 | 2025-08-20 20:42:08+00:00
^^^ This is an extremely underrated nitpick.

I am guessing that the HN audience would be / should be interested in that distinction. Mathematically speaking, chaos is an extreme sensitivity to initial conditions, and is very much still in line with deterministic systems. The resulting output, while seemingly random (since there is no easily identifiable pattern), is mathematically and conceptually different from actual randomness.
by WD-42 | 2025-08-20 20:42:11+00:00
It's the LSP plugin that finally drove me to leave ST4 for Zed. Language integration is table stakes for an editor now. The fact that ST support is behind a volunteer plugin instead of integrated directly in the editor just means it's never going to be as good as a editor that does have first class support. The ST devs need to actually improve the editor, but I haven't seen any material updates in years.
by ompogUe | 2025-08-20 20:42:22+00:00
Nope, they see the oil money as the important thing, and renewables aren't in their portfolios. The bigger economy and end-users are immaterial.

See also what happened when Stephen Harper became PM of Canada: they stopped science funding that didn't appeal to their interests and even auctioned off the data (the libraries of actual collected statistics) from various research stations.
by verdverm | 2025-08-20 20:42:26+00:00
We might be able to do this with permissioned spaces. There are instances or use-cases where you want an outside entity to make changes to a user's repo

- email / inbox [or @mail since it is @atproto :]

- unsubscribe from email

- notifications / rsvp

The cool thing is that we could use the stackable moderation infra for dealing with bad actors

https://bsky.social/about/blog/03-12-2024-stackable-moderati...
by sunshine-o | 2025-08-20 20:42:44+00:00
Yes, and there are probably a lot of immediate factors leading to that.

But this is the overall the result of an "anthropological reversal", meaning the society switch its focus on older generations rather than the younger ones.

Most policies in the last decades had the goal of favoring the silent and boomer generations ("boomers always win": ZIPR, assets inflation, etc.).

Millennials and Gen Z got wreaked, plus they know they might have to pay the debt left by the previous generations one way or another. So why not just dying, it is easier.
by autoexec | 2025-08-20 20:43:35+00:00
> people leaving their phones on Do Not Disturb, especially in the US where spam calls are rampant.

The solution for that is to record a few seconds of silence, save that as an MP3 and set that as the default ringtone. Then, select whatever ringtone you actually want to have to the few contacts you actually want to get calls from. Your phone never bothers you when spammers call, but you get pleasantly notified whenever a call from someone you care about comes in.
by therein | 2025-08-20 20:44:25+00:00
> It’s a smart and useful feature which you can turn off if you don’t like it.

If they hadn't gotten rid of the fingerprint sensor, I'd believe in the sincerity of that statement.

> It is not terrible

The fingerprint sensor was at the perfect location, it worked perfectly. FaceID has the downsides I have outlined and therefore in my opinion absolutely terrible.

> Especially on newer phones which support landscape rotation etc.

I don't understand how you could say "newer phones which support landscape rotation" in 2025 with a straight face. Even iPod Touch 2G supported landscape rotation.

The rotation doesn't help anyway, it is technically capable of detecting it is sitting still on my desk but it still does the FaceID dance first before showing me the passcode prompt which I also don't appreciate along with scanning my face every 30 seconds even when unlocked.

If it can scan it so rapidly, why not show me the passcode prompt or design the UX better so that I can already input my passcode before waiting for the device to decide it sees no face in there?

It can do it better but by design it is too eager to just perform the FaceID unlock and then turn itself into a user presence and attention sensor.

I'd easily pay $100 extra for an iPhone that didn't solely rely on FaceID to log me in and instead gave me a fingerprint sensor it had from generations ago.
by mackeye | 2025-08-20 20:44:43+00:00
> how do you convert a paper into working code?

this is something i've found LLMs almost useless at. consider https://arxiv.org/abs/2506.11908 --- the paper explains its proposed methodology pretty well, so i figured this would be a good LLM use case. i tried to get a prototype to run with gemini 2.5 pro, but got nowhere even after a couple of hours, so i wrote it by hand; and i write a fair bit of code with LLMs, but it's primarily questions about best practices or simple errors, and i copy/paste from the web interface, which i guess is no longer in vogue. that being said, would cursor excel here at a one-shot (or even a few hours of back-and-forth), elegant prototype?
by dang | 2025-08-20 20:44:51+00:00
The strongest plausible interpretation isn't "humans are not exceptional". Every species is exceptional by definition, so that's a weak and easily dismissed claim. This critique is not so interesting.

What's meant by "human exceptionalism" is something more like "humans' longstanding habit of regarding ourselves as the apex of a strict hierarchy of species, a worldview which has had profound consequences for ourselves and others". That is a complex thing worth exploring, and what the work in the article is about. A critique from that level would be more interesting. But to do this, one would have to take in a larger working set of information.

Comments that engage with only the title of an article or the tip of its iceberg tend to be rather boring, and also reflexive/indignant. On HN, a good comment is reflective rather than reflexive [1], and engages with specifics rather than just being a generic reaction to a generic claim (like "humans are/aren't exceptional") [2].

One way to "engage with specifics" is to dig beneath the top of the abstraction heap (i.e. the title or top-level claim) until you hit a layer of substance of the relevant work or argument. In this case that's pretty easy to do: there are two paragraphs which, in their first sentences, get more specific:

* when we assess other animals, we use human beings as the baseline * our tests of the abilities of nonhuman animals [...] study them under highly artificial conditions

One can disagree or debate the significance, but a response on this level is likely to be less reflexive and therefore more interesting.

To me the noteworthy thing in this HN thread is how rapid the reflex is to wholly dismiss the article (and the research it's about) and also how shallow that reflex is—how little information is processed before doing the dismissal. Strong emotional conditioning means little information can be tolerated before a reaction needs expressing. This thread is such a clear a case of that, that it points to how deeply what is called "human exceptionalism" lives in us.

Edit: actually, I was describing what I saw in the thread last night. Having looked it over again, there are a least some more substantive subthreads. That's good, and it's also common for those to take longer to appear, as described at [1] and [3].

[1] https://hn.algolia.com/?dateRange=all&page=0&prefix=true&sor...

[2] https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...

[3] https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...
by ModelForge | 2025-08-20 20:44:55+00:00
Could be an artifact of the small size not fully taking advantage of the GPU. For example, for the slightly larger Qwen3 0.6B model the A100 is faster (you can see it when scrolling to the bottom here: https://github.com/rasbt/LLMs-from-scratch/tree/main/ch05/11...)
by zamadatix | 2025-08-20 20:45:10+00:00
Zed had already targeted macOS when 10.15 still had over a year of support left https://github.com/zed-industries/zed/commit/b400449a58507cc... and some variant of x86-64 macOS will still be supported through 2028. Neither of these were adding support for really old things, one is current for many years to come and just there hasn't been a reason to break 10.15 support yet so why bother.

Meanwhile Windows 7 is already over 2 years past the end of extra-extended support at the time this new code was written with Windows 7 support still in mind. Which is nice, but a very different scenario.
by johnnyanmac | 2025-08-20 20:46:39+00:00
1. probably something with AI in it. You got maybe 2-3 years before the bubble pops.

2. branding. cultural awareness can take years or more, and I'm sure coporate knows by now that their brands aren't the best thing to slap onto every scenario. Disney is well learned in this kind of conduct.

3. Because the last thing you want in an aquihire is for all the talent your poaching to jump ship. Some employees may have even worked there previously and used a company to get away from that corporate culture.

So a lot of an aquihire's money tends to go towards golden handcuffs.
by thebruce87m | 2025-08-20 20:46:59+00:00
My aunt and uncle were disembarked from a cruise ship because they were ill (covid) and they were taken to hospital. They phoned my mum to tell her of the situation while still disoriented and said they were in Spain.

The Canary Islands are Spanish, but saying Spain in this situation wasn’t helpful when my mum was trying to book flights. Caused some mild confusion for a while.
by delta_p_delta_x | 2025-08-20 20:47:16+00:00
> but why does a code editor need to render on the GPU like a video game?

It isn't just text editors—nowadays, everything renders on your GPU, even your desktop and terminal (unless you're on a tty). For example, at the bottom of Chromium, Electron, and Avalonia's graphics stack is Skia, which is a cross-platform GPU-accelerated windowing and 2D graphics library.

GPU compositing is what allows transparency, glass effects, shadowing, and it makes actually writing these programs much easier, as everything is the same interface and uses the same rendering pipeline as everything else.

A window in front of another, or a window partially outside the display? No big deal, just set the 3D coordinates, width, and height correctly for each window, and the GPU will do hidden-surface removal and viewing frustum clipping automatically and for free, no need for any sorting. Want a 'preview' of the live contents of each window in a task bar or during Alt-Tab, like on Windows 7? No problem, render each window to a texture and sample it in the taskbar panels' smaller viewports. Want to scale or otherwise squeeze/manipulate the contents of each window during minimise/maximise, like macOS does? Easy, write a shader.

This was a big deal in the early 2000s when GPUs finally had enough raw compute to always run everything, and basically every single OS and compositor switched to GPU rendering roughly in the same timeline—Quartz Extreme on Mac OS X, DWM.exe on Windows, and Linux's variety of compositors, including KWin, Compiz, and more.

There's a reason OSs from that time frame had so many glassy, funky effects—this was primarily to show off just how advanced their GPU-powered compositors were, and this was also a big reason why Windows Vista fell so hard on its face—its compositor was especially hard on the scrawny integrated GPUs of the time, enough that two themes—Aero Basic, and Aero Glass—had to be released for different GPUs.
by JasperBekkers | 2025-08-20 20:47:35+00:00
Thankfully the content is actually provided by us without any sponsorship! We ran into a memory bandwidth problem on one of these devices, wrote some small tests for it and ran it on the other devices as well. Indeed tho, the AMD gpus do seem to have extremely linear cache performance.

Full disclosure: I do run the company behind Evolve.
by xenadu02 | 2025-08-20 20:47:38+00:00
> It's smaller, so it should cost less

That is... not how the physical world works. The laws of physics hate the large and the small. Or perhaps less glibly parameters do not scale equally. Making a phone is more difficult and expensive than making a laptop for the same reason a 30ft tall human would break their own legs attempting to walk.

To put it another way: A thread rolling screw machine can churn out 12mm/0.5" bolts all day long for a penny each. But if you want to make tiny screws for small pocket watches you're going to pay more (relatively) even though that tiny screw contains way less metal than the larger bolt and the operation is similar. A .00001" error in the larger bolt threads doesn't matter. That much error makes the tiny screw completely unusable. Making a thread-forming die with less than .00001" error is very difficult and expensive and the one for smaller screws accumulates error faster relative to allowable error so must be replaced more often. The steel is just as hard in both bolts but the form of the tiny one is proportionally much thinner.

And similarly if you want a 6m/12ft long bolt you are going to pay a lot more than just the proportional cost of the extra metal because finding machines that can even put that much tool pressure on the dies is not easy. It has to be lifted with a crane. It is just more difficult in every way.

Miniaturization is more expensive. Water and dust proofing is more expensive.

For most things there is a sweet range where cost is lowest and utility highest. Prices go up on either end of that middle ground.
by 3036e4 | 2025-08-20 20:48:05+00:00
As a, mostly, happy Android user since the HTC Magic in 2010 or 2009, the one thing I really wish they could fix (but I suspect it would never be possible) is the extremely confusing thing with intents and apps opening as views in other apps. Like when my mail app opens a PDF it looks like I am now in the PDF app and after reading for a while I completely forget that I am actually still in the mail app, and then I go BACK and instead of ending up in my PDF library view as I expected I am suddenly in my mail app. Or when I look at the running apps list there can sometimes look like I have two PDF viewers or two browsers running since some other apps used intents to open views from those apps that now exist in parallel with the real apps.

Somehow that manages to surprise and confuse me almost every day. In desktop operating systems, and, I belive, in iOS, there is no need for such thing? Opening a PDF from a mail application usually just opens the PDF viewer as its own application, or it is embedded in some nice way that does not make the entire mail app suddenly look like a PDF viewer app instead.

Unfortunately they can probably never fix that because app lifecycle and intents are connected to everything and a good fix for this would probably break everything.
by ModelForge | 2025-08-20 20:48:43+00:00
No the compiled version is actually faster.

From that table, the A100 tok/sec (larger is faster) numbers are:

- Eager: 28

- Compiled: 128

And

- KV cache eager: 26

- KV cache compiled: 99

The reason that the KV cache is slower is likely because it's not GPU-optimized code. On CPU the KV cache is faster. To make it faster on GPU, you would pre-allocate the tensors on the device for example instead of `torch.cat`ting them on the fly
by toomuchtodo | 2025-08-20 20:48:57+00:00
Don’t know about internal phototherapy, I think GLP-1s are going to be a component. Excess sugar negatively impacts collagen via glycation.

Unlocking longevity with GLP-1: A key to turn back the clock? - https://www.sciencedirect.com/science/article/abs/pii/S03785... | https://doi.org/10.1016/j.maturitas.2024.108028

Research Advances on the Damage Mechanism of Skin Glycation and Related Inhibitors - https://www.mdpi.com/2072-6643/14/21/4588 | https://doi.org/10.3390/nu14214588
by fodkodrasz | 2025-08-20 20:49:06+00:00
Really? If I remember correctly: My Static website served from S3 + CF + R53 by about 0.67$ / mo, 0.5 being R53 from that, 0.16 being CF, S3 being 0.01 for my page.

BTW: Is GitHub Page still free for custom domains? (I don't know the EULA)
by jimbokun | 2025-08-20 20:50:03+00:00
I think a lot of developers think like you, but most users of phones don't.

I don't think most people care enough to put time into organizing their photos, but would rather the phone or backend AI just find the photo they want by searching for it.

I'm not sure if most users even have a strong conception of "file" or really understand what data is physically on their phone vs "the cloud".

(The symmetry thing though probably does bother a lot of people regardless of their level of technical expertise.)