http://www.amazon.com/gp/product/0240825152/ref=oh_details_o00_s00_i00
 
To be released Monday, if I'm not mistaken.
 
The reason I find this so amazing is that I can't imagine more than a few hundred people in the whole world that would be interested in reading such a book, let alone shelling out 50 ro 60 bucks for it.
 
Of course I ordered it immediately.  I hate C++ with a passion, and the last thing I want to get caught up in is software development (this is what I've done for a living for 45 or so years) at the expense of music.  And yet ... I'm so curious about how all this VST magic works under the covers that I couldn't resist.
 
Fellow geeks, you might want to check this out.

Thanks for the heads up. I did Java sometime ago.. been avoiding C / C++.. 

It's nice all the info is made into a book instead of scattered around the net.

I feel ashamed.  I worked as a Telemetry processor programmer at NASA but it was back in the Apollo era and it was machine language and BAL.

I learned primitive coding on my Commodore 64 then moved on to programming in dbase...remember that?  Then started learning C.  Then...oh so wisely...threw in the towel.  Now, even writing a simple CAL routine is arduous work.  Real programmers frighten me:-)

About 6 years ago I would have loved to have the book. No time now though.

I'm an applications programmer, you know, to run businesses like; inventory control, purchasing, work order control, order entry, A/R, A/P & MRP. 

C/C++, Java etc. are for the "driver" and "architecture" wonks (no offence meant). Give me a 3/4GL language any day and I'm a happy camper. 
I admit that I have done two small projects, one in Ruby on Rails (tedious) and PHP (not so tedious as the application was already "built"). The fact that these languages/idioms/platforms/frameworks are meant for the web, their basic architecture reminds of the cr@p we had to go though in the early days of software development (mid 70s thru mid 80s).  

Let us know what you think of the book, David. Specifically, if it has information not already available for free via the SDK and online resources. 

I've written a couple simple VSTs just to see what's involved, always intending to revisit it some rainy day. But whenever said rainy day comes along, I find I'd rather be making music than cutting code. However, I do have some concepts in mind for plugins that currently do not exist but should be moderately easy to code. 

Dave,

When you get that TALENT vst done, I'll be your beta tester.

bapu


Dave,

When you get that TALENT vst done, I'll be your beta tester.

I'm first going to focus on the DOES-NOT-SUCK VST.  After that, we'll see.

bitflipper

Let us know what you think of the book, David. Specifically, if it has information not already available for free via the SDK and online resources.

That's not going to be possible, because I've not summoned up sufficient interest in tracking down on-line sources of information.  But with the convenience of this information within the covers of a book (that I can read in bed!), my interest is considerably more engaged.
 
But I will report back.  It may be a few months, but I once I've read it (or read enough to realize the purchase was a mistake), I'll do a mini-review here.