Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

I thought Rust was supposed to replace C and C++, not Java and Scala. But xAI's new x-algorithm repo tells a different story... and Rust is only a part of it.

ForrestPKnight's profile picture

Forrest Knight

18,344 subscribers

175,171 görüntüleme • 9 ay önce •via X (Twitter)

Bilim & Teknoloji
LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

Brian Kernighan: Rust is "a pain" The C and UNIX legend says the Rust programming language is "incomprehensibly big and slow", "I don't think it's gonna replace C". Bonus: What Kernighan thinks of NixOS.
5:35

Brian Kernighan: Rust is "a pain" The C and UNIX legend says the Rust programming language is "incomprehensibly big and slow", "I don't think it's gonna replace C". Bonus: What Kernighan thinks of NixOS.

The Lunduke Journal

10,945 görüntüleme • 1 yıl önce

Let's compare tagged unions in Rust and in C, and then steal some of that type safety from Rust with a bit of a compiler and macro magic so that C can have nice things too!
21:09

Let's compare tagged unions in Rust and in C, and then steal some of that type safety from Rust with a bit of a compiler and macro magic so that C can have nice things too!

Valentin Ignatev

18,657 görüntüleme • 7 ay önce

lol no I'm sorry but your file search is s̶h̶i̶t̶ not optimal consider fff you can literally just use it there is a C lib, Rust crate, and even nodejs lib
0:27

lol no I'm sorry but your file search is s̶h̶i̶t̶ not optimal consider fff you can literally just use it there is a C lib, Rust crate, and even nodejs lib

Dmitriy Kovalenko

91,015 görüntüleme • 7 ay önce

There is a new holding building plan animation on Staging Branch. I thought we had one before but no it only showed you holding it to others not in first person view. #Rust
0:20

There is a new holding building plan animation on Staging Branch. I thought we had one before but no it only showed you holding it to others not in first person view. #Rust

Protox

21,615 görüntüleme • 1 yıl önce

Grok Code Fast 1 is versatile across the full stack and is particularly strong at TypeScript, Python, Java, Rust, C++, and Go. Using Grok Code Fast 1, Danny Limanseta built the following game in a day.
0:58

Grok Code Fast 1 is versatile across the full stack and is particularly strong at TypeScript, Python, Java, Rust, C++, and Go. Using Grok Code Fast 1, Danny Limanseta built the following game in a day.

SpaceX Super Intelligence

1,076,310 görüntüleme • 1 yıl önce

Why Rust hello world is 200 times bigger than C hello world, and why it actually isn't
8:50

Why Rust hello world is 200 times bigger than C hello world, and why it actually isn't

Valentin Ignatev

133,732 görüntüleme • 11 ay önce

.strellic and I did a full 1:1 file-by-file port of Minecraft from Java to Rust both the server and client are ported -- there are some perf bugs but it does appear to work!
1:06

.strellic and I did a full 1:1 file-by-file port of Minecraft from Java to Rust both the server and client are ported -- there are some perf bugs but it does appear to work!

nikhil

289,613 görüntüleme • 27 gün önce

Why is Rust different than many/most programming languages? Alice Ryhl works on Google's Android Rust team, is a Rust language team advisor, and is a core maintainer of Tokio (the most widely-used async runtime in Rust) Timestamps: 00:00 Intro 04:09 Tokio: an overview 05:11 What Alice likes about Rust 12:48 Rust for TypeScript engineers 13:51 Moving from C++ to Rust 14:34 Memory safety 18:12 Garbage collection tradeoffs 21:46 Ownership, references, and borrowing 26:59 Unsafe in Rust 31:21 Crates and Cargo 35:55 Language design and RFCs 43:02 Building new features 46:30 Editions vs. versions 49:47 Getting paid to work on Rust 51:27 Contributing to Rust 53:03 Rust in the Linux kernel 55:45 AI use cases for Rust 1:01:35 Learning Rust 1:03:54 Book recommendation Brought to you by: • Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages. • Sentry – application monitoring software considered “not bad” by millions of developers Three things worth knowing about Rust: 1. Rust was designed to turn implicit failures into compile errors. Where other languages allow you to forget something, Rust makes an omission into a compilation error for things like null checks, uninitialized variables, or error propagation with the ‘?’ character. If you mess something up, it’s almost certain your program will not compile. If it does, at the very least you should see a lint warning. 2. Refactoring in Rust is safe and easy, thanks to the compiler. Alice: “I change a return type or struct field, then just fix the compiler errors until the compiler stops shouting. And then once I’ve done that, I’ve updated every place I need to update.” Rust’s focus on correctness makes refactoring it more straightforward than dynamically-typed languages and Java-style typed ones are to refactor. 3. “Editions” allow Rust to make breaking changes without ‘breaking’ anyone’s code. Rust editions (2015, 2018, 2021, 2024) can be mixed freely across crates. A library on the 2021 edition works seamlessly with a binary on the 2024 edition. This is how Rust evolves syntax (like adding async/await as keywords) without forcing an ecosystem-wide migration. Thanks a lot, Alice for this great discussion! And for your work on Rust.
1:05:52

