TypeSpec: A new language for API-centric development
1–10 of 121 posts
Re: TypeSpec: A new language for API-centric development
#2Re: TypeSpec: A new language for API-centric development
#3Re: TypeSpec: A new language for API-centric development
#4Re: TypeSpec: A new language for API-centric development
#5Why create a new language, rather than use an established programming language like Go where you can actually write an implementation too?
Re: TypeSpec: A new language for API-centric development
#6https://en.wikipedia.org/wiki/Web_Services_Description_Langu...
Perhaps it will last longer than WSDL did?
Re: TypeSpec: A new language for API-centric development
#71. People don't want to learn bespoke languages.
2. You have to build all the ecosystem tools for a language (compiler, docs, language-server, IDE integrations, dependency management)
Similar endeavors are WaspLang and DarkLang, which I have yet to see in the wild or (meaningfully) on HN. Better to use an existing language and focus on the value add.
I personally built something with similar value add (source of truth -> all the things). I've been through some of these pain points myself.
https://github.com/hofstadter-io/hof
The idea is CUE + text/template = (not limited to APIs)
Re: TypeSpec: A new language for API-centric development
#8Bespoke languages are a hard sell and incur significant extra effort on the team building this. 1. People don't want to learn bespoke languages. 2. You have to build all the ecosystem tools for a language (compiler, docs, language-server, IDE integrations, dependency management) Similar endeavors are WaspLang and DarkLang, which I have yet to see in the wild or (meaningfully) on HN. Better to use an existing language…