MurphyA/hacker-news huggingface dataset:
by rasz | 2025-07-25 07:25:03+00:00
Athlons official announcement June 23 1999, official shipping date August 17, 1999. A week after announcement reservations started at Akihabara https://akiba-pc.watch.impress.co.jp/hotline/990703/p_cpu.ht... https://akiba-pc.watch.impress.co.jp/hotline/990703/price.ht...

"AMD Athlon 500-600MHz (bulk) price display. The product is scheduled to arrive in mid-July, and reservations are being accepted. However, there is no specific arrival schedule for compatible motherboards yet."

"the K7 revised "Athlon" has been given a price and reservations have also started. The estimated price is 44,800 yen for 500MHz, 69,800 yen for 550MHz, and 89,800 yen for 600MHz."

Those were Pentium 3 450-550MHz prices.

A week before official AMD shipping date retail Athlons arrive in Japan https://akiba-pc.watch.impress.co.jp/hotline/990813.html

"AMD's latest CPU "Athlon" will be sold in Akihabara without waiting for the official release date on the 17th is started. All products on the market are imported products, and 3 models of 500MHz/550MHz/600MHz are on sale. The sale of compatible motherboards has also started, and it is possible to obtain it alone, including Athlon"

https://akiba-pc.watch.impress.co.jp/hotline/990813/p_cpu.ht...

~$380-800 depending on speed.

https://akiba-pc.watch.impress.co.jp/hotline/990813/newitem....

Picture of one of the Akihabara stalls full of CPUs being sold retail before official AMD launch date :) https://akiba-pc.watch.impress.co.jp/hotline/990813/image/at...

For reference in US 4 days later on August 17 Alienware was merely teasing pictures of Athlon system https://www.shacknews.com/article/1019/wheres-my-athlon According to Anand "OEMs will start advertising Athlon based systems starting August 16, 1999" https://www.anandtech.com/show/355/24
by derdi | 2025-07-25 07:25:14+00:00
> the train that leaves first gets there first

I understand this is what motivates people, and I also understand that, when asked, they would claim that this is in their rational self-interest. As I also wrote elsewhere, I tend to disagree or at least question this assumption in general. Are you really in that much of a hurry? If you have a very hard deadline, wouldn't it have been in your rational self-interest to leave home five minutes earlier? etc.
by theshrike79 | 2025-07-25 07:27:43+00:00
I have a "llm-shared" git submodule I add to all my projects.

In there I have generic advice on project management (use `gh` and Github issues for todo lists) and language-specific guidance in separate files, like which libraries to use etc.

Then I have a common prompt template for different agents that tells them to look there for specific technology choices and create/update their own WHATEVER.md file in the repo.

Gemini-cli is pretty efficient for creating specs and doesn't run out of context. With Context7 it can pull up API specs into the documentation it creates and with Brave API it can search for other stuff.

After it's done, I can just tell Claude to make a step by step plan based on the specs and create Github issues for them with the appropriate labels.

Clear context, and get Claude working on the issues one by one.
by jerpint | 2025-07-25 07:27:58+00:00
I built a library to manage this exact workflow! I actually used the library to build the library

https://github.com/jerpint/context-llemur

It’s MCP/CLI friendly , and wraps git around a context: folder, so you can super easily load context anywhere using: “ctx load” and ask LLMs to update and save context as things move along
by theshrike79 | 2025-07-25 07:29:37+00:00
This is why I have a standing order for all LLMs to run goimports on any file they've edited. It'll fix imports and minor nags without the LLM having to waste context on removing a line there or changing ' to " somewhere.

Even better if you use an LLM with Hook support, just have the hook run formatters on the file after each edit.
by recursivecaveat | 2025-07-25 07:29:45+00:00
Honestly I think Visa/MC appreciate being nudged into this situation. Normalization of them as financial gatekeepers gives them a big favor that they can grant to governments by cutting the tap off to orgs/companies/people whenever. Its a direction that is convenient for them and a lot of the heat for the move gets passed on to some Australian non-profit instead of them. Hard for me to square their behavior unless they are quietly quite receptive.
by Galanwe | 2025-07-25 07:29:46+00:00
> I see the point being made here, and yeah 5%-20% extra for what amounts to insurance against geopolitics isn't too bad