Why is Rust different than many/most programming languages? Alice Ryhl works on Google's Android Rust team, is a Rust language team advisor, and is a core maintainer of Tokio (the most widely-used async runtime in Rust) Timestamps: 00:00 Intro 04:09 Tokio: an overview 05:11 What Alice likes about Rust 12:48 Rust for TypeScript engineers 13:51 Moving from C++ to Rust 14:34 Memory safety 18:12 Garbage collection tradeoffs 21:46 Ownership, references, and borrowing 26:59 Unsafe in Rust 31:21 Crates and Cargo 35:55 Language design and RFCs 43:02 Building new features 46:30 Editions vs. versions 49:47 Getting paid to work on Rust 51:27 Contributing to Rust 53:03 Rust in the Linux kernel 55:45 AI use cases for Rust 1:01:35 Learning Rust 1:03:54 Book recommendation Brought to you by: • Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages. • Sentry – application monitoring software considered “not bad” by millions of developers Three things worth knowing about Rust: 1. Rust was designed to turn implicit failures into compile errors. Where other languages allow you to forget something, Rust makes an omission into a compilation error for things like null checks, uninitialized variables, or error propagation with the ‘?’ character. If you mess something up, it’s almost certain your program will not compile. If it does, at the very least you should see a lint warning. 2. Refactoring in Rust is safe and easy, thanks to the compiler. Alice: “I change a return type or struct field, then just fix the compiler errors until the compiler stops shouting. And then once I’ve done that, I’ve updated every place I need to update.” Rust’s focus on correctness makes refactoring it more straightforward than dynamically-typed languages and Java-style typed ones are to refactor. 3. “Editions” allow Rust to make breaking changes without ‘breaking’ anyone’s code. Rust editions (2015, 2018, 2021, 2024) can be mixed freely across crates. A library on the 2021 edition works seamlessly with a binary on the 2024 edition. This is how Rust evolves syntax (like adding async/await as keywords) without forcing an ecosystem-wide migration. Thanks a lot, Alice for this great discussion! And for your work on Rust.

Gergely Orosz

52,449 görüntüleme • 5 ay önce

Here's NeoHtop, a cross-platform system monitor app, ported from Tauri and Rust to Avalonia and Rust. Yes, you read that last part right, Avalonia UI in Rust 👇
0:40

Here's NeoHtop, a cross-platform system monitor app, ported from Tauri and Rust to Avalonia and Rust. Yes, you read that last part right, Avalonia UI in Rust 👇

Marc-André Moreau

20,998 görüntüleme • 2 ay önce

Is Rust the least secure programming language? There was yet *another* massive Rust security failure... and nobody seemed surprised. Most Rust activists simply shrugged at the normalcy of it. Considering the frequency and severity of malicious code being added to the Rust Crates ecosystem... is it the least secure programming language toolchain?
8:11

Is Rust the least secure programming language? There was yet *another* massive Rust security failure... and nobody seemed surprised. Most Rust activists simply shrugged at the normalcy of it. Considering the frequency and severity of malicious code being added to the Rust Crates ecosystem... is it the least secure programming language toolchain?

The Lunduke Journal

18,898 görüntüleme • 2 ay önce

“I didn’t want to be rude and leave anyone out, A lot of us don’t play rust a lot and we’ll lose to these big guys like camsoda” The burnt peanut says the big rust streamers can play but can only use primitive weapons 🤣
0:30

“I didn’t want to be rude and leave anyone out, A lot of us don’t play rust a lot and we’ll lose to these big guys like camsoda” The burnt peanut says the big rust streamers can play but can only use primitive weapons 🤣

The Burnt Peanut Clipped

339,524 görüntüleme • 7 ay önce

Why Rust is overused right now Martin Odersky (Creator of Scala): "Right now, rust is actually overused because a lot of people push Rust for things higher up in the stack Where a garbage collector is fine, but essentially you still want to code without. And that is, for me, a bit an exercise in doing it intellectually just because you can I don't really think there's a big sense in it. If you have the memory for a garbage collector, you should absolutely use one, because it makes a lot of things simpler. So, yes, of course, if given enough brains, I can write code around and I can do that, but why should you? It can be much simpler."
0:35

