Using Ruby Fibers for Async I/O: NeverBlock and Revactor
Ruby 1.9's Fibers and non-blocking I/O are getting more attention - we talked to Mohammad A. Ali of the NeverBlock project and Tony Arcieri of the Revactor project.
Tracking change and innovation in the enterprise software development community
Posted by Jonathan Allen on Jan 08, 2008 06:42 AM
PHP, one of the cornerstones of LAMP stack, is used by major websites such as Wikipedia. Designed as a server-side language, it normally has to be paired with JavaScript or Flash/ActionScript to build rich Internet applications.
Silverlight, like the rest of the Common Language Runtime, is in theory language-agnostic. In the past it has posed some problems for dynamic languages, which lead to the development of the Dynamic Language Runtime or DLR. The DLR provides a unified object model for dynamic languages and the ability to host just-in-time compilers needed for so-called scripting languages.
Tomas Petricek is leveraging Silverlight and the DLR to allow PHP developers to use their current skill set and libraries on the client. The core of this setup is two files, PhpNetCore.dll and PhpNetClassLibrary.dll. The first is a PHP compiler for .NET, the latter a collection of common PHP functions. When referenced from an XAML file, they allow PHPX files to be loaded and run from within Silverlight.
Because everything is done client-side, there should be no reason why Linux-based web servers that PHP developers prefer cannot be used to host the Silverlight applications.
You can learn more about Silverlight/PHP integration on Tomas Petricek's blog.
IBM software architect eKit: Grady Booch podcast, whitepapers, articles
Gamma's Jazz platform's first implementation: Rational Team Concert (Trial Download)
Alternatives in the .NET Space: Open Source, Frameworks and Languages @ QCon SF Nov 19-21
The Agile Business Analyst: Skills and Techniques needed for Agile
Ruby 1.9's Fibers and non-blocking I/O are getting more attention - we talked to Mohammad A. Ali of the NeverBlock project and Tony Arcieri of the Revactor project.
Tim Mackinnon talks about the aspirations behind the Agile principles and practices, the desire to become efficient, to write quality code which does not end up being thrown away.
Brian Goetz discusses the difficulties of creating multithreaded programs correctly, incorrect synchronization, race conditions, deadlock, STM, concurrency, alternatives to threads, Erlang, Scala.
Often the hardest part of changing technologies is language syntax differences. This new article provides Java developers with a transition guide to Actionscript which forms the foundation of Flex.
Neal Ford talks about having multiple languages running on one of the two major platforms: Java and .NET. He also presents the advantages offered by Ruby compared to static languages like Java or C#.
David Anderson talks about the history of Agile, the current status of it and his vision for the future. The role of Agile consists in finding ways to implement its principles.
Nick Sieger talks about the future of JRuby, Java Integration, and his work on JEE deployment tools for Ruby on Rails like Warbler.
Rustan Leino and Mike Barnett of Microsoft Research discuss the technology in Spec# and its futures.
No comments
Reply