I agree and I think the ideas in Elm are applicable in many other contexts. Adopting a new language is just hard, especially with larger teams. I ended up taking some of the ideas of Elm but implementing with Rust and TS - https://dave.tonge.org/articles/make-ts-boring/
The basic idea - all application state and view model creation is in Rust (compiled to Wasm). I'm using Rust not really for performance, but for its strong type system. Components are in TS but have a strict contract they can only accept plain input props and output events. Rust processes the events and ships a view model patch to TS.
This is not "Elm in Rust/TS" but it is definitely Elm inspired.
We're a fast growing start-up with a mission to help people better understand, organise and plan their finances. We recently won a best in show award at Finovate Europe and are looking for developers and designers to come on board and join us. (Bristol is often voted best city in the UK and has an amazing tech scene).
We use a JS / Coffee heavy tech stack - Node.JS, Backbone & D3 - but we're pragmatic and will use the best tool for the job.
We're currently looking for a:
* Senior Developer - Strong Backbone & Node skills, experience working with a large but modular codebase. £35k to £50k depending on experience.
* Front End Developer / Designer - UX focussed CSS crafter. Experience with D3 and designing touch based interfaces a plus. £28 to £40k depending on experience.
For more details on us as a company or the roles please send me an email:
dave.tonge at bluespeckfinancial.co.uk
The basic idea - all application state and view model creation is in Rust (compiled to Wasm). I'm using Rust not really for performance, but for its strong type system. Components are in TS but have a strict contract they can only accept plain input props and output events. Rust processes the events and ships a view model patch to TS.
This is not "Elm in Rust/TS" but it is definitely Elm inspired.