MurphyA/hacker-news huggingface dataset:
by embedding-shape | 2025-11-02 14:52:36+00:00
> the fact that I'm being confidently lied to by a damn computer on a regular basis

Many of us who grew up being young and naive on the internet in the 90s/early 00s, kind of learnt not to trust what strangers tell us on the internet. I'm pretty my first "Press ALT+F4 to enter noclip" from a multiplayer lobby set me up to be able to deal with LLMs effectively, because it's the same as if someone on HN writes about something like it's "The Truth".
by PaulKeeble | 2025-11-02 14:53:02+00:00
The fact they have Drax energy at 88% tells me they are counting the giant coal factory converted to burn the worlds forest as renewable, it definitely is not just because its biomass. They also have EDF energy, the nuclear power producer, very low tells us they are counting Nuclear as a none renewable. They aren't looking at temporal moves of energy either, which is a big part of Octopus energies customers who are solar and battery owners and do a lot of energy shifting for the grid. These three components mean the wrong companies are at the top and bottom. This index is useless as it stands its not about who is good for the environment and not.

The fundamental idea we need, but the implementation here is just terrible they aren't promoting the right things and it makes me wonder who is really behind this given the bad producers who have got themselves to near the top.
by Workaccount2 | 2025-11-02 14:53:06+00:00
The AI start-up field is going to be eviscerated. I too have the irresistible urge to bolt a SOTA LLM back end on a custom harness and charge $20/mo, but the total lack of a moat and ease of replication kills any motivation.

You have to either have some big cajones or be totally lost to think it's a good idea to create a startup that is just a simple cheap veil on someone else's extremely advanced and expensive product
Ask HN: Seriously, which AI coding thing is best?
by temperceve | 2025-11-02 14:53:15+00:00
It's so confusing. There's so many options and I never know which one is actually better/best. For a while it was one of the Claudes, then Codex came out and I feel like people starting saying nope nope, it's now that one. Don't even get me started on the different ways to actually wield them (like in Cursor directly, as a plugin, or via terminal).

Simply put, I want to know, today, which should I be using?
by embedding-shape | 2025-11-02 14:54:09+00:00
You need to try different models/tooling if that's the case, 80% sounds very high and I understand if you feel like it's useless then. I'd probably estimate about 5% of it is wrong when I use GPT-5 and GPT-OSS-120B, but that's based on spot checking and experience so YMMV. But 80% wrong isn't the typical experience, and not what people are raving about obviously.
by runarberg | 2025-11-02 14:55:32+00:00
I am not sure that is how carbon induced greenhouse effect works. The warming has pretty immediate effects and is pretty correlated with the amount of CO2 in the atmosphere. The only warming beyond that (as I understand it) is from positive feedback loops via these tipping points. All else being equal (and without tipping points) if we stopped emitting carbon today, the rise in temperature would also stop relatively quickly. And if we did find a way (by some miracle) to remove carbon from the atmosphere it would start to cool again relatively quickly.
by simonask | 2025-11-02 14:55:41+00:00
So I don’t want to come off as dismissive of the effort - it’s certainly impressive!

The reason I’m not super excited is based on the widely publicized findings from Google and Microsoft (IIRC) about memory safety issues in their code: The vast majority is in new code.

As such, the returns on running the entire userspace with Fil-C may be quite diminished from the get-go. Those who need to guard against UB bugs in seriously battle-hardened C software in production are definitely a small niche.

But that doesn’t mean it isn’t also very useful as a tool during development.
by hedora | 2025-11-02 14:55:42+00:00
Choice of things like desktop environments matters a lot. I’m using xfce or lxde or something (I can’t tell without checking top), and responsiveness for most stuff is identical between 2010 intel and a ryzen 9.

The big exceptions are things like “apt get upgrade”, but both boxes bottleneck on starlink for that. Modern games and compilation are the other obvious things.
by AndrewKemendo | 2025-11-02 14:55:55+00:00
There is no human superoganism, and the reason we’re doomed as a temporary species is precisely that humans cannot act eusocially as a superorganism.

