Civet: A Superset of TypeScript
civet.dev
Civet: A Superset of TypeScript
1–10 of 237 posts
Re: Civet: A Superset of TypeScript
#2I see a language that compiles to JS. What makes this a superset of Typescript? Are there more types? A more powerful type system?
Re: Civet: A Superset of TypeScript
#3The industry has deemed those languages completely unnecessary when we migrated away from coffeescript.
Syntactic sugar can’t be the only thing that makes a programming language.
Re: Civet: A Superset of TypeScript
#4I see a language that compiles to JS. What makes this a superset of Typescript? Are there more types? A more powerful type system?
The linked page is pretty self explanatory. It’s TS with some extra features, many of which are already proposals for the language. Cool for an experiment, not good for a maintained codebase.
Re: Civet: A Superset of TypeScript
#5That looks interesting but imo the syntax is too terse. Coming from Rust and Golang I very much appreciate the use of sigils and syntax sugar in moderation but especially the pipe operators look like they could lead to hard to debug code very easily.
Re: Civet: A Superset of TypeScript
#6Civet. Kopi luwak coffee. It's CoffeeScript.
I wrote a bunch of CoffeeScript back in the day, and everyone I've spoken to about it feels the same, that it was a bad idea in hindsight, and a language dead end. The language was only syntactic sugar, and by not bringing anything else to the table, was unconvincing for ports and support in other ecosystems. It now seems that most codebases have been decaffeinated though.
Civet looks like it adds a little more, but the things that aren't just syntactic sugar are just a grab bag of TC39 proposals. I'm a big fan of language proposals in general, and having a language that adds all of them for research purposes seems like a nice thing to have. Haskell did this well with GHC language options. Is this a research language though? It seems not.
What's the benefit over Typescript? A few less characters? Faster TC39 proposal integrations? What happens if a proposal is rejected, does it get removed from Civet? What's the cost? What happens as Typescript and Civet diverge? What if the TS tooling doesn't support Civet features?
Re: Civet: A Superset of TypeScript
#7Interesting but not sure how much do I buy it.
I would rather do with a stricter super set of TypeScript with some sugar/conveniences around its many verbose but useful features like branded types.
Re: Civet: A Superset of TypeScript
#8Really redminds me of coffeescript, lots of special syntax that doesn't really help readability?
I have a hard time understanding the motivation of this project other than syntactic sugar-maxxing JS/TS.
Re: Civet: A Superset of TypeScript
#9Civet has so many quality of life improvements! It's good that it exists sort of as a playground for ideas that could maybe in the future be adopted by JS itself, kinda like how it went with CoffeeScript.
Re: Civet: A Superset of TypeScript
#10Am I the only one that really dislikes the syntax choices here?