A problem we’ve been battling over for a while now is whether or not we should discontinue supporting Internet Explorer 6 in our new web applications. Not only does IE6 prove time and again to be buggy and infamously unable to adhere to standards, but it also takes about 20% more time during the development phase of any project for special handling. That time could be much better put to use in other things like code review, testing, and bug solving.

ie6_on_the_chair

 
Tawazi is the Arabic translation for the English word "Parallel". Tawazi is a library written 100% in Ruby. Tawazi provides Ruby developers an easy-to-use, easy-to-extend, high-performing parallel execution frameworks inspired by the theory of Parallel Design Patterns (http://parlab.eecs.berkeley.edu/wiki/patterns/patterns).
 
For years, processor manufactures consistently delivered increases in clock rates and instruction-level parallelism, so that single-threaded code executed faster on newer 
processors with no modification. Now,to manage CPU power dissipation, processor manufacturers favor multi-core chip designs, and software has to be written in amulti-threaded or multi-process manner to take full advantage of the hardware. Handling Parallel processing and concurrency issues every time we write our software has many drawbacks: 
 
1-Not all application developers has deep knowledge about parallel processing and councurrency control. They should focus in solving their application problems instead of dealing with parallel processing problems.
 
2-No code reuse. Every time you will repeat the same "patterns" to solve parallel processing problem.
 
3-A big source for bugs and concurrency mistakes, specially for large and complex systems.
 
4-Poor code clearness and readability. No common language between developers.