
This series is aimed at programming language aficionados. There's a lot of very abstract writing about programming languages and a lot of simple minded "language X sux!" style blog posts by people who know next to nothing about programming. What I feel is sorely missing is a kind of article that deliberately sacrifices the last 10% of precision that make the theoretical articles dry and long winded but still makes a point and discusses the various trade offs involved. This series is meant to fill that void and hopefully start a lot of discussions that are more enlightening than the articles themselves. I will point out some parallels in different parts of computing that I haven't seen mentioned as well as analyze some well known rules of thumb and link to interesting blogs and articles.
Member since:
2006-07-30
Exactly.
Effort is really hard to define because it depends on tons of things:
-your writing/reading speed
-your debugger
-the lifetime of your program
-how often you add features
...
Even if you just consider typing you have to ask yourself: Do shift keys count as typing? If they do Perl doesn't come out nearly as short
I'll touch upon this in a future article.
Of course, if you're the only person on OSNews who likes my articles I'm not sure how many more there'll be.