jessenoller.com - Python Threads and the Global Interpreter Lock
http://jessenoller.com/2009/02/01/python-threads-and-the-global-interpreter-lock/

interesting interesting!

oach the problem with what is now the near ubiquitous solution to the concurrency “problem”: Threads, a

more on the python-thread shennanigans. Better than most, but like many, seems to ignore GUI programming. Did webdev eat *everything* else?

Long story short, Rails can now serve multiple requests in more than one ruby threads ( or native threads if you’re on JRuby ) parallelly. Charles Nutter has done a good job of explaining the details here. Should you give a flying fuck ? You totally should if : * You’re using JRuby * You’re bold enough to play around with bleeding edge Neverblock stuff * Your application has a lot of long running processes, which are not heavy on blocking IO ( this would be rare I imagine ) You totally should NOT if : * You’re using Event based mongrel, thin or any of the event based web server in production. Event based servers don’t use Threads, so it just doesn’t matter. * You CBA You may have heard a bunch of hype about how threads make everything 100x faster, this is far from the truth. Don’t believe everything the hype merchants want to sell you, test your application first and see if it helps.

"A 'worker' is a script that will be loaded and executed in the background. Web Workers provide a way to do this seamlessly, for example: new Worker("worker.js") - available in Firefox, Safari and Chrome - "If you're doing any computation with JavaScript you should definitely opt to use Web Workers if they're available"

Computing with JavaScript Web Workers

"Normally in order to achieve any sort of computation using JavaScript you would need to break your jobs up into tiny chunks and split their execution apart using timers. This is both slow and unimpressive ..."

Solving 11 Likely Problems In Your Multithreaded Code

MSDN Library 2008/11 - Joe Duffy

Server-side programs have long had to deal with a fundamentally concurrent programming model, and as multicore processors become more commonplace, client-side programs will have to as well. Along with the addition of concurrency comes the responsibility for ensuring safety. In other words, programs must continue to achieve the same level of robustness and reliability in the face of large amounts of logical concurrency and ever-changing degrees of physical hardware parallelism.

good explanation of Ruby's threads & stack implementation

6s

ruby 1.8 mri assembly threads