Linked by Thom Holwerda on Fri 4th Sep 2015 22:46 UTC
OSNews, Generic OSes

OOSMOS stands for Object-Oriented State Machine Operating System. It is a new type of operating system where the fundamental contextual unit is the object, not the thread as it is in traditional operating systems.

Because there are no threads, there are no thread stacks, so OOSMOS is ideal for use in memory constrained environments where a traditional thread-based operating system is not a viable option.

Thread beginning with comment 617229
To view parent comment, click here.
To read all comments associated with this story, please click here.
jockm
Member since:
2012-12-22

Well the idea is that each "task" is an object that knows how to act on its state and set the next state.

I think the creator is stretching things to say it is completely new. It is of a piece with message oriented and event oriented systems that have been around for a long time.

That being said it is an interesting little system and could be quite useful.

Reply Parent Score: 4

Alfman Member since:
2011-01-28

jockm,

I agree, it seems very similar to asynchronous event oriented code. It takes the state machine concept and makes it explicit.

While I've merely glanced at this project, I'm actually a proponent of the model in general because it avoids concurrency problems and multitasking deadlocks quite nicely. Not to mention threaded code doesn't scale as well as state machine code, which is one of the big motivations for asynchronous programming over multithreaded programming.


Many devs prefer solving problems with sequential tasks rather than building state machines though.

Reply Parent Score: 3

Dano Member since:
2006-01-22

jockm,

I agree, it seems very similar to asynchronous event oriented code. It takes the state machine concept and makes it explicit.

Do you even know what asynchronous and event oriented actually mean? Nothing about this task switcher is asynchronous and the only event described is a kernel tick!

Reply Parent Score: 2