Why Rust is overused right now Martin Odersky (Creator of Scala): "Right now, rust is actually overused because a lot of people push Rust for things higher up in the stack Where a garbage collector is fine, but essentially you still want to code without. And that is, for me, a bit an exercise in doing it intellectually just because you can I don't really think there's a big sense in it. If you have the memory for a garbage collector, you should absolutely use one, because it makes a lot of things simpler. So, yes, of course, if given enough brains, I can write code around and I can do that, but why should you? It can be much simpler."

Ryan Peterman

216,237 görüntüleme • 2 ay önce

Fil-C is safer than Rust. Happy Halloween
5:09

Fil-C is safer than Rust. Happy Halloween

Filip Jerzy Pizło

155,024 görüntüleme • 1 yıl önce

Microsoft is porting the TS compiler to Go for a massive native speedup – amazing! But why not Rust / C# / etc? Here's Anders Hejlsberg explanation from his Wes Bos interview:
4:13

Microsoft is porting the TS compiler to Go for a massive native speedup – amazing! But why not Rust / C# / etc? Here's Anders Hejlsberg explanation from his Wes Bos interview:

Travis Fischer

584,218 görüntüleme • 1 yıl önce

NEW Siege weapons are coming to RUST! Ballista, Catapult and Battering Ram! #rust #rustnews #rusticated
0:28

NEW Siege weapons are coming to RUST! Ballista, Catapult and Battering Ram! #rust #rustnews #rusticated

Rusticated

44,343 görüntüleme • 2 yıl önce

OH MY F*CKING GOD Minecraft was rewritten from scratch in rust, and every mod you own just died with it this was never about rust being faster. it is about java mods having no door to knock on WHY JAVA MODDING WAS ALWAYS GOING TO HIT A WALL → a java mod does not call an interface. it performs surgery. the loader rewrites the game's own bytecode while it loads, and mixins inject into methods nobody designed to be touched → that is why two mods editing the same method fight each other, and why a single update breaks a hundred of them at once → the ceiling was never the language. it was that the game had no front door, so every mod cut its own hole in the wall WHAT THE REWRITE ACTUALLY CHANGED → horizon is not a loader bolted onto the old game. it is its own program in rust that reads the same worlds and generates the same terrain → mods are rust compiled to webassembly, loaded as sandboxed modules against a real api, instead of being injected into the engine's internals → it ships a mod api, a server api, a shader api and an agent control api, which means the game now has a surface built for something to drive it HOW YOU PROVE A REWRITE IS NOT A LIE → rewriting is the easy half. proving you matched the original is the half nobody wants to do → 281 differential harnesses feed identical input to both games and compare the output subsystem by subsystem, and every subsystem it covers comes back matching → and the giveaway detail: the rust side was made to copy java's floating point behaviour on every platform, because otherwise the terrain generates differently and the whole thing is a different game wearing the same name for fifteen years modding meant editing a running program now there is a door, and somebody built one
0:45

OH MY F*CKING GOD Minecraft was rewritten from scratch in rust, and every mod you own just died with it this was never about rust being faster. it is about java mods having no door to knock on WHY JAVA MODDING WAS ALWAYS GOING TO HIT A WALL → a java mod does not call an interface. it performs surgery. the loader rewrites the game's own bytecode while it loads, and mixins inject into methods nobody designed to be touched → that is why two mods editing the same method fight each other, and why a single update breaks a hundred of them at once → the ceiling was never the language. it was that the game had no front door, so every mod cut its own hole in the wall WHAT THE REWRITE ACTUALLY CHANGED → horizon is not a loader bolted onto the old game. it is its own program in rust that reads the same worlds and generates the same terrain → mods are rust compiled to webassembly, loaded as sandboxed modules against a real api, instead of being injected into the engine's internals → it ships a mod api, a server api, a shader api and an agent control api, which means the game now has a surface built for something to drive it HOW YOU PROVE A REWRITE IS NOT A LIE → rewriting is the easy half. proving you matched the original is the half nobody wants to do → 281 differential harnesses feed identical input to both games and compare the output subsystem by subsystem, and every subsystem it covers comes back matching → and the giveaway detail: the rust side was made to copy java's floating point behaviour on every platform, because otherwise the terrain generates differently and the whole thing is a different game wearing the same name for fifteen years modding meant editing a running program now there is a door, and somebody built one

Roxx

46,232 görüntüleme • 13 gün önce

Here is my Rust Guide for C devs in the age of Vibe Coding
1:19

Here is my Rust Guide for C devs in the age of Vibe Coding

Тsфdiиg

97,566 görüntüleme • 1 yıl önce