Comments for Technoetic http://blog.technoetic.com Thu, 21 Aug 2008 04:43:32 +0000 http://wordpress.org/?v=2.0.1 Comment on APM Tooling Survey and XPlanner by Steve http://blog.technoetic.com/2007/01/22/apm-tooling-survey-and-xplanner/#comment-22585 Sat, 17 May 2008 23:45:18 +0000 http://blog.technoetic.com/2007/01/22/apm-tooling-survey-and-xplanner/#comment-22585 I haven't worked on XPlanner for a few years now. You could ask your question on the XPlanner discussion forum at... http://sourceforge.net/forum/forum.php?forum_id=161119 Regards, Steve I haven’t worked on XPlanner for a few years now. You could ask your question on the XPlanner discussion forum at…

http://sourceforge.net/forum/forum.php?forum_id=161119

Regards,

Steve

]]> Comment on APM Tooling Survey and XPlanner by eswar http://blog.technoetic.com/2007/01/22/apm-tooling-survey-and-xplanner/#comment-22396 Fri, 16 May 2008 07:45:42 +0000 http://blog.technoetic.com/2007/01/22/apm-tooling-survey-and-xplanner/#comment-22396 I like XPlanner. However, there is no release beyond the beta? is there a specific reason why it is like that? Is it practically defunct now? I like XPlanner. However, there is no release beyond the beta? is there a specific reason why it is like that? Is it practically defunct now?

]]> Comment on Using JRuby for Java testing? by Evan Light http://blog.technoetic.com/2008/01/09/using-jruby-for-java-testing/#comment-22133 Tue, 13 May 2008 14:50:33 +0000 http://blog.technoetic.com/2008/01/09/using-jruby-for-java-testing/#comment-22133 @paul: With regard to Groovy =~ Ruby and Ruby =~ Groovy, not so. Groovy's metaprogramming API is big on ceremony whereas Ruby's is simple yet immensely powerful. IMO, Ruby's pure-OO nature and metaprogramming capabilities are what set it apart from other languages. @paul: With regard to Groovy =~ Ruby and Ruby =~ Groovy, not so. Groovy’s metaprogramming API is big on ceremony whereas Ruby’s is simple yet immensely powerful. IMO, Ruby’s pure-OO nature and metaprogramming capabilities are what set it apart from other languages.

]]> Comment on XPlanner on Rails Download by Steve http://blog.technoetic.com/2006/09/01/xplanner-on-rails-download/#comment-16251 Thu, 28 Feb 2008 23:51:05 +0000 http://blog.technoetic.com/2006/09/01/xplanner-on-rails-download/#comment-16251 I don't manage or work on the Java implementation of XPlanner any more. Jacques Morels is the project lead now. As always, if someone wants to continue development on an XPlanner on Rails, I'm willing to support that effort. However, I have other projects that are currently using most of my spare time. I don’t manage or work on the Java implementation of XPlanner any more. Jacques Morels is the project lead now.

As always, if someone wants to continue development on an XPlanner on Rails, I’m willing to support that effort. However, I have other projects that are currently using most of my spare time.

]]> Comment on XPlanner on Rails Download by Tiago Franco http://blog.technoetic.com/2006/09/01/xplanner-on-rails-download/#comment-16249 Thu, 28 Feb 2008 23:23:02 +0000 http://blog.technoetic.com/2006/09/01/xplanner-on-rails-download/#comment-16249 Hi, Any progress on this? I like xplanner, isn't getting a release since 2006. Thanks, Tiago Franco Hi,

Any progress on this?

I like xplanner, isn’t getting a release since 2006.

