Koree Monteloyola

"This is why you should support Android (not Google, but Android), even if you prefer the iPhone. This is why you should support Linux, even if you use Windows. This is why you should support Apache, even if you run IIS. There's going to be a point where being Free/open is no longer a fun perk, but a necessity."

- quoted from Richard Stallman Was Right All Along

I agree and like to think that there is freedom in free software, and money in proprietary software and/or developing for someone else. So where does this put a PHP web developer, like me?

Honestly, even if I really love the idea that I can spend most of my waking days building free software and experiment with solar power, in reality I have bills to pay. So I have to balance this out and if I'm lucky I can build my own platform, with that being said, I need to learn a new programming language this year.

Although the two terms are used interchangeably nowadays, the difference lies on the design of the programs that triggers the processes - how frequent can it be interrupted to give way to another process.

In multiprogramming a list of programs are queued and switches programs from active to passive states. If the program turns into a passive state another program would be considered active.

Whereas in multi-tasking, it eliminates this condition - it tries to pause/stop the currently running process instantly regardless of the state and executes another process instantly.