MurphyA/hacker-news huggingface dataset:
by caidehen | 2025-11-28 10:40:40+00:00
take both this article and my opinion with a large chunk of salt.

Industries like car manufacturing, textile, farming and so on are just too old, everybody can join without much difficulty, not fancy ones, just usable.

The competition is too intensive they just don't make much money and they are not the future. Investing too much in these industries are meaningless. Just use tariff walls to keep some local factories/farms open for strategic reasons(in case of war) and employment.

---

Climate change and carbon emission is another story. For most people money for next bill is much more important.
by throwawayqqq11 | 2025-11-28 10:41:26+00:00
To me, the worming aspect and taking developers data as hostages against infrastructure take down is most concerning.

Previously, you had isolated places to clean up a compromise and you were good to go again. This attack approaches the semi-distributed nature and attacks the ecosystem as a whole and i am affraid this approch will get more sophisticated in the future. It reminds me a little of malicious transactions written into a distributed ledger.
by Rochus | 2025-11-28 10:41:48+00:00
Cool project, congrats. I like the idea with libkernel which makes debugging easier before going to "hardware". It's like the advantages of a microkernel achievable in a monolithic kernel, without the huge size of LKL, UML or rump kernels. Isn't Rust async/awat depending on runtime and OS features? Using it in the kernel sounds like an complex bootstrap challenge.
by 1718627440 | 2025-11-28 10:42:23+00:00
C (actually POSIX) has a hashmap implementation: https://man7.org/linux/man-pages/man3/hsearch.3.html

