Carl Lerche

@yehor_smoliakov @ayushagarwal027 Templating is highly opinionated. It is OK to have different preferences.

@ayushagarwal027 idk, templating is better with askama and htmx in rust web

The Tokio team just released Topcoat : a batteries-included, Rails-style fullstack framework for Rust. 🦀 The standout idea: write one $(...) expression in ordinary, type-checked Rust. It runs on the server for the first render, and Topcoat also translates it to JavaScript so it re-runs instantly in the browser, no WASM bundle, no separate client build step. What's included: → Server-rendered async components that can query the database directly : no separate API layer needed → view! macro : HTML templates using real Rust control flow (for, if) → Module-based routing : route tree inferred from your file structure, no build step → Premade UI components (Tailwind-based, shadcn/ui-inspired) copied into your project, fully editable → Built-in asset bundling, Tailwind integration, htmx support Still early-stage and experimental, with breaking changes expected. Roadmap includes auth, background jobs, WebSockets, and streaming SSR. From the team behind Tokio itself, worth watching closely. 🔗 github.com/tokio-rs/topco… #RustLang #WebDev #FullStack #Tokio #OpenSource

Should we still write the Topcoat announcement blog post? 🤔

@XyzPilot1 Topcoat moved so fast, it shipped before it was announced.

@carllerche Move this fast on Topcoat :) x.com/RyanCarniato/s…

@nevgeniev @FrancescoCiull4 And they have been improving. There are also a few initiatives in progress that should meaningfully reduce build times.

@carllerche @FrancescoCiull4 That's what we hear for the last 5y

We are ive Listing bad and good things for rust in the next 10+ years.

@mixednuts_rs I choose to take the more charitable read and/or ignore snark. Lets' just focus on the tech and tradeoffs.

@carllerche I mean yes, sure, but they still don't get that I want compile time safety. They can be snarky all they want, but no, it's not better than Rust's safety

More safety is always a good thing and it is always worth trying different avenues. This is why having many different programming languages is good. The best ideas gain traction and there can be cross pollination.

@msimoni Also, I skimmed the entire article and did not see any mention of "outlawing" C. Do you have any evidence that there was an effort to lobby legislators to make writing new C code a crime?

@carllerche @ognian.milanov/forcing-rust-how-big-tech-lobbied-the-government-into-a-language-mandate-40ee80cbc148" target="_blank" rel="nofollow noopener">medium.com/@ognian.milano…

I have nothing against Rust, I think it's a fine language for many applications. However, parts of its community _have_ been very unfriendly, negative, and aggressive (calling C programmers C-niles, etc) and some even going so far as trying to get C outlawed (not making this up). The pushback they're now receiving from Fil-C and Zig is very much deserved. And everybody wins: We are actually getting memory safe systems languages, which is what we all want.

Honestly seems fine. People should be free to push and advocate for what they believe in. Let them argue for it, while maintaining decorum, and see if the argument holds. Part of it is to not get personally offended or attack anyone personally. I can think someone is wrong for choosing C without thinking they are a bad human being. I can also accept people disliking my design choices or disagreeing with my tech opinions without taking personal offense.

@msimoni I don't know what you are talking about, so I can't comment on it.

@carllerche I don't think there's ever been a language some of whose proponents tried to outlaw the competition.

@glcst Link for those who aren't familiar with it: github.com/tokio-rs/toast…

If you are using Turso in Rust, you will love the pairing with Toasty by @carllerche and the Tokio team.

@charliermarsh There is a TUI?

@zeeg Forking and maintaining *is* open source. This also is the result of the constant flood of OSS maintainers claiming they don't want AI bugs/PRs, that they are overloaded, that users should pay them, etc...

Open Source has gotten super weird. Some folks still treat it like it always has been, but a growing trend I'm seeing is people simply forking repos and maintaining the fork. Mixed feelings. On one hand its great - keep your own goals private - but for sufficiently complex projects it poses the threat that the upstream (and downstream!) projects are underinvested in.

@glcst @theo Which sci-fi novel or book correctly predicted this future? That AI would be bringing us an abundance of content like this?

crazy to see @theo on the streets like that.

The algorithm really wants me to watch videos of robots folding clothes.

@glcst I mean, I think I'm clueless. I just power through😅

Almost every single time I released something in my career, I see people saying: you are clueless. You don't understand the space. You don't know what I am doing. In the early days of the Turso Cloud, there was this guy here that would every now and they remark that "Turso keeps building the wrong thing", always followed by an explanation of what SQLite *IS*, what is good at, what is not good at, how people use it, etc. Turso now has almost one signup every 5 minutes, and 700,000 databases were created in our cloud this week. On the rewrite of SQLite itself, the common accusation was that we didn't understand that people use SQLite because of its reliability, and any rewrite would fail because it had no access to their test suite. We took Turso out of beta last week and power many production users already. Before that, it was Scylla, a rewrite of Cassandra. We were roasted by many, who said that we were morons who didn't understand that Cassandra was I/O bound, so any improvements in the CPU architecture were pointless. Scylla was 10x faster than Cassandra in real life. My first experience of that was when at Red Hat we patched QEMU to be the virtualization layer for the device abstraction for the KVM Hypervisor. I was 19 at the time, and being part of the team I submitted a talk to a local conference, who rejected me saying that QEMU was an emulator, and I didn't even seen to understand the different between virtualization and emulation if I was conflating the two. The common thread in all of those is always the same: people getting dead set in their ways, always looking at the world as it is, completely unable to understand that if you just tweak things, most things can be very adaptable. Things can reach new heights. They can be used in different ways.

@nother_pleb @HSVSphere DM me here or on Discord. I can give you access (discord.gg/tokio). tl;dr is it uses exclusively server-side rendering, reactivity added HTMX/Datastar style. There is no Rust running in the browser.

@carllerche @HSVSphere I'm curious on your approach, looking forward to try it

Great video as always. Sad that the stack you picked might be outdated soon for building full stack app with Rust... 🤫

@nother_pleb @HSVSphere Axum is the best option for building HTTP endpoints in Rust. What I'm working on is something for a more full stack experience that removes as much boilerplate as possible.

@HSVSphere @carllerche He's working on a fullstack framework (it may use axum idk) x.com/i/status/20771…