Well that is an insurance only for the US. As a european, I feel safer, or at best neutral, knowing my ships are made in the Taiwan rather than the US, so having them more 5-20% more expensive is not competitive.

With all their antagonizing of allies, and predatory privacy laws, and repeated espionage on allies, the US has disintegrated any trust other parties have to buy things made there.
by toddhodes | 2025-07-25 07:29:57+00:00
This is an important point, but we can do better!

this is why there is a difference between TODO and XXX

XXX is old-school, "popularized in early Unix-related projects like the Berkeley Software Distribution (BSD)", and acted both as TODO and warning.

amazingly, now, we can simply have both!

- TODO is literally "do this before merging, or, make an issue"

- XXX is "gah this is a bug and i can't fix it right now. i am putting the XXX so it stands out from non-bug comments"
by Tade0 | 2025-07-25 07:30:17+00:00
I'm wondering if it would be useful/possible to run the compilation in a service worker that would intercept requests for *.ts and compile them in the worker?

I've seen an alternative approach, where the TS code is sent for compilation to a dedicated server - dismissed that idea as over engineered, but then I learned that the swc WASM package clocks in at over 5MB.

I love the name BTW.
by cadamsdotcom | 2025-07-25 07:30:32+00:00
Brilliant idea.

Source code is frozen in time. Especially as the software world moves faster, software depreciates in value / rots over time. Separately and equally importantly, depending on the use, the same source code can be a fun hobby or be the centerpiece of a giant business.

This model lets open source flourish while reflecting those realities. From what I see, a business has the option of using the software without paying - they of course wouldn’t get maintenance. They could keep people on staff supporting it or just get support this way - and this way is far cheaper.

Let’s see how it plays out! Could become industry standard.
by asteroidburger | 2025-07-25 07:31:13+00:00
This sounds a lot like how Kiro works. Your requirements and design are in a .kiro directory inside the project, allowing you to commit them. The process is structured within Kiro to walk you through generating docs for each phase before beginning to write code. Ultimately, it generates a list of tasks, and you can run them one at a time and review/update between each.
by alexrp | 2025-07-25 07:31:21+00:00
As the guy currently handling Zig's LLVM upgrades, I do not see this as an advantage at all. The more IR layers I have to go through to diagnose miscompilations, the more of a miserable experience it becomes. I don't know that I would have the motivation to continue doing the upgrades if I also had to deal with MLIR.
by altbdoor | 2025-07-25 07:31:48+00:00
I've tried this before, with a service worker[1] that intercepts TS/X-ish requests, and directing them over to sucrase[2] to compile to JS, before being loaded by the browser. Unfortunately sucrase seems to be no longer maintained.

[1]: https://github.com/altbdoor/sucrase-build-iife

[2]: https://github.com/alangpierce/sucrase
by nunez | 2025-07-25 07:32:16+00:00
I have FSD on both of our Teslas and, honestly, it's about fucking time. FSD has always been an aspirational goal, and it's clear that the last mile is only getting longer and more expensive to complete.

FSD should not cost $12k, the package should be account-linked, not vehicle-linked, and owners who paid full price without feeling like they haven't gotten their money's worth should be entitled to a refund of some sort.

This will probably end or significantly curtail Tesla, which will be sad, as the car itself is phenomenal, but its about time they slept in the bed that they made.
by Hiolamaka | 2025-07-25 07:34:00+00:00
Greener Farms CBD Gummies Each piece contains a consistent amount of CBD, allowing users to easily track their intake and adjust as needed. Whether you're looking to ease anxiety, manage chronic pain, or simply improve your overall well-being, these gummies provide a simple and effective solution.