By your definition the Moscow Metallica show, Jan 6th riots, etc… were superorganisms and that’s not even barely applicable

Humans expressing group behaviors at some trivial number for a trivial period (<1M people for <2 days is the largest sustained group activity I’m aware of) is the equivalent of a locust swarm not even close to a superorganism
by Esophagus4 | 2025-11-02 14:56:02+00:00
A few months with the wrong hire is detrimental to the team.

Your stars will get annoyed that you have someone not pulling their weight, your team will have to clean up the mess of bugs and incomplete stories, and the mentors will spend more of their time supporting an engineer that will not come up to productivity no matter how hard they try.

If it’s really a bad hire, you can’t be afraid to move quickly. If it’s not going to work out, I’d rather it not work out in a month than not work out in six months.

A mentor of mine once said, “You will never regret firing somebody, but you will regret not firing somebody.”

Part of being a manager means having a bias for action and being able to back your decisions once you’ve made them.

Admittedly, you’re not just shooting from the hip and firing at random. But by the time you get to the point where you have to thinking about getting rid of an engineer, it’s probably past the point of no return and you need to move.
by rawgabbit | 2025-11-02 14:56:24+00:00
Both "trumprx.gov" and “Trumpcard.gov” said they were created by the National Design Studio which points to https://americabydesign.gov.

Cringeworthy Quote:

The same way a hotelier anticipates the needs of their guests. This is the hospitality design for our nation. This is President Trump going bigger than President Nixon.
by reitzensteinm | 2025-11-02 14:56:26+00:00
I'm a little nervous about the correctness of the memory orderings in this project, e.g.

Two acquires back to back are unnecessary here. In general, fetch_sub and fetch_add should give enough guarantees for this file in Relaxed. https://github.com/frostyplanet/crossfire-rs/blob/master/src...

Congest is never written to with release, so the Acquire is never used to form a release chain: https://github.com/frostyplanet/crossfire-rs/blob/dd4a646ca9...

The queue appears to close the channel twice (once per rx/tx), which is discordant with the apparent care taken with the fencing. https://github.com/frostyplanet/crossfire-rs/blob/dd4a646ca9...

The author also suggests an incorrect optimization to Tokio here which suggests a lack of understanding of what the specific guarantees given are: https://github.com/tokio-rs/tokio/pull/7622

The tests do not appear to simulate the queue in Loom, which would be a very, very good idea.

This stuff is hard. I almost certainly made a mistake in what I've written above (edit: I did!). In practice, the queue is probably fine to use, but I wouldn't be shocked if there's a heisenbug lurking in this codebase that manifests something like: it all works fine now, but in the next LLVM version an optimization pass is added which breaks it on ARM in release mode, and after that the queue yields duplicate values in a busy loop every few million reads which is only triggered on Graviton processors.

Or something. Like I said, this stuff is hard. I wrote a very detailed simulator for the Rust/C++ memory model, have implemented dozens of lockless algorithms, and I still make a mistake every time I go to write code. You need to simulate it with something like Loom to have any hope of a robust implementation.

For anyone interested in learning about Rust's memory model, I can't recommend enough Rust Atomics and Locks:

https://marabos.nl/atomics/
by kjs3 | 2025-11-02 14:56:52+00:00
It's a embrace-extend-extiguish play like the old days. Add a 'feature' that doesn't technically break the rules (or only does a little), get your users used to it (by making it the default, opt-out, etc) and hope that your users will pressure people not using your product to move. "What do you mean you didn't see my email reaction? That's the best feature in the whole world. You should really switch to outlook, etc.". See: every M$-only feature in IE.
by jesterson | 2025-11-02 14:56:54+00:00
It’s advisable not to judge within your limited worldview. Not everyone “reads” mainstream media, some people have real world experience.

Your arguments regarding why Ukraine can’t be used for money laundering are laughable and just show you are now aware how certain things in financial world work. That’s totally fine - but it gets distorted when some extended judgements are made based on very limited worldview.
by __jonas | 2025-11-02 14:57:31+00:00
I feel like this is going nowhere...

The question was: What do people use now to create HTML tables instead of the table manipulation API described in this blog post.

