I understand your concerns, and they are being addressed for issue #2. Without going in to too much detail, the person who normally does our layout work (for GroovyMag) was unavailable due to a family medical emergency. Finding anyone willing to take on a project of this size on short notice was difficult, but we did manage to get it out, primarily because, yes, the content itself is good. This was a decision with no easy answers, but I made the final decision to go ahead. Next month’s will be ‘back to normal’ so to speak, closer in spirit to the GroovyMag magazine, with clearer layout, mono fonts, and more of what you’d expect. The ‘proportional font’ issue – I’m somewhat embarrassed to say I’d passed this around to a number of other developers who’d also missed that. :/

I appreciate your feedback as this will make April much better. Thank you.

Sorry, I don’t mean to be rude, but this PDF really doesn’t look good. If it’s a PDF, then I would expect at least as good typography as one can achieve on a web page, not worse. I almost thought, that maybe there’s something wrong with my PDF reader.

Sure, the choice of colors is a highly subjective issue, but for me this blue-to-pink gradient looks like the lamest thing ever.

All lines are packed together so tightly, that it’s hard to read. Code examples are in proportinal font. I’m far from being a typography expert, but camon… using two dashes (–) instead of using m-dash (—)… how lame can you get?

The content looks good, but I can hardly stand the layout.