Thanks,
Tiago Franco

]]> Comment on Using JRuby for Java testing? by Paul Davis http://blog.technoetic.com/2008/01/09/using-jruby-for-java-testing/#comment-12899 Thu, 10 Jan 2008 18:45:30 +0000 http://blog.technoetic.com/2008/01/09/using-jruby-for-java-testing/#comment-12899 Really, they are both great for unit testing java. Often, the setup code for jUnit is bigger (more verbose) than the actual tests being performed. To offer comparisons, Groovy may be easier (for someone learning a new language) just because it is so close to java and is backwards compatible with it. On the ruby side, beyond simple unit testing, RSpec is an elegant way to write behavior tests. Probably more elegant than any of the other ways to do it. Groovy and Ruby are so similar that it's hard to try to position one above the other. Really, they are both great for unit testing java. Often, the setup code for jUnit is bigger (more verbose) than the actual tests being performed.

To offer comparisons, Groovy may be easier (for someone learning a new language) just because it is so close to java and is backwards compatible with it.

On the ruby side, beyond simple unit testing, RSpec is an elegant way to write behavior tests. Probably more elegant than any of the other ways to do it.

Groovy and Ruby are so similar that it’s hard to try to position one above the other.

]]> Comment on New Release of Jode Eclipse Plugin by 安阳 http://blog.technoetic.com/2005/08/18/new-release-of-jode-eclipse-plugin/#comment-11409 Tue, 18 Dec 2007 04:58:49 +0000 http://blog.technoetic.com/2005/08/18/new-release-of-jode-eclipse-plugin/#comment-11409 I am Chinese too! It cannot update to version 1.0.5, also the version 1.0.3 cannot work for eclipse version 3.2 I am Chinese too!
It cannot update to version 1.0.5,
also the version 1.0.3 cannot work for eclipse version 3.2

]]> Comment on Do You Write Green Software? by Tim Van Tongeren http://blog.technoetic.com/2007/03/25/green-software/#comment-7752 Tue, 11 Sep 2007 20:00:40 +0000 http://blog.technoetic.com/2007/03/25/green-software/#comment-7752 In a speech by Steve Ballmer, CEO of Microsoft, he said there needs to be a "$100 computer" for people in developing countries (Ricciuti, 2004). Nicholas Negropont, founder and chairman of MIT Media Labs, is developing a sub-$100 laptop (Siddle, 2005). Some are predicting a resurgence of network computers (Cooper, 2004), especially since using thin client machines with no hard drives and storing data on the network, drops power consumption by 80% (Gajjar, 2002). These types of computer would probably run different software than the desktops most Americans buy. Additionally, U.S. customers from many industries have been complaing about software taking more resources and forcing them to upgrade hardware (Gaudin & Nash, 1998). One accounting firm could not buy older versions of an operating system for new PCs, so their entire network was incompatible. The company thought the only solution was a forced upgrade of the operating system. However, by installing software that worked on both old machines and new machines, the company saved money on upgrade fees (McCreesh, 2002). There are people in developing countries who cannot afford new software which uses a lot of memory, disk space, or energy. There are people in the U.S. who do not want to upgrade their hardware to run new versions software. If these trends continue, there will be a movement in the software development industry to develop lean software. Generally, "lean software" refers to the process of using as few resources as possible during software construction, similar to lean manufactuing. However, this "lean software" would be engineered with the intent of consuming fewer resources during operation. Initial development costs may increase, but they would be an investment in lower operating costs over the life of the product. When we started testing web applications, we realized that the platform changed some of the emphasis of the testing. We started looking more at performance, compatibility, and security. The change to lean software could have us testing for different things once again: the software will operate using fewer resources (less disk space, less memory, less electricity), operate on older computers, and operate for a long period of time. Sources Cooper, C. (2004). The second coming of the network computer. CNET News.com. Retrieved from here on Nov 18, 2004. Gajjar, C. (2002). Sustainable software at the summit: Can software go green, free and cost-effective? WSSD News, Aug 2002. Retrieved from here on Nov 12, 2004. Gaudin, S. & Nash, K.S. (1998). Retail user groups tackle "bloatware". Computerworld, Aug 10, 1998. Retrieved from here on Nov 12, 2004. McCreesh, J. (2002). Introducing sustainable computing. Retrieved from here on Nov 12, 2004. Ricciuti, M. (2004). Ballmer: We need a $100 PC. CNET News.com. Retrieved from here on Nov 12, 2004. Siddle, J. (2005). Digital guru floats sub-$100 PC. BBC News. Retrieved from here on Feb 11, 2005. In a speech by Steve Ballmer, CEO of Microsoft, he said there needs to be a “$100 computer” for people in developing countries (Ricciuti, 2004). Nicholas Negropont, founder and chairman of MIT Media Labs, is developing a sub-$100 laptop (Siddle, 2005). Some are predicting a resurgence of network computers (Cooper, 2004), especially since using thin client machines with no hard drives and storing data on the network, drops power consumption by 80% (Gajjar, 2002). These types of computer would probably run different software than the desktops most Americans buy.

