Someone needs to mix this together with https://www.derw-lang.com/
Civet: A Superset of TypeScript
31–40 of 237 posts
Re: Civet: A Superset of TypeScript
#32I know this hasn't been updated, and I know it's a fork of CoffeeScript, but https://livescript.net/ has had a lot of the "magic" syntax here for quite a while.
Re: Civet: A Superset of TypeScript
#33Really 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.
Languages like this don't make sense anymore. You can just pick a mature, feature-rich language you like (Rust, Kotlin, Python, probably many more) and transpile to JS.
Re: Civet: A Superset of TypeScript
#34So make sure you introduce this in your company; become the subject expert in it, invite everyone to very cool sessions demonstrating how cool it is, and secure your job until the next rewrite!
Looking at the examples, 1/5th of it looked neat, which probably would be best to submit a proposal for |> to the typescript committee rather than write another alienation.
This is a solution looking for a problem to solve. It introduces an alternative and does so as a superset; which is not only dangerous to existing code bases, but also silly.
Re: Civet: A Superset of TypeScript
#35Am I the only one that really dislikes the syntax choices here?
I feel like there is a specific kind of person that likes all this, and there is very little overlap between those people and the people that choose to use Typescript.
Kinda feels like someone was forced to work in Typescript and really wanted to scratch their own itch.
Re: Civet: A Superset of TypeScript
#36This looks like F#
Re: Civet: A Superset of TypeScript
#37Civet. 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.…
CoffeeScript was not only a great idea but also successful beyond its adoption. It influenced and inspired many features that JavaScript later incorporated, such as arrow functions and destructuring assignments.
Over time, JavaScript evolved to the point where the few quality of life improvements offered by CoffeeScript no longer justified learning an entirely new syntax.
Re: Civet: A Superset of TypeScript
#38This is way less readable than normal TS. For that reason alone I doubt I’d use it.
Re: Civet: A Superset of TypeScript
#39Just dont….
This is seriously triggering my CoffeeScript PTSD.
Re: Civet: A Superset of TypeScript
#40Civet. 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.…
I think everyone mostly agrees that CoffeeScript was a dead end, but I think it drove at lot of innovation at the time. Hopefully Civet can do the same, even if it ends up being another dead end.
What makes Civet more likely to drive that innovation than TC39 proposals themselves?