MurphyA/hacker-news huggingface dataset:
by yurishimo | 2025-10-10 12:55:42+00:00
It entirely depends on the type of application you are building. Boring CRUD app that is rarely updated? Yea, server rendering is probably enough.

But the requirements of "modern" software are always changing. Sure, the static table might be enough, but then some business person says, "It sure would be nice if I could check a little box in the table row or assign this user here..." and now you're adding little JS hacks. Again, not impossible, but at a certain scale, the ability to have infinite access to client driven reactivity becomes a real business empowerment.

Given the interest in the JS working group to add reactive Signals to the core language, I suspect this will only become _more_ prevalent in the future. Maybe it will need less input from frameworks to do the same work and we can move back towards using built-in browser APIs, but the programming model itself works really well (so much so that SwiftUI uses a very similar reactive UI programming model).

Again, I don't disagree with your point, just at a certain scale, it becomes a huge hassle to maintain. If people are going to use these tools and frameworks anyway, it helps the entire web to make them more efficient.
by Spooky23 | 2025-10-10 12:56:18+00:00
You can’t live in it. Average stay is has to be <7 days.

It makes sense to do if you’re in the 35% bracket. You buy a condo or a house. So you buy a house, airbnb it for one year, then rent for 2-5 more. Then you 1031 exchange it and do it again. If you don’t trade up, you have to keep the property or they recapture the bonus depreciation on a prorata basis later.

Airbnb hasn’t been about couchsurfing in a long time. It’s a mechanism to monetize real estate under more favorable tax rules.
by nchmy | 2025-10-10 12:56:52+00:00
As ive said in many other comments - YOU DO NOT NEED PRO. The devs are very adamant about this - even aggressively so. 99% of apps will work just fine with the free library. Pro is for some bells and whistles, or just to support people who have invested many thousands of hours into making a genuinely innovative framework, and given it away
by poszlem | 2025-10-10 12:57:32+00:00
This isn't an "everyone who struggles to finish projects or is a perfectionist has it" kind of post, but if this has been a long-term pattern for you, one that's caused real suffering, lost jobs or contracts, or kept you from finishing important work - please consider getting checked for ADHD. It took me 42 years to get diagnosed, and starting on stimulants genuinely changed my life and pretty much solved those issues for me.
by diiiimaaaa | 2025-10-10 12:58:20+00:00
I recently had to setup another complex monorepo with eslint/vitest/vite/tsup/turborepo and it was such a pain. All the time either eslint breaks for some file, or some build breaks because of some obscure thing in tsconfig, turborepo behaves in a weird way, adding new packages is a pain, etc.

Hopefully Evan can pull this off and we have simpler initial setup.
by intrasight | 2025-10-10 12:58:35+00:00
Far from dead. Usage is growing.

HTMX is a single htmx.js file with like 4000 lines of pretty clearly written code.

It purports to - and I think succeeds - in adding a couple of missing hypermedia features to HTML.

It's not a "framework" - good

It's not serverside - good

Need to add a feature? Just edit htmx.js
by benrutter | 2025-10-10 12:58:51+00:00
> Humor, despair and any bias of mine aside. I am quite seriously unaware of anyone with a good opposition plan, to reverse the power centralization, at this point.

Interesting point! Bit of a tangent, bit Brazil is in the process of holding Bolsonaro to account for power grabs that have a lot of similarities with what's happening in the US.

Too early to call their long term efficacy, but definitely one to watch.
Show HN: AI Voice AudioBook – Convert ebooks to audio with your cloned voice
by pengfeituan | 2025-10-10 12:59:01+00:00
Hi HN, I'm P.F. Tuan, an indie, and the solo developer behind AI Voice AudioBook. Thanks for checking out my project! The "Why": I have a long commute and a huge list of articles and books I want to get through. I tried a bunch of text-to-speech apps, but I could never stick with them because the robotic, generic voices were so grating to listen to for more than a few minutes. I started wondering: what if I could listen to a book narrated in a voice I actually enjoyed, or even my own? That's the core idea behind this app. The "What": AI Voice AudioBook lets you turn any ebook (EPUB, PDF, TXT) or web article into an audiobook. The key feature is the voice: You can clone your own voice by providing a short audio sample. Or, you can use one of the premium, natural-sounding AI voices available in the app. It also automatically strips out ads and other clutter from web pages, so you get a clean listening experience. Tech Details: The app is built natively with Flutter. For the backend, the voice cloning and TTS generation are handled by a combination of commercial and fine-tuned open weight models based on self-collective dataset. One of the trickiest parts was reliably parsing clean text content from messy HTML, which leverages LLM processes. What I'm looking for: I'd be incredibly grateful for your feedback, especially on a few things: The Voice Cloning Process: Is it intuitive? How is the quality of your cloned voice for long-form listening? Especially for non-English languages. Is the service stable for various texts? Especially for non-English languages, we need to adjust our training dataset according to the feedback. Is the UI convenient? As there are many AI tools inside. The Web Article Parser: Does it work well on your favorite sites? Pricing: The AI models are expensive to run. Does the current pricing structure seem fair and make sense to you? I'll be here all day to answer every question. Thanks again for your time!