https://www.facebook.com/Official.Greener.Farms.CBD.Gummies/ https://www.facebook.com/GreenerFarmsCBDGummiesTry/ https://www.facebook.com/PlantaCBDGummies.Get/ https://www.facebook.com/TryPlantaCBDGummies/ https://www.facebook.com/CBDGummiesPlanta/ https://www.facebook.com/US.GlobalHealthFarmsCBDGummies/ https://www.facebook.com/EverGreenFarmsCBDGummiesTested/ https://www.facebook.com/EverGreenCBDGummiesTry/ https://www.facebook.com/EverGreen.Farms.CBD.Gummies.Officia... https://www.facebook.com/TryGlobalHealthFarmsCBDGummies/ https://www.facebook.com/Official.Global.Health.Farms.CBD.Gu... https://www.facebook.com/Terra.Pro.CBD.Gummies.Official/ https://www.facebook.com/TryTerraProCBDGummies/ https://www.facebook.com/BlissHarmonyCBDGummies.Get https://www.facebook.com/Vital.Farms.CBD.Gummies.Online/ https://www.facebook.com/VitalFarmsCBDGummiesTry/ https://www.facebook.com/LavazitGermany/ https://www.facebook.com/LavazitDE/ https://www.facebook.com/BloodVitals.UK.Official/
by abrookewood | 2025-07-25 07:34:18+00:00
I think in that case, you would still need RAG - I can't imagine someone is going to build an MCP server to a folder of docs and even if they did, it would still need to index them, extract data etc. BUT if you were feeding your Confluence pages into RAG, then that's probably not worth doing anymore (because there is an MCP server for that).

In short, MCP servers won't make RAG obsolete, but the number of use cases is definitely lower than it was without it.
by somenameforme | 2025-07-25 07:35:26+00:00
In every domain that uses neural networks, there always reaches a point of sharp diminishing returns. You 100x the compute and get a 5% performance boost. And then at some point you 1000x the compute and your performance actually declines due to overfitting.

And I think we can already see this. The gains in LLMs are increasingly marginal. There was a hugeeeeeeee jump going from glorified markov chains to something able to consistently produce viable output, but since then each generation of updates has been less and less recognizable to the point that if somebody had to use an LLM for an hour and guess its 'recency'/version, I suspect the results would be scarcely better than random. That's not to say that newer systems are not improving - they obviously are, but it's harder and harder to recognize those changes without having its immediate predecessor to compare against.
by svara | 2025-07-25 07:35:53+00:00
Down syndrome presents in different ways.

I wanted to respond to multiple comments with the touching speech of Frank Stephen (a man affected by Down syndrome) before the US Congress in 2017, so I'm posting it to the top level instead.

It's a complex issue but I think listening to Stephen will add a valuable perspective.

https://m.youtube.com/watch?v=vtS91Jd5mac&pp=0gcJCfwAo7VqN5t...
by mac-monet | 2025-07-25 07:35:53+00:00
Since this is adjacent to crypto, I came in here expecting some kind of hateful things being said about it, but seems like a fairly productive and honest discussion, something that is usually lost as soon as the c-word is mentioned.

Despite all of the issues that are within the crypto world, I do think stablecoins are a fantastic use-case that most of us should be able to get behind to break this duopoly. With some oversight/proofs of solvency for the issuers, I hope they can become the dominant payment method. I can say from experience, the fact that I can easily pay friends and also receive yield on my holdings is such a nice experience, especially considering the inflationary environment we're in currently.
by dengolius | 2025-07-25 07:35:54+00:00
This article discusses why TiDB, a distributed SQL database, migrated its observability platform from Prometheus to VictoriaMetrics.

The Problem with Prometheus At scale, Prometheus started showing limitations, especially for large enterprise customers like Pinterest.The main issues were: - High resource consumption: Prometheus used a lot of CPU and memory, leading to frequent out-of-memory (OOM) crashes. - Long recovery times: After a crash, Prometheus needed a long time to recover, sometimes failing altogether. - Limited query performance: Large queries would often fail or be very slow.

The Solution: VictoriaMetrics

TiDB switched to VictoriaMetrics and saw significant improvements: - Better resource utilization: CPU and memory usage dropped significantly, eliminating OOM crashes. - Improved query performance: Large queries that previously failed in Prometheus now run efficiently in VictoriaMetrics. - Lower costs: Reduced resource consumption and better storage efficiency led to lower operational costs.
by pjmlp | 2025-07-25 07:36:13+00:00
Yet is being embraced by everyone since its introduction in 2019, with its own organization and conference talks.

So maybe all those universities, companies and the LLVM project know kind of what they are doing.

