Civet: A Superset of TypeScript

Post by brianshaler » Tue, Oct 22, 2024, 2:51 PM UTC

dgoldstein0 wrote: post #49

danpalmer wrote: post #43

Earlier quoted context omitted.

> CoffeeScript made writing and reading things much easier My point is that it kinda didn't. It looked prettier on the surface, but didn't actually solve any of the deeper problems of writing JavaScript. To write CoffeeScript you had to still know JavaScript and all its oddities. TypeScript solved those problems, and that's why it has taken off and had a meteoric rise to the point that it's practically synonymous wit…

Coffeescript had some great features: classes, array comprehensions, default parameter values, arrow functions, optional chaining. Many of these eventually made it to ecmascript. And then it ruined us with implicit returns, optional parentheses and brackets, and the isnt vs is not fiasco. I worked a lot with Python and coffeescript at the same time back in the day. In Python you mess up your whitespace and 95% of the…

Post by wruza » Tue, Oct 22, 2024, 3:13 PM UTC

progx wrote: post #108

vivzkestrel wrote: post #86

Its not about how concise or short your code looks, its how about much time the new intern coming tomorrow needs to understand those 1000 line files. I find the syntax very hard to remember and confusing

And in times of Copilot & others writing become less and less a problem, as code completion works very well. Like this example: https://civet.dev/#everything-is-an-expression `items = for item of items`, in js you type `for`and copilot wrote nearly the full correct for-code. So you have to type not much and can read it easy.

  foro
    for ($1 of $2) {
      $0
    }

  touc
    toUpperCase()

  le
    length

  map
    map(x => $0)

Post by recursive » Tue, Oct 22, 2024, 3:47 PM UTC

edemaine wrote: post #65

recursive wrote: post #59

Earlier quoted context omitted.

JSX has a spec. This thing they're doing... I don't know what it is, but it ain't JSX.

The JSX spec hasn't changed for almost 10 years, and I'd guess there will never be a JSX 2.0. On the other hand, ideas for a better JSX are plentiful (check out the issues on the JSX repo, for example). If the spec never changes, how can we improve the JSX experience? Transpilation! Civet's futuristic JSX compiles to actual spec-compliant JSX, to it's compatible with all forms of JSX, including React, Solid, etc. We'…

Post by nsonha » Tue, Oct 22, 2024, 3:58 PM UTC

edemaine wrote: post #58

koolba wrote: post #41

What does this do? operator {min, max} := Math value min ceiling max floor Is that a declaration or an invocation?

It's doing a few things at once: First line: * `{min, max} := Math` is a destructuring declaration. It's similar to the destructuring assignment `{min, max} = Math` (i.e., `min = Math.min; max = Math.max`), but also declares min and max as const. * The `operator` prefix means to treat min and max as new infix operators in the rest of the program. Second line: Given that min and max are infix operators, `value min cei…

Post by azemetre » Tue, Oct 22, 2024, 4:03 PM UTC

wruza wrote: post #174

progx wrote: post #108

Earlier quoted context omitted.

And in times of Copilot & others writing become less and less a problem, as code completion works very well. Like this example: https://civet.dev/#everything-is-an-expression `items = for item of items`, in js you type `for`and copilot wrote nearly the full correct for-code. So you have to type not much and can read it easy.

I think it’s time to reveal the shocking ancient knowledge people weren’t ready to deal with before: textmate snippets. foro for ($1 of $2) { $0 } touc toUpperCase() le length map map(x => $0) And so on. Seriously, typing code is some '90s activity since forever. Using copilot for this is akin to hitting a nail with a microscope.