Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

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:

583,816 Aufrufe • vor 1 Jahr •via X (Twitter)

8 Kommentare

Profilbild von Travis Fischer
Travis Fischervor 1 Jahr

More details on the decision to port to Go: Michigan TS discussion w/ Anders Hejlsberg: GitHub discussion: Seems to make a lot of sense to me, aside from WASM being less interoperable w/ Go... thoughts?

Profilbild von AndaSeat
AndaSeatvor 1 Jahr

⌨️ 2AM debugging session: Your code won't compile, Stack Overflow is your best friend, and your Kaiser 4 is the only one who understands... Every developer's late-night reality: 💻 "One more bug fix" turned into sunrise ☕ Coffee cup collection growing 🐛 That bug that just won't die Kaiser 4 speaks fluent Python: 🌟 4D lumbar support for those debugging postures ✨ Perfect height for multiple monitors 💫 Recline mode for code compilation breaks Because good code comes from comfortable devs! ⚡️ Debug in comfort: #AndaSeat #DevLife #CodingLife #ProgrammerSetup #gaming #gamingchair

Profilbild von Just in Time
Just in Timevor 1 Jahr

@ahejlsberg @wesbos Sounds like a skill issue for me.

Profilbild von Scott Tolinski - Syntax.fm
Scott Tolinski - Syntax.fmvor 1 Jahr

@ahejlsberg @wesbos Full interview here. Typescript Just Got 10x Faster

Profilbild von Cody Mullins
Cody Mullinsvor 1 Jahr

@ahejlsberg @wesbos @grok summarize this video

Profilbild von Jonathan L Clark
Jonathan L Clarkvor 1 Jahr

@ahejlsberg @wesbos It was the natural direction for them to "Go".

Profilbild von Emeka Orji
Emeka Orjivor 1 Jahr

@ahejlsberg @wesbos literally had a convo about RustScript (hypothetical) yesterday

Profilbild von Ganesh
Ganeshvor 1 Jahr

@ahejlsberg @wesbos I would have preferred swift over Go. Go is this midage cult who resist changes.

Ähnliche Videos

Anders Hejlsberg (Anders Hejlsberg) is a living legend: he created Turbo Pascal, Delphi, C# and TypeScript (and today TypeScript is the most-used programming language, globally, as per GitHub.) Timestamps: 00:00 Intro 02:48 How Anders got into programming 05:40 Building his first compiler 07:44 Turbo Pascal 12:25 Delphi 14:53 Joining Microsoft 19:41 Building C# 29:11 Async/await 34:01 The rise of JavaScript 37:52 Building TypeScript 42:58 How the TypeScript compiler works 48:30 JavaScript’s strengths and weaknesses 52:18 How Anders uses AI 56:03 What language features work well with AI 1:02:49 How software craftsmanship is changing 1:07:49 Performance and efficiency 1:09:29 Anders’ tool stack 1:11:30 A 30-year career at Microsoft 1:13:40 Book recommendation Brought to you by: Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages. WorkOS – Everything you need to make your app enterprise ready. turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable. Four things that stood out to me: 1. “10x better for 1/10th of the price” is a proven winner. This is what Turbo Pascal did: it sold for $49.95 when competing compilers cost $500, and it was faster and more interactive than competitors’ products. Conveniently, the low price tag also killed off piracy 2. C# might have not existed without a famous court case. Microsoft originally hired Anders to architect its Java tools (Visual J++), but the Sun versus Microsoft lawsuit (1997-2001) meant Microsoft could not build on top of Java, as the company that owned Java’s IP (Sun) sued MS for alleged unauthorized changes to the Java language. Microsoft realized it had to build a new language that combined VB’s productivity with C++’s power. This led to C# and .NET. 3. TypeScript exists because Anders refused to build Script# for the Outlook .com team. Microsoft’s Outlook .com team asked Anders’ C# team to productize “ScriptSharp,” a language to cross-compile C# to JavaScript. Anders and the C# team pushed back, suggesting that a better approach was to fix JavaScript. Anders felt strongly that to be attractive to the best-of-breed developers in the JavaScript ecosystem, you want people to write JavaScript, and not another language like C#. 4. Designing a programming language is a 10-year play. As Anders puts it: “Version one is great, but has all sorts of issues. You’ve got to do version two, but it’s not until version three that it really starts to be great. Then you’ve got to convince people to adopt it.”

Gergely Orosz

129,032 Aufrufe • vor 2 Monaten

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

51,575 Aufrufe • vor 1 Monat