I said:

- If you render a table on the client (not what JS was originally built for, but what it is often used for now) using a framework like React, you declaratively render the table using its semantic elements (table, thead, tbody, tr, td etc.) instead of imperatively building it up using that API

- If you render a table on the server, you essentially do the same (output the table markup)

That's why I described the above mentioned table API as "niche", which you seem to have taken offense with but I still have no idea why.

Maybe you're suggesting that this API is commonly used to add interactivity to a table element on a page with JS? I could see it being used for that, no idea if it is, I still have the feeling that just using regular Element APIs is more common - the question was also about creating tables specifically, not manipulating them, so that's why I mentioned declarative frontend frameworks.
by evnc | 2025-11-02 14:57:44+00:00
Interesting. Does that mean if you want to say, make an asynchronous http request, you do something like “fire_event(HttpRequestEvent(…))” which returns immediately, and somewhere else define a handler like “on_event(HttpResponseEvent, function (event) { … })” ? So you kind of have to manually break your function up into a state machine composed of event handlers? How do you associate a given HttpResponseEvent with a specific HttpRequestEvent?
by kevincox | 2025-11-02 14:57:55+00:00
Yeah, I would happily run a bunch of my network services in this. I have loads of services that are public-facing doing a lot of complex parsing and rule evaluation and are mostly idle. For example my whole mailserver stack could probably benefit from this. My few messages an hour can run 2x slower. Maybe I would leave dovecot native since the attack surface before authentication is much lower and the performance difference would be more noticeable (mostly for things like searches).
by embedding-shape | 2025-11-02 15:00:09+00:00
Does that handle back button correctly? Nothing more annoying that sites/apps that overwrites the history incorrectly, so when you press the back button it goes to the entry before you entered the website/app, rather than back into what you were doing in the website/app.

Both approaches (appending/rewriting) have their uses, the tricky part is using the right thing for the right action, fuck up either and the experience is abysmal.
by gagik_co | 2025-11-02 15:01:15+00:00
My app is for chat-based notes[1] and I have been wanting E2E local-first sync on it for a while. Switched from Realm to SQLite after it was deprecated but never found a good non-niche DB SDK for it on Flutter. Tried to handroll sync + AES-GCM encryption with Supabase Realtime and it kind of worked but I knew managing encryption was going to be hell and also wanted collaboration features. Matrix was built for chat, and at some point I read someone call it basically a graph sync engine & potentially supporting general texting with other clients also seemed like a cool bonus.

That said, adopting it (even partially) was/is a big mess, there's a thousand corner cases with key exchange, etc. so it's really a big commitment, especially if there's no existing user-friendly SDK for it.

I'm not using yjs (yet), just going to more basic event sourcing that is essentially last-write wins but that's a direction I want to explore in the future.

[1] https://tetrify.com/
by throwaway2037 | 2025-11-02 15:02:07+00:00
> I was able to get dates 5+ nights a week and date 2-3 new women a week

For the record, you are probably well into the top 20% of attractive men on the apps. You should know that your experience is very much unlike the average man. The average normie on dating apps (5/10 in looks) gets, quite literally, zero matches, or matches only from scammers/bots/OnlyFans. There are numerous long-form YouTube videos on the topic with first hand experience.

> the quality of dates was significantly worse than what I used to get from just approaching women in places like

This is an interesting comment. Can you share one or two specific things that come to mind? I can offer one from my personal experience: When you approach someone in public (get their number, etc.), then later meet them for lunch/drinks/dinner, their enthusiasm and effort is much higher than people I meet on the apps.
by surajrmal | 2025-11-02 15:02:38+00:00
All major projects need to be done this way. Upfront design without any concrete feedback from a real implementation of that design will always be flawed unless incredibly simple. If anything, the next evolution of this is a process to determine which experiments are worth running to get to a point where you can come up with a sensible design. In organizations I've worked in, the first phase is known as problem framing, which quickly evolved into requirements gathering. From there you come up with several possible loosely defined designs which you pursue in parallel and then at some point, with data in hand you come back and decide on a path forward, possibly needing a few more iterations of experiments based on what you've learned. Reaching agreement early on the problem and requirements really does help the rest of the process move forward, and makes deciding on a final choice much simpler and less political.
by galangalalgol | 2025-11-02 15:03:07+00:00
People have used mrustc like that to put rust on a c64. The number of targets that make sense from a word length perspective that aren't already supported by llvm are pretty small I think? You aren't going to compile rust to some fixed point dsp where a long is 48bits. The c anything is likely to generate won't compile in whatever odd not-quite-ansi c compiler the chip maker provides.
by ziml77 | 2025-11-02 15:03:57+00:00
As someone squarely in gen y. I've had the same feelings about me doing stuff that others are associating with gen z.

