[DamagedProperty]

This book is great.

This book certiantly is not a crash course. I have been working through it in my spare time since I got it a couple of years ago. I have been taking my time because I was going through school when I got it and couldn't make time for it. Now seeing this article I should pick it back up again.

I suggest though that everybody resist the urge to find the answers rather than doing them yourself. It's quite rewarding when you figure things out. There isn't one way to do it.

The only complaint I have is that when you start getting into higher functions they recommend you not use the pieces you built up for performance reasons. Personally I would like to figure these out but perhaps that should be left for a later day.

[adaptives]

Using the pieces you built as you move along is a great idea, and an opportunity to understand the optimizations required to make them performant.

I think one reason, why they may insist is because, the basic pieces you built will be in HDL, while if you use the ones provided by the software, they will be in the form of compiled Java code. Perhaps that is one of the reasons why the books pieces will be faster/

[scorpioxy]

I finished the book a few months ago, and yes that is the main reason.

I wanted to test the whole finished stack using only my components so I did run it using only what I built. It ran but was around 10x slower, mainly the graphics tests. I did optimise the performance of the basic drawing algorithms using faster ones but, naturally, it was still much slower than the java implementation.

Another advantage of using your built components is that it helped me uncover some bugs which I only noticed when you ran something as complex as the pong example.