- https://mlir.llvm.org/

- https://llvm.github.io/clangir/

- https://mlir.llvm.org/talks/
by dm3 | 2025-07-25 07:36:44+00:00
Looks like we're in a similar situation. What is your current go-to for setting up lean incremental data pipelines?

For me the core of the solution - parquet in object store at rest and arrow for IPC - haven't changed in years, but I'm tired of re-building the whole metadata layer and job dependency graphs at every new place. Of course the building blocks get smarter with time (SlateDB, DuckDB, etc.) but it's all so tiresome.
by saghm | 2025-07-25 07:36:51+00:00
It's not clear to me what you mean by default with regards to that issue. As far as I can tell, there's not really any indication that this is undefined behavior. Yes, there seems to be to a bug of some sort in the code being generated, but it seems like a stretch to me to imply that any bug that generates incorrect code is necessarily a risk of UB. Maybe I'm missing some assumption being made about what the pointers not being equal implies, but given that you can't actually dereference `*const T` in safe Rust, I don't really see where you're able to draw the conclusion that having two of them incorrectly not compare as equal could lead to unsafety.
by jillesvangurp | 2025-07-25 07:37:31+00:00
As Apple and MS have shown, from a software point of view the difference is not that important. They both have ARM and x86 products. In Apple's case, the same software actually supports both. They literally just stuff two binaries in their executables. Their OS runs on both X86 and ARM (for now). That's how they seamlessly transitioned to their own chips over the course of the last five years. Users barely notice the difference.

What they do notice is vastly improved performance, longer battery life, the fact that the CPU fan doesn't come on if you just move your mouse, etc. That's because there are some big differences at the hardware level that Intel has so far not addressed. Which is why ARM for Windows laptops is a thing multiple manufacturers are trying to get off the ground.

I have an M4 Max laptop. I don't think Intel currently ships something that comes even close to this thing. I don't think anybody does. And clearly they all want to. AMD comes decently close. Nvidia is of course king of GPUs and perpetually rumored to get into the (ARM based) system on a chip market. But their attempt to buy ARM failed and it seems they are more focused on AI. Either way, they haven't really launched much of interest yet. AMD actually cornered the market for game consoles. Steam Deck, XBox, and Playstation have in common that they get their chips from AMD (not Intel or Nvidia). But most Windows laptops continue to kind of suck in terms of energy usage and performance per watt.
by brabel | 2025-07-25 07:37:57+00:00
Rust is objectively harder to write than Go (or any other GC-language) because it exposes more concerns for the programmer to take care of. With Rust, you must always ensure your program complies with the borrow checker's rules (which is what makes Rust memory-safe) which includes having to add lifetime annotations to your variables in many cases. Go just doesn't have any of that. You could argue Rust still has an advantage in that it prevents bugs that in Go you're free to write, but then what you're claiming is that this compensates for the extra work you have to do upfront in Rust. That's a difficult position to defend, though, because an experienced Go developer probably has internalized how to avoid those bugs and the cost of preventing them can be nearly negligible. I do agree that they will still make mistakes, and those can have a cost, but they may also be quite rare, or may not matter much most of the time depending on your domain. I think that's why most people seem to agree Rust is probably only advantageous where the cost of data races in production is higher than the cognitive cost (which translates into increased effort) on the programmer.
by lrvick | 2025-07-25 07:38:02+00:00
GrapheneOS (like all modern AOSP based ROMS) can literally not function with just the open source code. It requires hundreds of binary blobs from the vendor partition of a stock Android ROM, many of which have root access and have not been audited by anyone, including Google, who often lacks source code for them.

Beyond that, the GraheneOS team still controls a single signing keychain for all phones in the wild, which we have to assume is still controlled by Daniel Micay (strcat) as it has not rotated as far as I can tell since he mostly stepped away from public view.

He is without question a brilliant security engineer, but we can't ignore his very public Terry-Davis-esqe history of mental illness. Making -anyone- a single point of failure for a ROM frequently recommended for journalists and dissidents is a bad plan, and especially not someone very prone to believing wild conspiracy theories.

I can't recommend GrapheneOS for any high risk use cases until:

