technuflections(@bricoi1) 's Twitter Profile Photo

Rich Harris endpoints, protocol, workflows, etc. are first-class concepts. Jolie enable implementing microservices and deployment patterns in a fraction of the time that with a GSL and with a short distance between specs and implementation. cf. infoq.com/news/2021/05/j…

account_circle
technuflections(@bricoi1) 's Twitter Profile Photo

Artem Zakharchenko Types != TypeScript. also, TypeScript is both a type system and a set of tools. Benefits of types are clear. It is the cost of using TypeScript that varies according to teams and projects. As usual, no fast rule in either direction. Sometimes it will not be worth the hassle.

account_circle
technuflections(@bricoi1) 's Twitter Profile Photo

Rich Harris involved in a web application specification, implementation, testing, and deployment first-class, that will be better than alternative choices. Think routes, APIs, user scenario, data objects, etc. all first-class. Good example is Jolie a micro-service DSL where service, 3/

account_circle
Konstantin Münster(@kmuenster) 's Twitter Profile Photo

technuflections There is a short vanilla JS introduction: lexical.dev/docs/getting-s…

This should be a starting point. But there are indeed no helper packages for other libraries like Svelte etc.

account_circle
Pier(@pierbover) 's Twitter Profile Photo

technuflections Matthew Phillips Imba is over 10 years old IIRC. It doesn't take a page from Svelte :)

I don't think Rich Harris knew about it when starting Svelte.

Also, it doesn't do surgical DOM updates. It re-renders everything but with a memoization technique.

twitter.com/pierbover/stat…

account_circle
Pier(@pierbover) 's Twitter Profile Photo

technuflections Matthew Phillips Rich Harris I guess most people these days associate a compiler with Svelte but it's not really a novel approach.

Marko did it years before or stuff like CoffeeScript.

account_circle
Magne(@magnemg) 's Twitter Profile Photo

technuflections Gary Bernhardt David K 🎹 I think Effect | TypeScript at Scale could be uniquely positioned to create a Modular Monolith which could transition to a distributed system with the most minimal amount of refactoring. Since it treats sync and async effects the same.

account_circle
Asher Cohen 🤖🤳(@code_tank_dev) 's Twitter Profile Photo

Magne technuflections Gary Bernhardt David K 🎹 Effect | TypeScript at Scale The fact that appeals to me the most in both Effect | TypeScript at Scale and Stately.ai is the model-first -> implement later approach.
Having a generic model (split into modules that interact with eachother) independent from the implementation is core to a distributed system.

account_circle
Fraser(@fraser_drops) 's Twitter Profile Photo

technuflections Cycle.js is definitely something I've looked at, without deeply understanding it all. But my general impression of stream based approaches, which are definitely in the same problem space as eventcharts, is that branching logic is very difficult to follow

account_circle