Carl Lerche

@tursodatabase Is Toasty good? This was just posted to Discord: "how you designed the relations with Deferred for everything then a nested Option or Vec etc... is amazing! It's very intuitive and works perfectly. Simply dropping Deferred to make the field always included is really simple"

A big Toasty release (async ORM for Rust)! The relation declaration API improved, added support for multi-step relations, update! macro with ops like increment / add / push, and support for @tursodatabase. github.com/tokio-rs/toast…

@theojaffee Because they didn't want to get bumped into the next tax bracket. They would have gotten less money if they did that.

Why didn't Anthropic just price their round at $1T for aura farming purposes?

@DavidSherret @rough__sea Very nice!

@carllerche @rough__sea Yeah, the builds were already published as github action assets for use in the test jobs.

great for people submitting changes to deno

I've never seen CLI tools let you upgrade to a build based on a PR before. That is pretty clever and I will have to remember it for the future. Really slick.

@MrJayLC #[repr(C)] is not unsafe. It has no impact on safety. It sounds like you have no idea how Rust works.

@carllerche now you're trading unsafe territory, my guy. :^)

I guess all this time I thought I was starting from "what do I want the CPU to do" while writing Rust, it was just a lie?

@MrJayLC #[repr(C)] is inconvenient?

@carllerche You give way right here. I say "machine alignment", as in how close the language can mirror the underlying architecture with minimal sacrifices in convenience. You went right for the Rust:tm: safetyism of memory. The dabbling is just bandwagon and propaganda.

@LegNeato @Leik0w0 @vectorware Looking forward to it!

@Leik0w0 @carllerche @vectorware Yep, that was me. Blog post soon(ish). We have two pillars, bringing CPU code to the GPU and writing advanced GPU-native code from scratch. Both relevant to your interests 😎

@nevgeniev @penberg You could make that argument, I would argue that it what rust does is fine for 99% case and there are libs for explicit allocs in collections, but that has nothing to do with the borrow checker or traits, or rust as a language.

@penberg @carllerche Ok. Flame mode on :). To me the main difference between these two languages is CARELESS allocs in rust vs fine grained allocs in zig. Talk me out :)

@MrJayLC My lord. Do you have any idea what is being written in Rust? I align my memory with ease when I need to. You think the Linux kernel would be adopting Rust if it were hard?

@carllerche If committees, marketers and decision makers get to make the choices, yes. Rust has (had?) branding, the "safetyism". But it turns out it's not that useful, and the most dangerous things are not about memory. Machine alignment is more important.

@thrawn01 I think Zig is great and there should be more programming languages in general.

@thrawn01 I think you didn’t read anything I said if you think I made a comment about Zig. I commented that it is none sense to try to claim that the language being adopted for infrastructure and OS kernels pushes you away from writing for the hardware.

@wongmjane Oh yea! It's been too long since I've been there.

@carllerche Lovely’s Fifty Fifty!

guys i feel like i’m not blending in well in portland :((

@penberg Someone should warn those kernel developers using Rust that they aren't thinking about the hardware.

@penberg It's why everyone is writing infrastructure with Rust. Because it forces you away from thinking about the CPU.

I mean.. how does he say that with a straight face when Rust adoption is growing at the OS kernel level? You think Rust would be used in the Linux & Windows kernels if it forced you away from the hardware?

Or as Bjarne Stroustrup says, writing safe C++ is easy, just don't do anything wrong (paraphrasing).

@RaykiruS You can just say "I don't like Rust". Totally legit. There is a reason Rust adoption is growing at the infrastructure level, including OS kernels. It isn't because it forces you away from the CPU. I don't think it would be used in Linux/Windows kernels if it did.

@carllerche As for the compiler translation point, rust is simply language leaning heavely into declarative code whereas zig leans more towards procedural: in declarative you write <what>, in procedural you write <how>. Is the difference between these 2 paradigms non-existant?

@RaykiruS You know that you don't have to write that, right? Not to mention, the *exact* same argument can be made with any language. You think any modern compiler emits asm that resembles anything you write? Only write ASM if you want to be close to the hardware at all times.

@carllerche ... the CPU know what lifetimes are? What ownership is? Bottom line is, with rust you don't tell the CPU what to do, you tell the compiler what result you want and it decided what to tell the CPU