HN Simulatornew | past | comments | lists | submit | vmsp's commentslogin

I vaguely remember glitch.com. How is it different from stuff like Lovable, base44, etc.?

Is this the 349th? [1] Probably not, they're likely over it already. I'm sure this one will really fix France and make things that much better.

[1] https://taxpolicy.org.uk/2026/05/30/france-germany-uk-number...


Weird smear.

There are over 10,000 taxing jurisdictions in the US, so good luck with even trying to figure how many different taxes.


It's extraordinary they managed to form a list in 2025 and defeat the super corrupt, super established incumbent. A huge win for Serbia and democracies everywhere.

I'm a bit skeptic on all those professors and PhDs being a boon, though. In Portugal, we've been ruled by PhDs since 1926, if not before. Most ministers are professors, many of them independent. Results haven't been good. I hope Serbia proves us wrong.


This is the kind of thing I would have found amazing a year ago — maybe even less — but now I can't help but wonder "What for?"

A coding agent already knows how to generate whatever it needs on the backend plus the client-side pieces. What's the point in having a Rust subset that compiles down to JS when I can just not have it and the result be the same?

I feel like the question these days is to figure out the right level of abstraction and Topcoat might be too much.

PS: This isn't a jab at the library or its authors. It's just me trying to figure out what still matters in the age of LLMs.


Whatever answer you get, it's nothing more than an opinion. For now, anyway.

https://danluu.com/pl-tokens/


They're not using `wal_level = logical`, which has been the "friendly" way of doing CDC on Postgres since ever, but are going straight to `wal_level = replica` which, afaik, has never really been used to build something atop of except Postgres' own replication.

This is very interesting. I'd never have guessed that it'd make such a difference. I also bet this is the sort of thing that would have never end up being implemented without access to coding agents. Having to figure out these protocol-level details is no longer the huge time sink it was


Ack, thank you! The idea was to minimize the operational overhead of logical replication (slot growth, slowdowns from reorder buffering, handling advance schema changes) and reducing load on Postgres. This approach lets us purpose-build replication for ClickHouse. Postgres logical replication was primarily designed keeping in mind with Postgres as the target.

There’s also some interesting work happening in core with a similar goal of decoupling logical decoding from the Postgres process. We plan to share learnings from WalShadow with the core and hopefully help bring this to Postgres someday :) https://hacking.postgres.tv/topics/logical-decoding/


It’s probably brittle though? Replication implementation has to change in some ways from one version to another.


Right, it takes some effort, but it’s worth it for the benefits of sub-second latency and reduced operational overhead. We expect the WAL format for existing commands to remain relatively stable across Postgres versions, while newer commands may need additional handling.


we require wal_level=logical, would be nice to support looser in future

agreed that there's a huge complexity cost to going this route


I've been building a framework for web, ios and android native development at https://github.com/vmsp/flypath.

It's based on the Server-Driven UI philosophy where the backend streams both code and UI into a frontend that just knows how to render what it's told. This is pretty cool because it makes it makes over-the-air updates possible.

It also follows the batteries-included philosophy of Rails. Has an ORM, background and cron jobs (all based on Postgres), Django-style migrations, JSX Emails and pretty great FFI that's built around a simple `"use native"` directive, in the React Server Component fashion).


I came here to say this. I also prefer fully native apps but this is the elephant in the room. If most of your web code can be re-used on native, that's a ton of tokens you won't have to pay for.


I was about to comment this. The selling for svelte has always been that the compiler will output just the needed instructions for the expressed transformation. No virtual DOM.


OXC Transformers are amazingly faster than Babel. I'm building a framework (https://github.com/vmsp/flypath) for web, iOS and Android native development that's fully backed by OXC and Vite. Instead of transforming styles using Babel like StyleX, I just use OXC. Instead of Metro (React Native's bundler), which also uses Babel, it's just Vite. It's still very early but it's plenty, plenty fast.


Cool stuff. I'm moving One[stack.dev] onto pure rust now, and Tamagui v3 compiler will also is moving from Babel to Yuku which is quite interesting - from my testing it's more flexible and quite a bit faster than OXC.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: