Brian Terlson
@b.trl.sn
Working at Microsoft on TypeSpec, JavaScript, TypeScript, Azure, etc. when I find time between wrangling two tiny children.
We use backticks for escaping keywords like swift does: typespec.io/playground/?... Template literals use 3+ quotes (also like swift I think?)
typespec.io
typespec.io
October 9, 2025 at 3:29 AM
We use backticks for escaping keywords like swift does: typespec.io/playground/?... Template literals use 3+ quotes (also like swift I think?)
Yeah I agree. Just imagining the parser work 😂
October 9, 2025 at 3:22 AM
Yeah I agree. Just imagining the parser work 😂
How sad would you be if there were some sort of sigil for custom "keywords" like :record Foo { }
October 9, 2025 at 3:17 AM
How sad would you be if there were some sort of sigil for custom "keywords" like :record Foo { }
Oh const fields! Yes would be nice.
October 9, 2025 at 3:13 AM
Oh const fields! Yes would be nice.
Yes very embarrassing omission 😭
October 9, 2025 at 3:06 AM
Yes very embarrassing omission 😭
There is! typespec.io/playground/?...
typespec.io
typespec.io
October 9, 2025 at 2:59 AM
There is! typespec.io/playground/?...
You can use jsdoc style comments instead of @doc if you like (tho same restrictions). But if you mean return value of an operation, you might use jsdoc returns as usual, else @returnsDoc. I believe that metadata is attached to the operation.
October 9, 2025 at 2:54 AM
You can use jsdoc style comments instead of @doc if you like (tho same restrictions). But if you mean return value of an operation, you might use jsdoc returns as usual, else @returnsDoc. I believe that metadata is attached to the operation.
We could probably relax the grammar for decorators to allow reserved words, I thought we did that already.
I also want custom keywords! It was in some of my original sketches. I think actually important for swiss army knife DSL langs.
I also want custom keywords! It was in some of my original sketches. I think actually important for swiss army knife DSL langs.
October 9, 2025 at 2:51 AM
We could probably relax the grammar for decorators to allow reserved words, I thought we did that already.
I also want custom keywords! It was in some of my original sketches. I think actually important for swiss army knife DSL langs.
I also want custom keywords! It was in some of my original sketches. I think actually important for swiss army knife DSL langs.
This is so cool! TSP was basically born of a distaste for reading another massive json file, it's kind of a niche 😂
If you have typespec thoughts I'd love to hear them, feel free to reach out directly if you like. Also I wonder if you looked at the new emitter framework?
If you have typespec thoughts I'd love to hear them, feel free to reach out directly if you like. Also I wonder if you looked at the new emitter framework?
October 9, 2025 at 2:31 AM
This is so cool! TSP was basically born of a distaste for reading another massive json file, it's kind of a niche 😂
If you have typespec thoughts I'd love to hear them, feel free to reach out directly if you like. Also I wonder if you looked at the new emitter framework?
If you have typespec thoughts I'd love to hear them, feel free to reach out directly if you like. Also I wonder if you looked at the new emitter framework?
This type isn't super popular but it also isn't widely available. I've seen a lot of cases where 32bits isn't large enough but approx 53 bits is. In such cases today people generally use int64 and pray no precision loss happens in JS. Something like `z.safeint()` might make more people reach for it.
April 12, 2025 at 11:55 PM
This type isn't super popular but it also isn't widely available. I've seen a lot of cases where 32bits isn't large enough but approx 53 bits is. In such cases today people generally use int64 and pray no precision loss happens in JS. Something like `z.safeint()` might make more people reach for it.
Oh is that new Zod 4 behavior? That's not bad. Right now it's `z.number().int().safe()` which isn't super friendly.
The name is somewhat confusing, but doubleint is an integer which fits in the safe range of a double.
The name is somewhat confusing, but doubleint is an integer which fits in the safe range of a double.
April 12, 2025 at 11:52 PM
Oh is that new Zod 4 behavior? That's not bad. Right now it's `z.number().int().safe()` which isn't super friendly.
The name is somewhat confusing, but doubleint is an integer which fits in the safe range of a double.
The name is somewhat confusing, but doubleint is an integer which fits in the safe range of a double.
Nice to see the new number types! Consider adding `doubleint` (OpenAPI Format) or `safeint` (TypeSpec type)? Especially with the JSON Schema conversion throwing by default for int64, this type is super convenient when 32 bits isn't enough but 53 bits is.
April 10, 2025 at 11:00 PM
Nice to see the new number types! Consider adding `doubleint` (OpenAPI Format) or `safeint` (TypeSpec type)? Especially with the JSON Schema conversion throwing by default for int64, this type is super convenient when 32 bits isn't enough but 53 bits is.
I'm confident the rewrite would be much less work if the base library (Alloy) had Go language components, but unfortunately we do not yet. If you are interested you can find the base framework here: github.com/alloy-framew...
March 24, 2025 at 5:21 PM
I'm confident the rewrite would be much less work if the base library (Alloy) had Go language components, but unfortunately we do not yet. If you are interested you can find the base framework here: github.com/alloy-framew...
It's a complete rewrite unfortunately. You can see what it looks like here: github.com/bterlson/tsp...
tsp-mcp/packages/typespec-ts-data-server/src/index.tsx at main · bterlson/tsp-mcp
Contribute to bterlson/tsp-mcp development by creating an account on GitHub.
github.com
March 24, 2025 at 4:48 PM
It's a complete rewrite unfortunately. You can see what it looks like here: github.com/bterlson/tsp...
No plans that I'm aware of.
February 8, 2025 at 1:13 AM
No plans that I'm aware of.
All I'll say is that we have a lot of documentation to update so nobody should be surprised if something falls through the cracks...
February 7, 2025 at 11:18 PM
All I'll say is that we have a lot of documentation to update so nobody should be surprised if something falls through the cracks...
Thanks for the kind words 😁
Regarding direct code generators, we're working on them! Should have both client and server generators in a few languages soon for you to try (or you could even try now depending on your tolerance for roughness, if so let me know).
Regarding direct code generators, we're working on them! Should have both client and server generators in a few languages soon for you to try (or you could even try now depending on your tolerance for roughness, if so let me know).
January 30, 2025 at 10:40 PM
Thanks for the kind words 😁
Regarding direct code generators, we're working on them! Should have both client and server generators in a few languages soon for you to try (or you could even try now depending on your tolerance for roughness, if so let me know).
Regarding direct code generators, we're working on them! Should have both client and server generators in a few languages soon for you to try (or you could even try now depending on your tolerance for roughness, if so let me know).
Also recipes just outright lie about how long things take ("cook onions until caramelized, about 5 minutes") or are wildly unrealistic about tasks which can be done in parallel if you only have two hands.
January 6, 2025 at 6:29 AM
Also recipes just outright lie about how long things take ("cook onions until caramelized, about 5 minutes") or are wildly unrealistic about tasks which can be done in parallel if you only have two hands.
Just spent 3.5 hours on a 1.5 hour recipe, here. Everyone cooks at their own pace, are faster or (more often) slower at certain tasks. I think recipe websites are motivated to make them sound easy so they tend to under-account time.
January 6, 2025 at 6:25 AM
Just spent 3.5 hours on a 1.5 hour recipe, here. Everyone cooks at their own pace, are faster or (more often) slower at certain tasks. I think recipe websites are motivated to make them sound easy so they tend to under-account time.
Sir how do we know you aren't playing steel guitar or the marimba?
December 12, 2024 at 11:43 PM
Sir how do we know you aren't playing steel guitar or the marimba?