This entry was posted
on Wednesday, January 7th, 2009 at 10:01 pm and is filed under General.
You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.
Well, your answer was pretty funny alright. But as you can read in the other answers, there are also many serious and relevant points to be made about green programming.
Any code change done to improve performance (response time) by saving on CPU cycles has the side benefit of saving power and is thus "green".
That is also why, in my opinion, concern for the environment and saving power costs, can validly be used as arguments in favor of using native Delphi over C# or Java.
Hire good programmers. They will write good code using less resources, and users won’t waste power trying to get past stupid bugs like Delphi users are forced to do. Right now I am wasting lot of power trying to bypass a bug in D2007 when running msbuild from the command line. In the build events the /p switch to select a different configuration is ignored and the configuration set in the IDE is always used.
I am starting to think that an Open Source Delphi is the only thing who could save it, because at least users will be enabled to fix all these stupid bugs one for all. And next I have to work on TDCOMConnection because it was never improved since it was introduced - and it does not allow to set an identity but the actual user - other power wasted to configure DCOM properly (no, I won’t use the JSON/dbExpress datasnap - I want to use interfaces and type checking, not thirty lines to call a function…).
"Get a mouse-ball based mouse. That red light has to be burning watts."
why not turning the mouse ball’s movement into power again? a self-powered mouse. sounds like a great power saving idea to me.
oh. i was a little bit late:
January 7th, 2009 at 11:51 pmSelf-powered cordless mouse
http://www.freepatentsonline.com/6903725.html
"Get a mouse-ball based mouse. That red light has to be burning watts."
Most ball-based mice are optomechanical, so there’s still a LED or two in there.
http://en.wikipedia.org/wiki/Computer_mouse#Mechanical_or_opto-mechanical
Better advice would be to ditch any of those dumb MS mice with their stupid "tail light"
January 8th, 2009 at 1:05 amAs green as "green programming" gets : rgb(0,255,0);
January 8th, 2009 at 1:53 amI’d vote you up, but I currently only have reputation 1
January 8th, 2009 at 8:54 amWell, your answer was pretty funny alright. But as you can read in the other answers, there are also many serious and relevant points to be made about green programming.
Any code change done to improve performance (response time) by saving on CPU cycles has the side benefit of saving power and is thus "green".
That is also why, in my opinion, concern for the environment and saving power costs, can validly be used as arguments in favor of using native Delphi over C# or Java.
January 8th, 2009 at 9:58 pmHire good programmers. They will write good code using less resources, and users won’t waste power trying to get past stupid bugs like Delphi users are forced to do. Right now I am wasting lot of power trying to bypass a bug in D2007 when running msbuild from the command line. In the build events the /p switch to select a different configuration is ignored and the configuration set in the IDE is always used.
January 12th, 2009 at 7:35 pmI am starting to think that an Open Source Delphi is the only thing who could save it, because at least users will be enabled to fix all these stupid bugs one for all. And next I have to work on TDCOMConnection because it was never improved since it was introduced - and it does not allow to set an identity but the actual user - other power wasted to configure DCOM properly (no, I won’t use the JSON/dbExpress datasnap - I want to use interfaces and type checking, not thirty lines to call a function…).