I think there may be two things at play here. One is that some people are just bad at adapting to social shifts and assume that everyone is the same way as them. The other is that people have gotten loose with usage of generation terms. So for some older people "gen z" = "person younger than me", while for some younger people "boomer" = "person older than me"

And both of those are problems with the speaker, so now I just ignore them and happily keep on doing the "gen z" things.
by bensg | 2025-11-02 15:05:12+00:00
Thanks for the feedback. You raise three important points that I'll address in turn:

1. Biomass: We report renewables as defined by Ofgem (the UK energy regulator), which for better or worse includes biomass. However, we recognise this is contentious. To address this, we show the breakdown of generating technologies for each supplier so users can see the composition. But regardless, your point is valid and has been raised several times this week, so we have a PR open to add a filter that lets viewers exclude biomass if they disagree with the UK's legal definition.

2. Nuclear: Our initial focus was on renewable power (where intermittency is highest), but we'll be adding nuclear to the index in the next few weeks. This will increase the scores for EDF, Octopus Energy, and British Gas in particular, who purchase the majority of nuclear power. We've called this out in various places on the index (e.g., on the EDF page: https://matched.energy/clean-power-index/edf-energy).

3. Load shifting: Because we measure generation and demand at a half-hourly level, we do account for load shifting that suppliers like Octopus incentivise through agile tariffs. This is actually one of the key advantages of our approach over historic annual accounting; the half hourly temporal granularity means we reward load shifting behaviour.
by dmje | 2025-11-02 15:05:22+00:00
The whole (original) premise of social media was "let's make a more human side of our business so that people can connect with us". Now we've come full circle where the robots are making all the social content and increasingly the robots are the ones consuming it too.

Weird, uncanny valley times. And, FWIW, not times I want anything to do with, hence why I've been off all social media for years now...
by throwaway2037 | 2025-11-02 15:05:42+00:00
> Looking for dates on there gave me a similar feeling as looking for a house on property sites. Yes, I really want a house and there are houses here. But I am still hating this experience of looking at houses.

I like this final paragraph. You touch upon an important emotional issue. Most people want to believe in the fairy tale stuff of chance meetings, true love, etc. The whole idea of a "marketplace" to find a partner is so off-putting. Yes, it is practical, but it is emotionally unsatisfying.
by durul | 2025-11-02 15:06:20+00:00
I just wanted to share my latest Vision Pro project, StratoSync — it allows you to see the ISS orbit live in your space, with Earth spinning in front of you, orbit trails glowing, and real data updating every 5 seconds.

Built entirely with SwiftUI + RealityKit, it’s been an incredible journey into VisionOS and spatial computing.

Here’s the TestFlight link: https://testflight.apple.com/join/tWS4CERT
by adolph | 2025-11-02 15:06:23+00:00
Hanselman famously said “URLs are UI” and he’s absolutely right

A challenge for this is that the URL is the most visible part of an HTTP request but there are many other submerged parts that are not available as UI yet are significant to the http response composition.

Additionally, aside from very basic protocol, domain, and path, the URL is a very not human friendly UI for composing the state.
by ghaff | 2025-11-02 15:06:23+00:00
They did buy Red Hat (for a lot of money) and seem to have generally gotten their AI act together although not as visibly as the high profile SV players. Mainframe business seems to hum along. There's also quantum though not a big revenue source yet.

So, overall, seems a pretty decent business at this point although not something that is on a lot of HN readers' radars. Yes, it's oriented towards large companies and public sector.
by rawgabbit | 2025-11-02 15:06:28+00:00
Nice article that sums up the modus operandi of rudderless companies.

Quote:

This is the pit into which HP and IBM have fallen. They want to maintain margins to keep Wall Street happy, but the easiest way to do that is by cutting costs. Eventually this will be visible in declining sales, which IBM has now experienced for three straight years. Yet with a combination of clever accounting and bad judgement even declining sales can be masked… for awhile.
by r_singh | 2025-11-02 15:06:46+00:00
Here’s how I decide what to use:

ChatGPT – journaling, talking, planning. Codex – framework and middleware-layer coding. Claude Code – logic and application-level coding. Anthropic models via OpenRouter + Cline – when the task is error-prone, tedious, or needs high fidelity; lower error rate in my experience, though pricier. Cursor Agents – multi-file integration, boilerplate, and forking tasks.

Each fills a different slot in the workflow, so “best” depends on what kind of coding you’re doing.
by gkfasdfasdf | 2025-11-02 15:07:06+00:00
> image-manip squash: This is the key to reclaiming disk space and the core of our strategy to squash the image layers. The tool creates a temporary container, applies all 272 layers in sequence to an empty root filesystem, and then exports the final, merged filesystem as a single new layer. This flattens the image's bloated history into a lean, optimized final state.

Wouldn't a multistage Dockerfile have accomplished the same thing? smth like

FROM bigimage

RUN rm bigfile

FROM scratch

COPY --from=0 / /
by syngrog66 | 2025-11-02 15:07:17+00:00
like how moving money atomically between 2 remote databases was a solved problem then some guy said, "Yes but let's reinvent that using blockchain!" and all the dystopic effects the world has seen since. indirectly leading to the overinvestment in massive amounts of GPU hardware which then got repurposed by the AI/LLM folks. funny that
by kragen | 2025-11-02 15:07:38+00:00
(02015) but both HP and IBM seem to be alive and well 10 years later, even if their products are dog vomit.

This phrase "confusing the scoreboard with the game" is golden!

IL14 is a lot better than Cringely's commentary on it: https://www.fourmilab.ch/autofile/www/chapter2_86.html
by the__alchemist | 2025-11-02 15:07:57+00:00
My 2C: What we need isn't a translater, but painless FFI. The FFI tools avail like cc and bindgen make working results most of the time, but they need [manual] wrapping.

It's kind of a similar situation (Although a bit more complicated) exposing Rust libs in python; PyO3/maturin do the job, but you have to manually wrap.

So... I would like tools that call C code from rust, but with slices etc instead of pointers.
by kevincox | 2025-11-02 15:08:37+00:00
I would assume that these two use cases are basically completely separate.

Auto-translate from C to Rust would serve as a great step to starting a porting project. Now you can incrementally re-write the "basically C" auto-ported code to "proper Rust" without dealing with FFI and other pains that come from function-by-function ports.

Fil-C is great for running software that you don't want to port. (Or don't yet have the resources to port.)

Interestingly there is probably a gap between the two. When your project is pure C you can use Fil-C. However I don't think Fil-C supports Rust. So assuming that the initial C to Rust translation doesn't produce 100% safe code (I'm not aware of any current tools that do this) you have this middle state where you can no longer compile with Fil-C but have lots of unsafe Rust code. So maybe there is a use case for Fil-Rust where you compile your Rust program so that even unsafe blocks are in fact safe. This could be used until you complete the port.
by throwaway2037 | 2025-11-02 15:09:28+00:00
> Being bad at apps means you are either ugly, or your pictures are bad.

For the record, I assume you are speaking about men whom are seeking women. The reverse is certainly not true.

> He had ... an obvious 6 pack.

This is very specific. Did he have shirtless photographs? I assume yes.

It fascinates me that if you listen to what women say, 95% will say they dislike dating profiles the most when the man has shirtless photographs. Yet, 95% of women will also say that guys with a six pack are hot. It reminds me of the old adage: "Watch what women do, not what they say."