Comments for Ozone

Comment on Metaprogramming, Java’s downfall by G.B

G.B — Sun, 15 Jul 2012 12:58:20 +0000

What’s really missing in Java is *static* metaprogramming. You can do almost anything you want through reflection. But of course there’s a tradeoff: dynamic metaprogramming is easier to implement and makes your code smaller, and static metaprogramming makes your code run faster.

Comment on Development best practices: coding standards and the “20 lines” rule by Carl Vilbrandt

Carl Vilbrandt — Wed, 06 Jun 2012 19:27:03 +0000

Yes 20 lines is as dumb and crude as humans. It is needed because programmers do not understand or want to admit to any human limits … Perhaps the pure reality is logical coupling and cohesion .vs. artificial breaking code in to modules based the limits humans eye / brain. Perhaps the exception is when the coupling and cohesion extends human limits then documentation is needed to help extend human limits. Documentation also needed to understand compact code… and to help people learn to code…

Comment on Metaprogramming, Java’s downfall by Tarsi

Tarsi — Wed, 25 Jan 2012 12:51:35 +0000

Java lacks metaprogramming….
how about using groovy which has some powerful features when it comes to metaprogramming ?

Comment on Development best practices: coding standards and the “20 lines” rule by David Murphy

David Murphy — Tue, 24 Jan 2012 21:57:54 +0000

Pah, of course I meant Coupling and Cohesion (beats head against wall). I must be getting old…

Comment on Development best practices: coding standards and the “20 lines” rule by David Murphy

David Murphy — Tue, 24 Jan 2012 21:57:07 +0000

The extra functions will contain the same number of execution paths in total. Also, you may create extra needless paths because you have taken functions that might have been logically cohesive with loose coupling and turned them into the opposite.

Comment on Development best practices: coding standards and the “20 lines” rule by David Murphy

David Murphy — Tue, 24 Jan 2012 21:53:31 +0000

I started programming in 1981 in a government place whose code went back to the early 1970s. The 20 line rule applied than (it was for Cobol, can’t remember of the same rule applied on the assembler code). It was there because the code fit into one page of standard computer printout (we didn’t have screens, we used punch cards and paper).

It was a dumb rule then and a dumb one now, it delivered little benefit but made logically coherent code artificially split across modules. If you applied the ancient rules of code modularisation (Coherence and Cohesiveness) you would not need such artificial rules.

I suppose I ought to be surprised to see you recreating ancient coding rules again, but given most programmers only (re) discovered the necessity for testing recently and still don’t have any rules to guide them about handling exceptions I suppose I should not be.

Comment on Little Prolog challenge by Youssef Hassan

Youssef Hassan — Fri, 13 Jan 2012 03:11:43 +0000

When I backtrack from the shuffle code [1,2,3] it gives [1,2,3,[]]??Why is that??

Comment on Blame it on Io! A slow-paced introduction to the Io language by 10 programming languages worth checking out | IdeasCart

10 programming languages worth checking out | IdeasCart — Mon, 10 Oct 2011 20:15:58 +0000

[...] Blame it on Io! A slow-paced introduction to the Io language [...]

Comment on Development best practices: coding standards and the “20 lines” rule by Nagora

Nagora — Tue, 13 Sep 2011 08:34:05 +0000

“Eventually” was about 30 years ago when Forth did exactly this – you were (and still are in some current Forths) automatically allotted one screen of comment space for each screen of source code. These screens were called “shadows” and depending on the editor either were shown side-by-side with the corresponding code or there was a key to flick between them.

Having space allotted like this “tempted” coders to actually use it for commenting.

Additionally, it was difficult (although not impossible) to code single functions (or “words” in Forth lingo) that were more than 15 lines long and the recommended length was 2-4 lines.

Forth was a major player back in the day and used by NASA for many probes. It still shows up in places now and has a reputation for creating solid reliable code. In modern terms, it is a domain language defining language – you start with Forth and design a language with it that suits your problem and then you solve the problem with that language. It’s rather fun.

Comment on Metaprogramming, Java’s downfall by Yasky

Yasky — Thu, 04 Aug 2011 17:23:35 +0000

How would you compare Java’s metaprogramming to Ruby’s? Could you make a post about that? Thanks