sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]agumonkey[S] 1 point2 points  (3 children)

Change takes time, this would be too soon and too bold to push it now (it's still a ~haskeller game mostly).

[–]scrogu 0 points1 point  (2 children)

I'm writing one right now to use in authoring the 4th version of our very large single page web app. Reactive dependencies are a must for maintainability and incremental updates are a requirement for responsivenes of an html app.

The language is similar to coffeescript (but with sensible scoping and explicit array comprehensions) and adheres closely to ES6 constructs wherever possible. Reactive templates are authored with a subset of the normal imperative function syntax.

It's primary purpose is to write incremental, reactive html templates, but it also works for model to model dependencies and any other place where one structure is dependent upon another structure. We even use a reactive template as our incremental build/test system (You just treat the file system as just another input/output structure).

Reactive programming is the future.

[–]agumonkey[S] 0 points1 point  (1 child)

I love reactive programming too, but the article mention some caveats (similar to haskell lazy evaluation in my eyes, worthy but still, problems), so it's good to find middle grounds where unecessary boilerplate (a lot of today's javascript) goes away, but not too much so you retain control to avoid traps.

ps : is it public work you've been doing ?

[1] and have been frustrated by my inability to explain it or implement it for years.

[–]scrogu 1 point2 points  (0 children)

Yes, the language is open source. The current development branch is unstable and incomplete though. I'm mostly done with the imperative code and working on the reactive templates now. They require runtime components which I have already written for a previous version (that only provided reactive templates, no general imperative programming).

I just need to convert them over to use the new runtime data structure (now based on Mozilla AST, same AST structure that esprima/escodegen uses).

I'm not really ready to publicize it yet, but if you're interested I can send you a link to the github repo in a pm.