What it doesn't have is a hashmap type, but in C types are cheap and are created on an ad-hoc basis. As long as it corresponds to the correct interface, you can declare the type anyway you like.
by Cthulhu_ | 2025-11-28 10:42:52+00:00
"The original Java platform" had no package management though, that came with Maven and later Gradle, that have similar vectors for supply chain attacks (that is, nobody reviews anything before it's made available on package repositories).

And (to put on my Go defender hat), the Go ecosystem doesn't like having many dependencies, in part because of supply chain attack vectors and the fact that Node's ecosystem went a bit overboard with libraries.
by TheAceOfHearts | 2025-11-28 10:43:21+00:00
I think one of the key issues is that most of these discussions are happening at too high of an abstraction level. Could you give some specific examples of AI regulations that you think would be good? If we actually start elevating and refining key talking points that define the direction in which we want things to go, they will actually have a chance to spread.

Speaking of IP, I'd like to see some major copyright reform. Maybe bring down the duration to the original 14 years, and expand fair use. When copyright lasts so long, one of the key components for cultural evolution and iteration is severely hampered and slowed down. The rate at which culture evolves is going to continue accelerating, and we need our laws to catch up and adapt.
by iand675 | 2025-11-28 10:43:49+00:00
I've been trying `beads` out for some projects, in tandem with https://github.com/github/spec-kit with pretty good results.

I set up spec-kit first, then updated its templates to tell it to use beads to track features and all that instead of writing markdown files. If nothing else, this is a quality-of-life improvement for me, because recent LLMs seem to have an intense penchant to try to write one or more markdown files per large task. Ending up with loads of markdown poop feels like the new `.DS_Store`, but harder to `.gitignore` because they'll name files whatever floats their boat.
by Kon5ole | 2025-11-28 10:44:13+00:00
>The option up here really truly is "do we use fossil fuels, or do we use nuclear". Renewables do not help.

Hey now - renewables gave us electricity up here long before Einstein started thinking about atoms!

We are very few people here, 250MWh helps a lot, but if we have to chip in to build a nuclear plant we'll be broke before the project planning is done. ;-)
by pbmonster | 2025-11-28 10:45:22+00:00
> And pumped storage is significantly cheaper for seasonal storage than any proposed alternatives.

This is incorrect. There is currently not a single pumped hydro station that is suitable for seasonal storage. They're all designed to drain their upper reservoir in 4-16 hours.

It's the only thing that's half economical. Do the math: Even a modest power plant - 1 GW output - that can run for 1000 hours means you need a 1 TWh (even typing it feels ridiculous) storage reservoir. If you only have 100m of head, that's 3 cubic kilometers of water. That would mean building an artificial lake that immediately would be Norway's 6th largest body of fresh water, and draining it completely every winter.

And effectively, you'd have to build it twice - you also need a lower reservoir. Because there's nowhere to get 3 cubic kilometers of fresh water to fill it otherwise, and you really don't want to do pumped hydro with seawater.
by deviation | 2025-11-28 10:45:36+00:00
Likely a combination of practicality, and the importance of airflow throughout the sand in order to heat it and pull from it effectively.

Also, water's specific heat capacity is 4.186 J/g°C, while air's is approximately 1.005 J/g°C. It would take much more energy to heat up water than it would to heat up air.

Also, water boils at 100 degrees, and they store it in the sand at 600 degrees.
by PaulRobinson | 2025-11-28 10:45:53+00:00
Being frustrated with something at work and having somebody to rant about it with is one of the pillars of any friendship. Your friends can do the work of listening, empathising, reassuring and then helping you get past it and enjoying the beer, game or barbecue you're at. That's cool, I agree.

Having deep feelings of inadequacy and bringing that to the friendship at every opportunity is asking that friend to help you with those feelings, they probably aren't equipped to do that in all sorts of ways.

As with most things, it's a spectrum, not binary. Some friends would love to help you overcome childhood trauma, but most will not. Your partner may be able to help you deal with the way that family member behaves, but quite often, that's your thing, not theirs, deal with it. A work colleague might be able to support you when a co-worker is being a jerk, but might not have the skill or ability to help you manage your feelings or deal with that behaviour.

A therapist is trained to help you with those things your friends, family and colleagues can't. More specifically, they are trained to help you figure out what you are going to do about it.

Sometimes, when we talk to people about problems, we're "giving them the problem", as in, we want them to tell us what to do about it, or to actually do something about it. They often can't or won't do that - it's your thing. Therapists won't take it either, but they'll help you manage it as your thing.

A friend who is just there to listen, that's different, if the ask is just to listen and be somebody to talk to, sure, most friends have that ability and skill, and are happy to do so. But there's a lot of stuff people go through where that isn't enough, and asking those same people to do more is probably not going to work.
Show HN: Agent/LLM observability for tracing, cost, evals, and debugging
by zlatkov | 2025-11-28 10:46:03+00:00
Hi HN - I’m Alex, currently Head of Agent Development Tools at Progress. Before this, I was a Co-founder/CEO of a session replay startup called SessionStack, which was acquired in August this year.

Since then, I’ve been pretty deep in the LLM/agent dev tools, and observability has been my main thing.

I ran a small poll on LinkedIn recently about where teams are with observability for LLM-powered apps/agents. Results:

• 20% instrument LLM observability from day 1 • 30% plan to implement later • 20% are building an in-house solution • 30% are still learning about this space

That 20% building in-house was the most interesting to me, so I followed up with a mix of early-stage, YC founders and more mature orgs. The drivers I kept hearing:

1) Local / self-hosted models Some teams assume there aren’t viable observability options for local/hybrid LLM stacks, so DIY feels like the default. In practice, there are ways to do this, but they’re easy to miss right now.

2) Cost uncertainty Token usage is hard to estimate early on, so pricing feels unpredictable. A minimal in-house layer looks safer than surprise bills.

3) Control + speed Bootstrapping basic tracing/logging is straightforward and gives full ownership while teams iterate quickly on the core product.

This reminds me a lot of early APM / product analytics. Many teams started with “we’ll just implement our own logging.” Totally reasonable at the beginning — but once usage and complexity scaled, that logging quietly turned into:

• an internal platform to maintain • a backlog of features to build • a growing surface area of edge cases to debug

…often becoming a real distraction from the core business.

Our bet is LLM/agent observability follows the same path: teams start with DIY logging, then realize it’s becoming a side-product, and eventually most adopt a standard platform early. We’re also seeing APM/analytics vendors expand into LLM flows, which reinforces that direction.

