InfoQ Homepage Development Content on InfoQ
-
Paul King on the Groovy Ecosystem
Paul King discusses the state of Groovy and its maturing ecosystem which includes IDE support, static analysis tools, testing frameworks and the GPars library for concurrency.
-
What’s Next for jclouds?
Adrian Cole discusses his jclouds project, which is an open source library that helps Java developers get started in the cloud and reuse their Java development skills. Cole also talks about some of the challenges of creating a cloud agnostic library, such as the use of different hypervisors and that various cloud implementations are written in different languages, such as VB, Python, Ruby, etc.
-
Emil Eifrem on Neo4j and Graph Databases
Emil Eifrem explains graph databases, what domains they fit well, and the state of Neo4j. Also: how graph databases stack up against RDBMs.
-
Rich Hickey on Protocols and Clojure 1.3
Rich Hickey explains the ideas behind Clojure 1.2's new polymorphism constructs deftype and protocols. Also: Clojure 1.3 features such as faster arithmetic and future features like Pods.
-
Josh Bloch on Java and Programming
In this interview, Google’s Josh Bloch shares his views on the open-source Java landscape as well as on the future of the Java language, including changes being implemented via Project Coin. Bloch also discusses support for multi-core in programming languages, support for multiple languages on the JVM, Java pain points and the “next big language.”
-
Juergen Hoeller on the Past and Future of Spring
Juergen Hoeller explains the past and future of the Spring framework: how it will make use of Java 7 features like Fork/Join, work with JEE6 and PaaS platforms, and much more.
-
Deep inside Node.js with Ryan Dahl
Node.js aims to abstract the problem of concurrency and allow programmers with little experience to easily create servers that scale into the thousands of connections. This interview with the creator of Node.js, Ryan Dahl goes beyond the basic introductory information and focuses on motivations, internals and real-world issues like debugging, monitoring and scaling in the large.
-
ThoughtWorks’ Jez Humble Delivers on Continuous Delivery
In this interview Jez Humble discusses the concept of continuous delivery, which implies that software should always be production ready throughout its lifecycle. That means that every build could be released into production and run effectively. Continuous delivery involves build and deployment automation, continuous integration, test automation, managing infrastructure and environments and more.
-
Brad Abrams on Google, Spring Tools Integration
In this interview Google tools honcho from Brad Abrams talks about how Google tools integrate with Spring tools to help make Java developers’ lives easier. Abrams discusses Google’s reasons for targeting the popular Spring Framework. He also delves into the integrations between Google App Engine, Google Web Toolkit (GWT) and Speed Tracer with Spring tools such as Roo, STS, Spring Insight and more.
-
Doug Crockford on HTML and Fixing the Web
In this interview, Doug Crockford discusses his views on HTML5, which basically amount to a warning that the technology is not quite ready and poses potential risks is widely adopted too quickly. Crockford also talks about the evolution of JavaScript, which has become his favorite language, and of the ECMAScript 5 standard. In addition, Crockford calls for the eradication of IE6.
-
Brian Marick on Test Maintenance
Brian Marick discusses the difficulties met trying to maintain tests that are vital to a project’s success, and how mocking frameworks can help, providing advice on writing unit and integration tests
-
Laforge and Rocher Discuss the future of Groovy, Grails and Java
In this interview, Graeme Rocher and Guillaume Laforge of SpringSource talk about the present and future of the Grails framework and the Groovy language. Rocher talks about Grails 1.4 and some of its enhancements such as improvements to GORM. And Laforge discusses Groovy 1.8, which features new DSL authoring capabilities, among other things. They look at how Java’s future impacts their projects.
