Comments for Ozone http://ozone.wordpress.com Software Development Bits'n'Bobs Sat, 07 Nov 2009 11:57:53 +0000 http://wordpress.com/ hourly 1 Comment on Metaprogramming, Java’s downfall by kcp http://ozone.wordpress.com/2006/02/20/metaprogramming-javas-downfall/#comment-7697 kcp Sat, 07 Nov 2009 11:57:53 +0000 http://ozone.wordpress.com/2006/02/20/metaprogramming-javas-downfall/#comment-7697 very nice article,with annotations(java) we can achieve meta programming very nice article,with annotations(java) we can achieve meta programming

]]> Comment on Development best practices: coding standards and the “20 lines” rule by Gestire le API… « JP’s Web Place http://ozone.wordpress.com/2006/03/08/development-best-practices-coding-standards-and-the-20-lines-rule/#comment-7692 Gestire le API… « JP’s Web Place Wed, 01 Jul 2009 07:25:07 +0000 http://ozone.wordpress.com/2006/03/08/development-best-practices-coding-standards-and-the-20-lines-rule/#comment-7692 [...] niente API tuttofare, niente funzioni/metodi mastodontici (cfr. questo bel post); [...] [...] niente API tuttofare, niente funzioni/metodi mastodontici (cfr. questo bel post); [...]

]]> Comment on Blame it on Io! A slow-paced introduction to the Io language by Alex http://ozone.wordpress.com/2006/03/15/blame-it-on-io/#comment-7687 Alex Tue, 05 May 2009 19:50:22 +0000 https://ozone.wordpress.com/2006/03/15/blame-it-on-io/#comment-7687 Have any Sheep or MutantSheep been harmed in the production of this article? Have any Sheep or MutantSheep been harmed in the production of this article?

]]> Comment on Blame it on Io! A slow-paced introduction to the Io language by fordston http://ozone.wordpress.com/2006/03/15/blame-it-on-io/#comment-7686 fordston Tue, 05 May 2009 17:01:07 +0000 https://ozone.wordpress.com/2006/03/15/blame-it-on-io/#comment-7686 Thankyou for your article! Is there a Smalltalk-like IDE for Io, and does this question even make sense? I.e., how does one keep track of all the protos and methods in the system? Is there a proto/method browser available? (I'm from Smalltalk, and, lately, from Java, -- and only tenuously from either of them at that!). ford Thankyou for your article!

Is there a Smalltalk-like IDE for Io, and does this question even make sense?

I.e., how does one keep track of all the protos and methods in the system? Is there a proto/method browser available?

(I’m from Smalltalk, and, lately, from Java, — and only tenuously from either of them at that!).

ford

]]> Comment on Build Io on Ubuntu Dapper by Andreas Schipplock http://ozone.wordpress.com/2006/07/27/build-io-on-ubuntu-dapper/#comment-7673 Andreas Schipplock Thu, 01 Jan 2009 18:57:27 +0000 https://ozone.wordpress.com/2006/07/27/build-io-on-ubuntu-dapper/#comment-7673 On Ubuntu Intrepid amd64 libsgml 1.1.4 doesn't link properly so it's not usable. I also noticed the latest version is from 2003 so it's quite old. On Ubuntu Intrepid amd64 libsgml 1.1.4 doesn’t link properly so it’s not usable. I also noticed the latest version is from 2003 so it’s quite old.

]]> Comment on Development best practices: coding standards and the “20 lines” rule by Bill Cernansky http://ozone.wordpress.com/2006/03/08/development-best-practices-coding-standards-and-the-20-lines-rule/#comment-7667 Bill Cernansky Wed, 23 Jul 2008 00:56:35 +0000 http://ozone.wordpress.com/2006/03/08/development-best-practices-coding-standards-and-the-20-lines-rule/#comment-7667 Arguing that 20 lines is better because it fits nicely in a window is a bit of antiquated thinking (in my view), born in the VT100 days. When I went to college in 1982, the rule in my Pascal classes was that a routine was disallowed from being larger than 24 characters. I found out later that this was because the graders could view the whole function on a single screen, so this fits your reasoning. However, when I am editing code, my coding window has at least 50 lines, if not more. This has been true since I got my first Amiga in 1986. I do strive for simplicity and brevity in my functions, but I seem violate my own guideline at least once per major project, when the "fix" would be more work to maintain than the original code. Arguing that 20 lines is better because it fits nicely in a window is a bit of antiquated thinking (in my view), born in the VT100 days. When I went to college in 1982, the rule in my Pascal classes was that a routine was disallowed from being larger than 24 characters. I found out later that this was because the graders could view the whole function on a single screen, so this fits your reasoning. However, when I am editing code, my coding window has at least 50 lines, if not more. This has been true since I got my first Amiga in 1986.

I do strive for simplicity and brevity in my functions, but I seem violate my own guideline at least once per major project, when the “fix” would be more work to maintain than the original code.

]]> Comment on Reinventing the wheel and associated pains by web application development http://ozone.wordpress.com/2006/10/17/reinventing-the-wheel-and-associated-pains/#comment-7661 web application development Thu, 08 May 2008 09:09:49 +0000 http://ozone.wordpress.com/2006/10/17/reinventing-the-wheel-and-associated-pains/#comment-7661 Hi Olivier read your blog...very interesting...as far i see, reinventing things rather than stabilizing the ones that already exist come with the man's nature of being insatiable for growth and popularity.Everybody wants to deliver something new to have its identity known by its new creation. Hi Olivier

read your blog…very interesting…as far i see, reinventing things rather than stabilizing the ones that already exist come with the man’s nature of being insatiable for growth and popularity.Everybody wants to deliver something new to have its identity known by its new creation.

]]> Comment on Blame it on Io! A slow-paced introduction to the Io language by Paulo Köch http://ozone.wordpress.com/2006/03/15/blame-it-on-io/#comment-7660 Paulo Köch Mon, 05 May 2008 21:00:09 +0000 https://ozone.wordpress.com/2006/03/15/blame-it-on-io/#comment-7660 Ruby vs. Io: I think it's a matter of taste. They have somewhat different paradigms, so it's like comparing two stripes of cheese. =P I already know ruby very well and I'm currently exploring Io. And liking it. =) Overall, it just seems more 'pure'. Ruby vs. Io: I think it’s a matter of taste. They have somewhat different paradigms, so it’s like comparing two stripes of cheese. =P

I already know ruby very well and I’m currently exploring Io. And liking it. =) Overall, it just seems more ‘pure’.

]]> Comment on Adding virtual methods to Ruby by Olivier Ansaldi http://ozone.wordpress.com/2006/02/28/adding-virtual-methods-to-ruby/#comment-7472 Olivier Ansaldi Tue, 25 Dec 2007 09:41:31 +0000 http://ozone.wordpress.com/2006/02/28/adding-virtual-methods-to-ruby/#comment-7472 You're absolutely right! I should have also highlighted that I have never ever used this pattern (or even thought of using it) in any production code, since it has no place in Ruby. This post was an attempt at showcasing Ruby's flexibility. Thanks for your comment! You’re absolutely right!

I should have also highlighted that I have never ever used this pattern (or even thought of using it) in any production code, since it has no place in Ruby. This post was an attempt at showcasing Ruby’s flexibility.

Thanks for your comment!

]]> Comment on Adding virtual methods to Ruby by Seungjin http://ozone.wordpress.com/2006/02/28/adding-virtual-methods-to-ruby/#comment-7451 Seungjin Sun, 23 Dec 2007 07:31:38 +0000 http://ozone.wordpress.com/2006/02/28/adding-virtual-methods-to-ruby/#comment-7451 The above way not only requires a dependency (the .virtual method), but means you can’t inherit from any other class. Furthermore it discourages duck-typing. The above way not only requires a dependency (the .virtual method), but means you can’t inherit from any other class. Furthermore it discourages duck-typing.

]]>