No power? No problem!
Came across this nice story of someone living off of the grid in Scotland while still running a pretty well serviced network. I’d love to see what an equivalent Windows Server based environment would cost in terms of power.
The author makes a good point that what some people chose to view as a disadvantage of open source based systems – that you can choose many different components for an open source system and that you can configure them in a myriad of ways – is, for at least some environments, very much an advantage. I tend to agree. While I like to create homogenous, documented environments for my customers – I do tailor each of those environments to my customers’ requirements – rather than trying to change their processes and workflows to suit the software (an all too common problem which occurs when deploying entirely proprietary systems).
Maven Hello World
I’ve been looking at Maven (2.0) recently as part of my work with the Digital Enterprise Research Institute (DERI) . In the past, most projects I’ve worked on used Apache Ant which works pretty well. Maven is a lot more complex than Ant (see some of its features in What is Maven?) but can be used as a “better Ant” if that’s all you need/want (and it seems like a sensible way to start moving to Maven).
Three things I like about Maven from the start:
- Maven includes support for managing dependencies allowing your project to automatically specify what 3rd party JARs it depends on and automatically downloading those at compile-time rather than requiring other developers to spend time hunting for these applications.
- Maven espouses the idea of convention over configuration for its configuration. This is great, in essence, Maven tries to provide sensible defaults as much as possible so you can use it with the minimum of configuration/effort. If you don’t like these conventions, you can change them, but for the casual user, the effort required to start using the tool is low. This is a great approach, all software should strive to be easy to start using (while catering for the power users by enabling the engine to be tweaked if you want to get your hands dirty under the hood).
- Related to the previous point, it’s remarkably easy to build a new Hello World application (a good smoke test for tools like this). Like
mvn archetype:generate -DarchetypeGroupId=org.apache.maven.archetypes -DarchetypeArtifactId=maven-archetype-webapp -DgroupId=ie.atlanticlinux -DartifactId=HelloWorld
to create a new project and
mvn package
to build a test WAR file which you can just drop into your Tomcat webapps directory and immediately test.
The future of Atlantic Linux
Atlantic Linux was a trading name of Applepie Solutions Ltd until the end of 2008. In January, 2009, Atlantic Linux was relaunched as an independent business. We will continue on our core mission of delivering pragmatic, reliable, expert Linux support and consulting. We continue to work with both the free Debian GNU/Linux and Ubuntu distributions as well as the commercial distributions Red Hat® Enterprise Linux and Novell/SuSE Linux (for which we act as resellers).
Our core mission continues to be helping businesses reduce their overall business costs while improving the effectiveness of their IT infrastructure with smart use of Linux and other open source software technologies.
Categories
Archives
- September 2010
- February 2010
- November 2009
- September 2009
- August 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- November 2007
- September 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- September 2006
- July 2006
- June 2006
- April 2006