The spirit of innovation we brought earlier on lives again, this time with a modular design and efficiency from Day 1.
Functional Reactive programs are probably the best way for web programming, due to its async nature:
https://t.co/SljTtuOC7h
is the first π§± 2/2
2/2
Almost 15 years ago, we brought new ideas to web programming:
- strong static typing
- the JSX syntax π
- automatic code split between client and server
- database automation
However, we missed a few things, namely lack of modularity and an inefficient implementation ... 1/2
@amasad@paulg Oh yes! For @opalang we wasted a lot of time implementing a clever HM(X) constraint-based type system. Error messages were horrible, among many other problems. We ended up rewriting the typechecker as a monolithic W algorithm.
@pcarrier@jolon And thatβs the typical modern single-page app which is taking over the classical server-side rendering. You will need a server for many things (database, ...) and the first tweet was to discuss about coming back to simpler server-side HTML.
@pcarrier@jolon Itβs indeed more complex to maintain client runtime in the server. The original Opa approach is to « sliceΒ Β» code between client and server automatically. Many parts become HTML generated server-side.
@svensauleau@quentin_smr@jordwalke@andpoul Here! https://t.co/kShBGWWM7X
Opa is a cousin language of ours. It pioneers many ideas that could hit mainstream js one day. Check it out!