P.F. Tuan from ZanChat
by seec | 2025-10-10 12:59:20+00:00
I agree, software development has become insane. It's basically people creating problems to justify their existence, very much like the bureaucrats.

The reality is that the vast majority of people don't really need "self-hosting", what they would need is a decent software that they can run on their computer and let others access the data from time to time, mostly locally because global availability is rarely worth the hassle.

But since there is not much money into that and devs are enamored with insane layers of complexities and obtuse use case that are irrelevant for the vast majority we get the server software, that relies on web views and have a large disconnect with the data on a local machine. You just had another layer of stuff to manage on yet another computer when most already have one sitting idle the vast majority of time. I think the laptop craze is also partly to blame.

Even good local Mac apps have dried up and now it's all cloud-based subscription software, and you are supposed to be thankful you can install open-source stuff with a docker image and god knows how many configuration steps and gotchas.

Many of those softwares would be desirable and worth a bit of money if only you could just have a simple installation and management process but instead you have to pay with your time, which is not worth it for most. So, at this point, people just say fuck it and pay someone else, usually one of the big tech providers to take care of the problem and that's that.

As much as I like web technology for interactive documents, the software use case is still largely a pain in the ass.
by sgarland | 2025-10-10 12:59:43+00:00
To clarify, I was working with 2nd Quadrant BDR (now Enterprise DB Postgres Distributed), running on some extremely large EC2 instances, in a global mesh - IIRC, five regions. Also in fairness, EDB told us that we were the largest mesh they had seen, and so we frequently ran into fun edge cases.

Each node had N replicas running vanilla Postgres attached, which were on EC2s with node-local NVMe drives for higher performance. This was absolutely necessary for the application. There were also a smattering of Aurora Postgres instances attached, which the data folk used for analytics.

In no particular order:

* DDL is a nightmare. BDR by default will replicate DDL statements across the mesh, but the locking characteristics combined with the latency between `ap-southeast-2` and `us-east-1` (for example) meant that we couldn't use it; thus, we had to execute it separately on each node. Also, since the attached Aurora instances were blissfully unaware of anything but themselves, for any table-level operations (e.g. adding a column), we had to execute it on those first, lest we start building up WAL at an uncomfortable pace due to replication errors.

* You know how it's common to run without FK constraints, because "scalability," etc.? Imagine the fun of having devs manage referential integrity combined with eventual consistency across a global mesh.

* Things like maximum network throughput start to become concerns. Tbf, this is more due to modern development's tendency to use JSON everywhere, and to have heavily denormalized tables, but it's magnified by the need to have those changes replicated globally.

* Hiring is _hard_. I can already hear people saying, "well, you were running on bare EC2s," and sure, that requires Linux administration knowledge as a baseline - I promise you, that's a benefit. To effectively manage a multi-master RDBMS cluster, you need to know how to expertly administrate and troubleshoot the RDBMS itself, and to fully understand the implications and effects of some of those settings, you need to have a good handle on Linux. You're also almost certainly going to be doing some kernel parameter tuning. Plus, in the modern tech world, infra is declared in IaC, so you need to understand Terraform, etc. You're probably going to be writing various scripts, so you need to know shell and Python.

There were probably more, but those are the main ones that come to mind.
by tptacek | 2025-10-10 13:00:07+00:00
There isn't one! TCP running on top of UDP would have been a reasonable design. TCP/IP is full of warts like this. The URG pointer. The conflicting length fields.

The fact of ICMP not being itself a UDP protocol caused major problems for systems programmers, because it meant that OS kernels all "owned" ICMP, provided only a baroque sockopt programming interface to like 5% if it, and required userland programs to hold suser privileges to do any real ICMP work. Awful design. And ICMP is slow-pathed by routers, because it isn't UDP.

UDP literally doesn't do anything but multiplex raw IP. Unless you're actually worried about the 8 bytes the header takes up, there's no reason, none at all, to slide a new IP protocol anywhere but on top of UDP. Again: that's why UDP was designed in the first place. You can go look this up! David Reed still talks about it!
by simonw | 2025-10-10 13:00:13+00:00
Looking at https://data-star.dev/reference/datastar_pro#pro-features the features that stood out for me as things I would want to to use (and that don't feel particularly "pro" to me) are the animation features, data-replace-url, data-on-resize, data-scroll-into-view, the @clipboard() mechanism and, most importantly, the debugging tool.

