OOSMOS, the Object Oriented State Machine Operating System, Is Now Open Source

Re:OOSMOS, the Object Oriented State Machine Operating Syste... by merb on Wednesday November 04, 2015 @06:07PM (#10510473)

internally message passing, futures and actors are all about state. especially in erlang and scala. the libraries just wrapping that state so you don't need to care about.

also there is always state. look at the io front there your application needs to deal with state, if you are using fp your program maybe doesn't contain state. but the public api mostly deals with it.

[ Parent | on HN ]

Re:OOSMOS, the Object Oriented State Machine Operating Syste... by eru on Wednesday November 04, 2015 @06:57PM (#10510678)

Functional programming is about carefully managing your state. Ideally, you want to separate the pieces with the complicated logic, from the pieces that do the state persisting. Then each piece can do one thing and do it well.

There are lots of useful stateless services. But that's the nirvana, and not possible with all things you might want to offer.

[ Parent | on HN ]