What we’re building My team and I are working on LLM/agent observability focused on usage, cost/pricing, evaluations, and debugging. Most teams we talk to still don’t have anything in place, even when LLMs are core to the product, so we’re trying to make the “day 1” setup practical.

We're part of a larger org, but this team is being run like a startup within it: small group, fast cycles, heavy on user conversations, and shipping quickly based on real usage. That setup is why we’re doing early access and iterating closely with teams.

Early preview / notes here: https://aback-handbell-1cd.notion.site/Progress-Observabilit...

We’re planning to support self-hosted options as well.

If this is relevant to what you’re building and you want to help us shape the LLM Observability you need, we have a free Early Access Program here: https://www.telerik.com/agent-observability-early-access
by oliwary | 2025-11-28 10:46:12+00:00
I can mirror everyone singing praise to pocketbase here. Once you grasp the concepts (which map pretty closely to SQL concepts, with rules for row-based security), it is by far the easiest way IMO to create a maintainable, robust backend with direct auth integrations and a pleasant interface.

I have around 5 instances of pocketbase running on a 10 USD/month Hetzner server, serving thousands of users a day without breaking a sweat.
by scotty79 | 2025-11-28 10:46:18+00:00
Because, unlike at the stock market, the government provides no assurances regarding any part of the crypto trade that is being made. When things go south, fraud happens in crypto, government is pretty much zero help in most countries of the world at most times.

I imagine if it turned out you never possessed any AMD or Nvidia stocks and all of that was just fake number on a fake piece of paper there would be serious government involvement pretty much everywhere.

Also on more practical note, a single sale of crypto can really be a 50 sales to 50 people at various prices. Calculating gain is virutally unworkable. Especially between crypto pairs where the value of one or the other isn't really known.

When you sell NVidia stock and buy AMD it's a sale and a purchase. But if somebody gave you some AMD stock for your NVIDIA stock, there's no sale or purchase and the value of each is only a guess.

That's why reasonable countries decided it's way better to tax stuff on exit to fiat, via conversion or purchase. And it works just fine. When it's crypto it remains Miki Mouse money, but when it exits to fiat and there's more of it than was put in, there's real and taxable gain.
by _joel | 2025-11-28 10:46:25+00:00
I use gh cli to make and track issues on the repo's issue tracker, create and reference the issue in the PR. I use Claude normally, so have Gemini and Codex that sit as automated reviewers (github apps), then get Claude to review the comments. Rinse and repeat. Works quite well and catches some major issues. Reading the PR's yourself (at least skimming them for sanity) is still vital.
by veunes | 2025-11-28 10:46:33+00:00
The problem is that "hardware-agnostic PyTorch" is a myth, much like Java's "write once, run anywhere". At the high level (API), the code looks the same, but as soon as you start optimizing for performance, you inevitably drop down to CUDA. As long as researchers are writing their new algorithms in CUDA because it's the de facto language of science, Google will forever be playing catch-up, having to port these algorithms to XLA. An ecosystem is, after all, people and their habits, not just libraries.
by xzjis | 2025-11-28 10:47:24+00:00
I commend Collabora's tremendous work on Bluetooth LE audio on Linux and their work in general, but I can't help being frustrated that it's volunteer contributors handling the implementation, while the Bluetooth Special Interest Group makes a ton of profit by licensing Bluetooth yet contributes nothing to implementing the standard on Linux. It's really typical of the "open source" spirit: volunteers are exploited, and the fruits of their labor are harvested as profit.
by bewo001 | 2025-11-28 10:47:33+00:00
It's much simpler. In the EU, truckers have to do mandatory 45 min breaks after 4 1/2 hours of driving. With the latest truck generation, this is enough time to recharge to get through the rest of the shift. 400 kW charging is sufficient in this scenario. No wasteful expensive H2 or fancy battery swapping technology required.
by Cthulhu_ | 2025-11-28 10:47:38+00:00
To add a few:

