TypeScript

Source, the Rust Foundation.

The article explained that Microsoft now classifies Rust as a Tier 1 language, placing it alongside C++, C Sharp, and TypeScript as one of the main languages for internal development.

This status means Microsoft provides full support for using Rust in production, including tooling, platform integration, and compliance with security standards.

A key project, Rusty C underscore Codigin underscore UTC, connects Rust to Microsoft's native Windows compiler backend, MSVC, enabling seamless interoperability with C++ and supporting hybrid Rust slash C++ projects on Windows.

And they talk about like they put it, they embed it in like Microsoft Azure Web something, right? Some product none of us have like, and they're like, well, no one's really using it.

And then what they kind of like, I don't know if they quote figure it out, but they basically hook up with the TypeScript team, right? And someone's building TypeScript.

And I guess that was part of the thing, too.

And they're like, we've got this editor.

And he's like, why don't I just take that editor from you and you keep working on TypeScript? So that was kind of interesting.

But then I guess what they kind of figured out was like, well, why don't we build essentially an application, right? And this is the part that...

you know, they portray it as like a good thing.

So you end up with code that works, but Perhaps for many business users it ends up being too slow or the amount of code that has to be sent across the wire is too high.

So it ends up being not competitive anymore with writing JavaScript or TypeScript or anything else that doesn't add quite so much abstraction to their runtime.

So I really wanted to avoid that and Gleam is a very simple language and It's a very simple language, and the features that it does have can actually be represented on JavaScript quite well.

So for normal flow control and just regular programming, there's almost no runtime.

It's very...

It's, it's pretty TypeScript heavy.

Um, you can use a templating language called Vento, which is really nice.

It's by the same person who makes Loom, uh, Oscar Otero.

editor.

So this is where the bun and TypeScript side comes in, is we have a way to make this, in this case, a very dumb widget, right? This dumb widget that's a circle.

So

the bun part is sort of like you decided to use JSON as a scripting language for creating...

up to...

How many languages do we have? We got C, Rust,

TypeScript, and Lua.

TypeScript and Lua.

And they just recently rewrote to, I don't know what they wrote to, like probably Python or something.

But I'd be curious, like some of those like, if there's no base layer of like garbage collection or base layer of like tools that make sense for an easier experience for the agent that meandered through or like even like someone's talking about like TypeScript.

Now you have like a, what's the effect TS where it's like a next level abstraction on top.

But like what the problem with JavaScript is, well, I don't know the problem with JavaScript.

It didn't have types, but That might have been the hypothesis going into it.

But now, what you get out of TypeScript is this now bloated code.

Because now the agent's meandering between how do you write types for every single thing because we've got this contract.

But languages that have compilers... like you might have a better experience because the compiler has to complete.

You chose Rust all the way back then? What were the big projects in Rust back then?

We actually started with TypeScript for one and a half months.

So we were like, okay, like, you know, VS Code seems to be working pretty fast.

pretty fine with typescript why don't we also did that yeah so we started writing that uh in typescript for a while um and then at like week six we decided to give up because the performance was just like way too slow and then the worst part was that um just like all of our developer friends would like refuse to use a new terminal if they knew that it was built in typescript

Yeah, totally.

And depending on your team size, you're either grabbing JavaScript for speed or, you know, TypeScript to catch errors via static typing before runtime.

OK, so Vite gives us the blueprint and the lumber, but you can't build a house with your bare hands.

Definitely not.