InfoQ Homepage QCon Software Development Conference Content on InfoQ
-
Adam Wiggins on Heroku
Heroku's Adam Wiggins talks about how Heroku, Add-Ons, Ruby, and how Heroku manages to work around Ruby's inefficiencies using Erlang and other languages.
-
Don Box Discusses SOAP, XML, REST and M
In this interview from QCon San Francisco 2009, Don Box discusses the history of SOAP, XML, XML Schema, RELAX NG, SOAP and WSDL, REPL, opinions on REST, REST at Microsoft, coexistence of REST and WS-*, the M programming language, M and DSLs, M versus XML/XML Schema, Data as XML, and future plans for M and data modeling at Microsoft.
-
Ruby Creator Yukihiro "Matz" about Ruby, Functional Programming and Programming Languages Design
In this interview, Yukihiro Matsumoto talks about programming languages design and decisions he had to take while designing Ruby. He also discusses other programming languages including Haskell, Scala, Python and Clojure. While talking about Ruby language and functional programming, Matz explores opportunities of integrating some of FP into Ruby and imagines a purer IO approach for it.
-
Michael Nygard on Building Resilient Systems
Michael Nygard on: feature complete vs. production ready, how to make a system more resilient and monitorable, explaining stability patterns like Bulkhead and Circuit Breaker, and the need for the development department to cooperate with the operations one and the business managers.
-
Ric Smith on the Present and the Future of HTML 5
Ric Smith is an advocate of HTML 5, considering that browser vendors will incorporate more and more features of the emerging standard, driving its adoption. Ric details some of the features already implemented, Web Sockets, server events, focusing on the difference between plug-in solutions and HTML 5 ones.
-
Patrick Curran and Geir Magnusson on the Standardization Process
Patrick Curran and Geir Magnusson discuss the role played by the standardization process and the lessons taken from the open source movement, one key aspect being related to reference implementations that are required from spec leaders.
-
Cameron Purdy on Scaling Out Data Grids
What is Data Grid computing? What makes it different from a database? Is a data grid always scalable? Is the cloud the next step? Cameron Purdy answered these questions and others during an InfoQ interview, and also gave some hints on how to build scalable grids and how to avoid horror stories.
-
Michael Feathers on Programming Languages
In this interview with Sadek Drobi, Michael Feathers explores working with legacy code, working with different programming languages, the right scope/size of modules, and the importance of readability of code regardless of the programming language.
-
Dion Hinchcliffe on Web 2.0 and Web Oriented Architecture
Dion Hinchcliffe is an advocate of Web 2.0 and the Web Oriented Architecture. He explains how a mindset shift helped some companies be very successful using the Web 2.0 model while others have failed. He also considers that eventually most companies will migrate to WOA because we are living in an increasingly networked world.
-
Neil Bartlett on OSGi
This interview, conducted at QCon 2009, covers a wide range of topics beginning with a definition of OSGi and ending with an audience question about integrating OSGi into legacy application servers (like Websphere). In between Neil answers questions about the origins and evolution of OSGi, how OSGi compares to .Net modularization, and constraints on the use of certain Java libraries.
-
A Conversation with Sr. Tony Hoare
Sir Tony Hoare answers questions about his background, his relationship with Microsoft Research, his interest in "Unifying Theories of Programming," and numerous other topics in the area of programming, correctness, formal analysis of programs, and even type systems. Also addressed: concurrency, null-references, and even buffer overflows.
-
David Pollak On Lift Framework and Scala
David Pollak talks about using Scala to write the Lift web development framework and his desire to write a productive framework that allows the developer to write concise code on top of a very strongly typed language.
