Birbla

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

Sign in
  • Hacker News
  • Sounds a lot like Liveview in Phoenix.
    by victorbjorklund
  • I bet with AI we will complicate existing apps because it is now easier to develop.
    by devops000
  • It's interesting to see that they let you mix markup with logic directly in rust, but I have worries about maintainability. I remember the bad old days of PHP where you'd mix markup with logic directly, even when doing OOP with classes and it really made things more difficult long term.
    by sc68cal
  • I used to write Leptos, but abandoned it. I hoped the experience would get better, it took a lot of memory just for the language server to validate especially. Web apps become too cumbersome to maintain in bigger distributed teams where we want fast feedback. I think writing web apps in straight rust will always be niche. There's not many frontend devs who write React or Vue who want to write straight Rust just because of safety or performance.

    That's why I created SnapFire FSR (https://www.snapfirers.com), but many examples, to allow frontend devs to develop in their favorite framework (or mixture of). Write Tera templates, Web Components if you don't want to bring in frameworks like I tend to. Don't need to pay massive switching costs which, even with, AI not fun.

    I found it much better to create and maintain web apps near the markup and language they originated from. You won't find me writing straight Rust for Web Apps unless I need to anymore.

    I'm going to continue to work on this and switch all my leptos and svelte sites over.

    by excsn
  • 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.

    by vmsp
  • I really like the direction Topcoat is going in as a Rails developer. Although it is just a bit itchy to my eyes, it is not acid-level, though.

    The things that look great are LiveView and getting rid of boilerplate for client-side reactivity

    by lackoftactics
  • Some absolutely great work, but I don't know why you would come up with a new term for a server component (shard). Why not just use the obvious client/server annotations so you don't have to define a novel term for new users?
    by jazzypants
  • > Rust is the best general-purpose language for the new world of AI-driven development.

    Funny, the Python guys say Python is the best general-purpose language for AI and the Go guys say Go is the best general-purpose language for AI etc etc

    by muglug

Explore Birbla archives

Topcoat is pushing the boundary of server applications with Rust · Birbla