My problem with this business model is that it has a chilling effect on open source contributions to the project, because it incentivizes the core maintainers to not accept community contributions that overlap with the paid features.
by johnthewise | 2025-10-10 13:00:16+00:00
why? The purpose of the prediction market is not to be fair to market participants, it's to aggregate information regarding an event. There is a public benefit to allowing participants to bet on insider information. It could be even argued there is nothing unfair about it if everyone is free to do it/can anticipate others might have insider info. If we actually limited the market to participants who have insider information(not feasible because we can't verify), that'd be a great public utility. this is the next best thing for all those who don't participate in it. These are specialized markets and we shouldn't rush to 'protect' people who bet on very technical events happening.
by CodingJeebus | 2025-10-10 13:00:27+00:00
Capitalism is not a panacea and its history is steeped in blood.

The Dutch VOC, considered one of the first capitalist enterprises, carried out genocide in its pursuit to control spices in the Indies.

Capitalist interests in the US interfered in South American politics for decades, overthrowing democratically elected leaders and funding militias aligned with corporate interests. One of my closest friends is Guatemalan and most of his family was killed during the United Fruit Company conflict.

The Russians experienced one of the largest declines in quality of life in human history after the Soviet Union fell and the country became privatized.
by YuukiRey | 2025-10-10 13:00:39+00:00
No it's not out of date. It's very much the reality. Every new tool is just one more thing added on top. When I have to do something in a JS/TS repo at work it's always a surprise which epoch of JS hype stuff I find. Today I fix ESLint warnings, tomorrow it's Biome errors, then I need to figure out how to override dependencies in pnpm, but oh no there's a some bug in Bun now. Did I forget the 10249120491412e12 config options of Jest? Ah no wait, this one is Vitest.

For NextJS, do you remember the runtime used for middlewares? What was this swc thing again?

It never ends. Every year new things are added and they never really replace anything, it's just one more thing to learn and maintain.

If every technology causes exactly 1 issue per week then you quickly spend 50% of your time fixing bugs that have absolutely zero to do with what your company is actually doing.

---- EDIT

And it doesn't even stop at issues. Every one of those technologies regularly goes through breaking changes. In the process, plugins are deprecated, new ones have completely different APIs. You want to upgrade one thing for a security fix, then you're forced to upgrade 10 other things and it spirals out of control and you've spent entire work days just sifting through change logs to change `excludeFile` to `excludedFile` to `includeGlob` to `fileFilter` to `streamBouncer` to I don't know what.
Ask HN: Claude Code Alternative
by muddi900 | 2025-10-10 13:00:40+00:00
Claude pretty much killed the cli app for Pro users. The new usage limits mostly make it useless. I am not a pretty heavy user, and rarely reached the previous limit. Even my context rarely reached auto-compact limit.

Now it takes me 20-30 minutes of use to reach the session limit. I can upgrade to higher tier, but he next higher tier costs 10 times the current tier.

I tried Gemini CLI, and it is good. But the inability to whitelist/blacklist terminal commands makes it too counterintuitive. If I have to approve every terminal command, then I might as well run them myself and save the token cost.

I believe Qwen-coder is based on Gemini CLI and has similar issues. Is there any other alternative?
by nchmy | 2025-10-10 13:00:45+00:00
Its interesting, and telling, that that's the only part of my comment that you replied to...

Anyway, browsers are built specifically to render HTML. And html/hypermedia is specifically meant to manage and transfer state. The web has lost its way. If you want to read more about this, this free book is a great start: https://hypermedia.systems/book/contents/

Or the essays at HTMX https://htmx.org/essays/

Good luck to you
by gethly | 2025-10-10 13:01:03+00:00
It is quite simple.

Datastar keeps the logic in the backend. Just like we used to do with basic html pages where you make a request, server returns html and your browser renders it.

With Datastar, you are essentially doing kind of PWA where you load the page once and then as you interact with it, it keeps making backend requests and render desired changes, instead of reloading the entire page. But yo uare getting back snippets of HTML so the browser does not have to do much except rendering itself.

This also means the state is back in the backend as well, unlike with SPA for example.

So again, Datastar goes back to the old request-response HTML model, which is perfectly fine, valid and tried, but it also allows you to have dynamic rendering, like you would have with JavaScript.

In other words, the front-end is purely visual and all the logic is delegated back to the backend server.

This essentially is all about thin client vs smart client where we constantly move between these paradigms where we move logic from backend to the frontend and then we swing back and move the logic from the frontend to the backend.

We started with thin clients as computers did not have sufficient computing power back in the day, so backend servers did most of the heavy lifting while the thin clients very little(essentially they just render the ready-made information). That changed over time and as computers got more capable, we moved more logic to the frontend and it allowed us to provide faster interaction as we no longer had to wait for the server to return response for every interaction. This is why there is so much JavaScript today, why we have SPAs and state on the client.

So Datastar essentially gives us a good alternative to choose whether we want to process more data on the backend or on the frontend, whilst also retaining the dynamic frontend and it is not just a basic request-response where every page has to re-render and where we have to wait for request to finish. We can do this in parallel and still have the impression if a "live" page.
by lovelearning | 2025-10-10 13:01:15+00:00
Because "just say it" doesn't work on many sites. I don't know about this site but anecdotally, I've seen that when I use certain words / phrases / names on YouTube or Reddit subreddits, those comments are either not shown at all (not shown even to me) or shadow-banned (not shown to others).

Another reason I don't just say it sometimes is to avoid trolling by fans of whatever or whoever I criticized.
by traceroute66 | 2025-10-10 13:01:17+00:00
> compared to CockroachDB

CockroachDB != PostgreSQL.

I take great issue with the way CockroachDB marketing seeks to imply compatability, when infact what they are promising is wire protocol compatability (i.e. you can fire up your copy of psql on the CLI and it will connect).

Last time I looked, a great number of primitive, obvious, fundamental, low-hanging fruit were completely absent from CockroachDB, e.g. (IIRC) stored procedures are nowhere to be seen in CockroachDB.
Show HN: Rustacean AI – Tracking Rust's Expanding Role in AI
by nogueian | 2025-10-10 13:01:51+00:00
Rustacean AI, a weekly newsletter exploring how Rust is shaping the future of AI and Machine Learning. Issue #1: From Models to Data — Rust’s Expanding Role in AI Covers the growing Rust ecosystem around AI frameworks (Burn), data systems (Polars, Qdrant, Daft), and emerging tools that power safe, high-performance pipelines. The goal is to curate news, releases, and experiments from across the Rust + AI community — helping developers follow how the language is influencing the next generation of infrastructure. Read first issue here → https://rustacean.ai/p/issue-1-from-models-to-data-rust-s-ex...
by inetknght | 2025-10-10 13:02:51+00:00
I haven't had that problem. I just code something up, and poke around to understand some of the terms that it's talking about. Then I start reading about error return codes, why them happen, what kinds of parameters actually mean, etc. No examples are usually needed as long as documentation is complete

The most frustrating things are things that are undocumented at all and only have examples. What the hell kind of shitty documentation is just examples with no idea what parameters could or shouldn't be?!
by raxxorraxor | 2025-10-10 13:03:12+00:00
Visa and Mastercard are subjected to political pressures to disincentivise conducting transactions. If the market would be more diverse, these pressures would be way less effective.

If a digital € would change that is questionable though. Perhaps ambitions would get even worse.

Also a very good argument for cash. I like untracable transactions. I isn't just to benefit crime, it is also about privacy.
by pas | 2025-10-10 13:03:34+00:00
... but the whole social movement of "back to the backend" is about getting rid of the client-side application as a separate component

of course it (should) lead to a lot less code! at the cost of completely foregoing most of the capabilities offered by having a well-defined API and a separate client-side application

... and of course this is happening as over the last ~2 decades we mostly figured out that most of that amazing freedom on the client-side does not worth it

... most clients are dumb devices (crawlers), most "interactions" are primitive read-only ones, and having a fast and simple site is a virtue (or at least it makes economic sense to shunt almost all complexity to the server-side, as we have fast and very capable PoPs close to users)
by delichon | 2025-10-10 13:03:37+00:00
From the New York Times "The Daily" podcast today:

Mark, what you've described and what we're seeing unfold is genuinely an impressive feat by Trump. To be able to capitalize on what seemed like this giant setback. Israel literally bombed the negotiators and the mediators. To turn that around and get a deal that Biden couldn't get done, that no other leader in the world had managed despite trying for two years straight. It is significant achievement. He was able to bring these sides together that had shown no willingness to end the war. And now they've come to this agreement. And it should also be said that one of the biggest things here is that he was willing to put pressure on Netanyahu in a way that President Biden was unwilling to do. Why do you think that's the case? I think there's a few reasons. First, I think Trump genuinely wanted to end the war. He campaigned on ending the war in Ukraine and in Gaza.

Too late for this year, but if it holds it should be considered for next year.
by EvanAnderson | 2025-10-10 13:03:54+00:00
I find it's important to remember, too, that a failed PING tells you nothing other than your echo request did not receive a response. If the remote host received your request, and if it responded, are both things a failed PING can't tell you, because both of those things could be true but you still end up with a failed PING.

I've seen technicians get tripped up in troubleshooting thinking that a failed PING tells them more than it does. When the possibility of asymmetric return paths is involved it's always important to remember how little a failed PING actually tells you.