Additionally, U.S. customers from many industries have been complaing about software taking more resources and forcing them to upgrade hardware (Gaudin & Nash, 1998). One accounting firm could not buy older versions of an operating system for new PCs, so their entire network was incompatible. The company thought the only solution was a forced upgrade of the operating system. However, by installing software that worked on both old machines and new machines, the company saved money on upgrade fees (McCreesh, 2002).

There are people in developing countries who cannot afford new software which uses a lot of memory, disk space, or energy. There are people in the U.S. who do not want to upgrade their hardware to run new versions software.

If these trends continue, there will be a movement in the software development industry to develop lean software. Generally, “lean software” refers to the process of using as few resources as possible during software construction, similar to lean manufactuing. However, this “lean software” would be engineered with the intent of consuming fewer resources during operation. Initial development costs may increase, but they would be an investment in lower operating costs over the life of the product.

When we started testing web applications, we realized that the platform changed some of the emphasis of the testing. We started looking more at performance, compatibility, and security. The change to lean software could have us testing for different things once again: the software will operate using fewer resources (less disk space, less memory, less electricity), operate on older computers, and operate for a long period of time.

Sources
Cooper, C. (2004). The second coming of the network computer. CNET News.com. Retrieved from here on Nov 18, 2004.
Gajjar, C. (2002). Sustainable software at the summit: Can software go green, free and cost-effective? WSSD News, Aug 2002. Retrieved from here on Nov 12, 2004.

Gaudin, S. & Nash, K.S. (1998). Retail user groups tackle “bloatware”. Computerworld, Aug 10, 1998. Retrieved from here on Nov 12, 2004.

McCreesh, J. (2002). Introducing sustainable computing. Retrieved from here on Nov 12, 2004.

Ricciuti, M. (2004). Ballmer: We need a $100 PC. CNET News.com. Retrieved from here on Nov 12, 2004.

Siddle, J. (2005). Digital guru floats sub-$100 PC. BBC News. Retrieved from here on Feb 11, 2005.

]]> Comment on Do You Write Green Software? by software developer http://blog.technoetic.com/2007/03/25/green-software/#comment-7228 Tue, 28 Aug 2007 14:53:45 +0000 http://blog.technoetic.com/2007/03/25/green-software/#comment-7228 Really interesting idea. I've never heard about it. Really interesting idea. I’ve never heard about it.

]]> Comment on XPlanner on Rails Download by Steve Bate http://blog.technoetic.com/2006/09/01/xplanner-on-rails-download/#comment-7072 Tue, 21 Aug 2007 21:06:29 +0000 http://blog.technoetic.com/2006/09/01/xplanner-on-rails-download/#comment-7072 Hi Joshua, A few people have expressed interest in working on it, but no one has followed through yet (AFAIK). Keep in mind that the prototype uses an somewhat old version of Rails. However, I was only using core features of Rails so I doubt it would difficult to upgrade it to the latest version of the framework. Hi Joshua,

A few people have expressed interest in working on it, but no one has followed through yet (AFAIK). Keep in mind that the prototype uses an somewhat old version of Rails. However, I was only using core features of Rails so I doubt it would difficult to upgrade it to the latest version of the framework.

]]>