1. they are able to find a device they can run 100% open source code on with no binary blobs

2. The ROM can be full source bootstrapped to mitigate trusting trust attacks.

3. The ROM builds 100% deterministically and is reproduced and signed by multiple team members publicly

4. Threshold signing or a quorum managed enclave issues the final signature only if multiple team members give it signed approvals of a hash to sign.

Until at least those points are covered, the centralized trust model of GrapheneOS is a liability and the central keyholder is at high risk of being targeted for manipulation or coercion.

Honestly there is no good solution to these problems right now, and as a security and privacy researcher my best advice today to potentially targeted individuals is don't carry a phone at all, or if you must carry one, keep it in airplane mode whenever possible and do not do anything sensitive on it. Consider QubesOS or AirgapOS for such things.

If you are fine with centralized control of a phone, and fine with binary blobs controlled by random corpos having God access to your device, but would prefer to eliminate as much proprietary corpotech bullshit as possible, then I would suggest considering CalyxOS which is at least run by a former LineageOS maintainer with a great reputation.
by simianparrot | 2025-07-25 07:38:12+00:00
Let's not forget that the US is only _one_ member of Five Eyes: https://en.wikipedia.org/wiki/Five_Eyes

Credit where credit is due: Australia, UK, New Zealand and Canada are all doing their major parts in espionage on each other and everyone else as a service as part of Five Eyes.

As a European myself, I am pretty miffed that my fellow Europeans keep acting like we're not leading the charge when it comes to spying on each other.
by godelski | 2025-07-25 07:39:14+00:00
I'm not a big fan of crypto but I've always wondered why the US wouldn't want to create a highly secure private coin that's pegged to the dollar. I mean you put a very small transaction fee on it (can be far less than Visa's 2%) and you're suddenly generating revenue from tons of global transactions, benefiting from the status of the dollar being the global currency. You even get to "tax" illegal transactions, and as a consumption "tax". It would only work if it was highly private (effectively like cash) as no one else wants to be handing all that data over but it still sounds like it would be a big win to many parties (well not the authoritarians? Maybe?). Everyone will be "banked", you get digital payments everywhere, and you even probably reinforce the reliance on the US dollar. Is the demand for control so much greater than the demand for money combined with providing a public good? I know there's still challenges to resolve but a guy can dream, right?
by bawolff | 2025-07-25 07:39:22+00:00
> Imagine trying to explain to a relative the lesson of this post: always be suspicious, even if the email is from a trusted domain and dkim/dmarc/spf all pass

Imagine explaining to a relative what dkim/dmarc/spf is!

These are all behind the scenes technology that users should not be aware of.

Honestly this attack is not as scary as it sounds. The article is being misleading to sell their product.

> It does seem surprising the To: header isn’t one of the headers that is covered by the dkim signature.

I dont think that would really matter. How often do you read the To header. Keep in mind that in email the To header does not have to include the intended recipient.
by ddorian43 | 2025-07-25 07:41:42+00:00
No, there aren't. And no, you haven't ready any reputable studies where people did clean keto/carnivore.

All your studies are people just talking about their diet, eating meat & stuff. And that "meat & stuff" never works on treating any diseases either.

Feel free to link anything from "everything I've ever read about high red meat consumption" and we'll see if it's true keto/carnivore/ketovore.
by time4tea | 2025-07-25 07:42:11+00:00
So much of this is just normal stuff anyway, right? Signing CI output, tracking dependencies, using bundled resources..

Bit-for-bit reproducible builds are definitely doable, but mean including build dates is tricky, and care needs to be taken with archival file ordering.

Is this such a big departure from the norm? Curious what constitutes normal!
by torium | 2025-07-25 07:42:24+00:00
Does anybody else here see as problematic that this OS supports mostly Pixel, a Google phone?

Over and again people on HN make the following argument: "Google is a company that makes most of its revenue from ads and surveillance. Therefore, you should always assume that Google is spying on you". But somehow when it comes to Pixel people give it a pass?

Prediction: If Pixel isn't already hardwired to phone home and report on your activities, it will slowly become so over time, as Google realizes its interest. You know, as it happened with Android, Chrome, and everything else that Google touches.