* NPM has a culture of "many small dependencies", so there's a very long tail of small projects that are mostly below the radar that wouldn't stand out initially if they get a patch update. People don't look critically into updated versions because there's so many of them.

* Developers have developed a culture of staying up-to-date as much as possible, so any patch release is applied as soon as possible, often automated. This is mainly sold as a security feature, so that a vulnerability gets patched and released before disclosure is done. But it was (is?) also a thing where if you wait too long to update, updating takes more time and effort because things keep breaking.
by sph | 2025-11-28 10:47:39+00:00
I do the same. Fever is a feature, unless the infection is so pervasive the fever itself becomes a health hazard (at which point you need to see a doctor ASAP, not lower your fever)

Taking an antipyretic for a regular flu completely defeats the purpose. Let your immune system do its thing, it is pretty good at it.

https://en.wikipedia.org/wiki/Fever#Management
by faidit | 2025-11-28 10:48:21+00:00
Yes, these decisions are being made by flesh-and-blood humans at the top of a social pyramid. Nick Land's deranged (and often racist) word-salad sci-fi fantasies tend to obfuscate that. If robots turn on their creators and wipe out humanity then whatever remains wouldn't be a class society or a market economy of humans any more, hence no longer the social system known as capitalism by any common definition.
by quitit | 2025-11-28 10:49:54+00:00
I never said they didn't. They did, they announced they would, and it's now shipped.

This entire thread is about whether or not they were forced to do so by the EU.

As another dot point: We also don't have Margrethe Vestager or Thierry Breton (or other EU figures) doing a victory lap on social media as they usually do.
by Cthulhu_ | 2025-11-28 10:50:09+00:00
Yes, exactly; I followed a Github course at one point and it was Strongly Recommended that you enable Dependabot for your project which will keep your dependencies up to date. It's basically either already enabled or a one-click setup action at this point. The norm that Github pushes is that you should trust them to keep your stuff updated and secure.
by jrflowers | 2025-11-28 10:50:47+00:00
>We are just it's temporary vehicles.

> “This is because what appears to humanity as the history of capitalism is an invasion from the future by an artificial intelligent space that must assemble itself entirely from its enemy's resources.”

I see your “roko’s basilisk is real” and counter with “slenderman locked it in the backrooms and it got sucked up by goatse” in this creepypasta-is-real conversation
by fifilura | 2025-11-28 10:50:48+00:00
If you pump the water back into the existing reserviors you will have less flooding?

I suggested a pump-water extension to existing hydro power reservoirs.

Like your EV recharges when you release the pedal.

Right shouldn't talk about EVs with a Finn, that analogy will not fly. Ok, like if you plan carefully where you throw up your koskenkorva you can re-use it.
by scotty79 | 2025-11-28 10:51:25+00:00
A single sale of crypto can really be 50 sales to 50 people at various prices. Calculating gain is virtually unworkable. Especially between crypto pairs where the value of one or the other isn't really known and changes every second and depends on particular exchange out of may you could be trading on.

When you sell NVidia stock and buy AMD it's a sale and a purchase. But if somebody gave you some AMD stock for your NVIDIA stock, there's no sale or purchase and the value of each is only a guess.

That's why reasonable countries decided it's way better to tax stuff on exit to fiat, via conversion or purchase of something other than crypto. And it works just fine. When it's crypto it remains Miki Mouse money, but when it exits to fiat and there's more of it than was put in, there's real and taxable gain.

Taxing crypto on every trade would be like taxing forex on every trade.
by SideburnsOfDoom | 2025-11-28 10:51:54+00:00
> The propaganda machine in the US has tricked a huge number of Americans into sabotaging their own industrial future, merely to give fossil fuel infrastructure stocks a few more years of slightly higher profits.

It's instructive to compare and contrast the countries, and I think the driving forces are actually quite simple.

Both countries desire energy independence and thriving domestic industry. Who doesn't?

But while the USA is a net fossil fuel exporter, China is a net importer. While the USA has a long-established automobile industry and shown willingness to bail it out more than once, China is a relative newcomer to this industry.

