krivx

Does it matter at this point? If you are shopping for used equipment and all the early fails have been filtered out already then that's a good thing.

It doesn't sound like you are iterating on this. Look at the code you are not happy with. What is wrong? Can you fix it? If so, try to do those things next time. Don't stop the process.

>I learned by reverse engineering DSP code in another platform which was used for obfuscation

Whoa, I want to hear about this. I have a couple of DSP firmware images I've shied away from reverse engineering as I don't know the platforms.

If you need a fan to keep cool in that small space then a second body will make things a lot more uncomfortable.

>It is an utter and simple fact that due to tech being an everchanging landscape, any book more than a few years old is going to teach bad habits or explain concepts incorrectly.

Concepts change meaning and good habits turn bad every few years?

Shitty books are shitty, OKish books will be probably be fine for a language intro, even if they are old.

I guess Perl is kind of a special case :) I got up to speed by reading half of some fairly old Perl book, then reading most of Modern Perl.

Totally agree, and I'll piggyback this to say that the quality is not always too important either. Worrying about whether the book you are learning from is "the best" is not as productive as getting on with learning the language. A book really only has to good enough not to teach bad habits or explain concepts incorrectly.

>The FPGA also lacks an open-source (or even shared-source) toolchain,

I think this point is overstated. FPGAs are not microprocessors. I don't think an OSS toolchain would be anywhere near as beneficial as something like gcc. It would be nice to have but it's hard to think of any problems specific to programmable logic that this would address.

What would help is toolsets with less friction and less of an entry barrier.

I used to read those articles! Fond memories.

Any re-spin will cost money (and a lot of it). As technology improves, the old processes usually become cheaper too.

Japanese developers from that era are famously secretive. I have heard that Nintendo has a reputation for being particularly shortcoming with information to journalists or historians.

A surprisingly huge amount of modern science is formalising and quantifying existing knowledge. I would say that they either discovered this by chance or adopted it from another group that made the discovery - they had access to a very wide range of folk remedies from across the Roman empire.

They may have had no insight into how or why this worked other than drinking ash tonics makes you feel better than not drinking them.

I seem to remember lots of readers' letters mentioning worries about this...

"License

License for this source code is pending."

Sort it out!

How does the performance compare to a Forth implementation on an mcu? There are cheap fast ARM Cortex parts available, is the "100 MHz 16-bit dual stack processor" part directly comparable?

pvideo is great but there is an overwhelming amount of material. I was just hoping for a "curated" list.

e: a couple of my favourites by Raymond Hettinger

http://pyvideo.org/video/1780/transforming-code-into-beautif... http://pyvideo.org/video/1669/keynote-3

Are there similar list for other languages? Python, maybe?