China is for better or worse prepared to set industrial strategy more rigorously and over longer time periods than others.

A while back China took a bet on non-fossil fuel technologies as a source of both energy independence and a way to get early into a new industry. This is now paying off hugely. It's not purely a green ideological choice, they still use coal heavily. It was strategic - to reduce dependence on imported oil, and "leapfrog" into being a major player in an emerging industry, rather than trying to catch up with ICE engines.

Meanwhile the USA continues to shore up the fossil-fuel chain from extraction to consumption in ICE automobiles. I find this short-sighted and unwise in many ways. And the negative consequences are likely coming soon. but it is not a very surprising choice given where they are and how they make such decisions.
by 1718627440 | 2025-11-28 10:52:09+00:00
char * left_pad (const char * string, unsigned int pad) { char tmp[strlen (string)+pad+1]; memset (tmp, ' ', pad); strcpy (tmp+pad, string); return strdup (tmp); }

Doesn't sound too hard in my opinion. This only works for strings, that fit on the stack, so if you want to make it robust, you should check for the string size. It (like everything in C) can of course fail. Also it is a quite naive implementation, since it calculates the string size three times.
by kaoD | 2025-11-28 10:52:14+00:00
Rust's async-await is executor-agnostic and runs entirely in userspace. It is just syntax-sugar for Futures as state machines, where "await points" are your states.

An executor (I think this is what you meant by runtime) is nothing special and doesn't need to be tied to OS features at all. You can poll and run futures in a single thread. It's just something that holds and runs futures to completion.

Not very different from an OS scheduler, except it is cooperative instead of preemptive. It's a drop in the ocean of kernel complexities.
by disgruntledphd2 | 2025-11-28 10:53:12+00:00
> Elon Musk explicitly said in his latest Joe Rogan appearance that he advocates for the smallest government possible - just army, police, legal. He did NOT mention social care, health care.

This would be a 19th century government, just the "regalian" functions. It's not really plausible in a world where most of the population who benefit from the health/social care/education functions can vote.
by vee-kay | 2025-11-28 10:54:09+00:00
> In the USA you get ops real fast and doctors can be seen same day.

IF the patient has Medical Insurance.

Only in the USA, medical insurance seems to be tied to employment. Non-employment driven medicare is unaffordable except for the filthy rich.

If someone is unemployed or poor, they won't be able to afford or get healthcare (not even for a toothache!) in the USA.

EU nations are struggling with state-sponsored Medicare because those are old systems that weren't improved with growing populations and the needs of modern times, and there are concerted efforts by Big Pharma to cripple and dismantle such free or affordable healthcare. NHS is under attack by Big Pharma is you read the news closely.

EU nations also made tne mistake of intaking thousands of "refugees" many of whom are still jobless and a constant drain on the nation's fragile Medicare system and social service subsidies.

Contrast this to countries like India which has lots of expert doctors and excellent hospitals, and free clinics and free healthcare for the poor. India also has state-sponsored pharmacies selling generics medicines that are extremely affordable substitutes for Big-Pharma-branded medicines.

e.g., A metal stent for a heart surgery in India costs a pittance compared to rest of the world. A dental root canal treatment costs around 5000 rupees (around $55). Foreigners visit India to get cheap (but high quality) Medicare (especially surgeries). One diabetic American I personally know gets his Insulin from India, because it is cheaper despite the shipping cost involved. There's a growing industry for "medical tourism" in India, as catered packages, wherein a foreigner needing surgery arrives with family to stay at a nice hotel, then gets timely appointment and surgery at a reputed hospital by skilled doctors, and then patient and family can recuperate at a nice holiday resort and partake in some local sightseeing as guided tours as part of the whole package.

I am not trying to belittle USA here, but even the staunchest American patriot will agree their healthcare system is under the crippling grip of Big Pharma and bad policies, and is anti-poor by design, and desperately needs an overhaul to become at par with the best healthcare systems in other developed nations. A closer look at America's neighbor Canada's healthcare system will be an eye opener on how to do healthcare better.