[ Previous entry: Terai Yuki 2! (Links fixed) ]
[ Next entry: Vociferous ]
Thoughts on TheFoxProShow 024 (Better late than never) music:
I was archiving the access logs of Pixelcatalyst.Lair and Foxpro.catalyst while The FoxPro Show 024 was playing once again in the background.
I did hint a while back that I'll be posting something TFPS024 related. The FoxPro Show 25 came out, then 26, 27, 28, 29, 30 and 31... a couple of Mondays podcasts were also released and after a month, I'm still here unable to scribble those buffered thoughts.
OzFoxRocks even went online a couple of weeks ago.
So I was thinking it was about time I 'unbuffer' those buffered thoughts which a couple of minutes ago are being electrocuted by strange toon-porn infested neurons.
There's a problem though with unbufferring a month old casing of thoughts. The mind-to-fingertips-to-keyboard coordination just won't work smoothly.
Though I remember most things discussed in the show, I would like to double check on one detail.
Now there's a difference too, when you're working, archiving, reading some parts and listening at the same time through an P850.00 (1 US dollar = P55.00) speaker... I kept on skipping the part where that detail was being discussed.
It was an insfoxpirational show, so I didn't mind listening again and again.
After the fifth replay though I noticed that ants and a couple of six legged entities were slowly swarming in.
Sixth replay and I'm seeing metal plated grasshoppers with tiny boxing gloves and soccer shoes.
Now... It was the fear of the eight-legged creatures weaving out that got me to stop the other works and concentrate on listening... and there on the 13:27 timestamp, I found what I was looking for.
I'm currently multitasking once again (I can't seem to blog if I'm not doing some other stuff, and returning to this window every now and then to continue my chain of thought (and listening to some loud Moby stuff)), so I hope I get this right.
Ken Levy was giving out the 100:1 ratio in terms of Visual Studio/Visual FoxPro's usage. Which he further places on a different perspective that based on that 100:1 stat, VS can gain in three days what VFP can sell for a year.
(That would make approximately 122:1 though, but still... we get the point.)
My first thought/reaction when I first heard this a month ago was why not re-include Visual FoxPro (without changing the VFP core) inside the Visual Studio package.
Ah there... I'm hearing the uproar of CLR purists (and yes I admit I'm not an expert at this marketing/branding stuff (besides Microsoft's licensing and pricing is not that simple to start with)).
But let's just do a little elementary math.
Approximately VFP's price is 650 dollars.
Now... Visual Studio comes with different prices and I don't have the actual statistics to show which edition/package sells better. But for the sake of this blogcussion, let's pick the Professional Edition which is around 800 dollars.
Now let's go back to that 100:1 ratio above. If VFP can sell 100 copies in 300 days, VS can sell the same number in three days.
(Let's use 300 instead of 365 since this is 'elementary math' and I will refrain from using the 'for the sake of discussion' line from here forth)
Going further VS can sell 100 * (300/3) copies in 300 days. And that is 10,000.
Now for the sake of discussion (didn't I mention that I would refrain from using that already...), let's include VFP inside VS and just jack up the price of VS to 800 + N dollars (where N is less than VFP's current price).
(I know VFP is worth MORE and if I have enough bucks I wouldn't mind buying VFP even if it's base price is more than 650. Legacy is priceless... but just FTSOD (For The Sake of Discussion)).
Now if N = 50 then, 850 * 10,000 is 8,500,000.
The additional 50 * 10,000 alone is 500,000. Much more than 650 * 100 which is equal to a 65,000.
And even if N = 10, 10 * 10,000 is still 100,000... 935,000 more than 650 * 100.
Yes I know I know... the pricing of these shrinkwrap softwares are more complicated than elementary math and there are tons of factors involved.
And for the nth time, the things posted above are FTSOD. Though there are possible benefits for both products (VS and VFP) and the community as well, if MS packs back VFP inside the Visual Studio package.
And there are disadvantages too, which are in the first place the reasons why VFP was not included inside that .NET package. (As discussed inside the Fox.wikis site, the Universal Thread forums and countless other fox sites.)
(Also notable are the advantages of shipping Visual FoxPro as an independent product.)
A clientbase of 100,000 (though I think VFP's actual client base is more than that) is still NOT negligible.
And if you can remember around 2,000 years ago, a shepherd left 99 sheep to find one missing sheep. Though the FoxPro community is far from being lost sheep, we deserve the same kind of lovin'.
Disclaimers are for castrated EARTHLINGS.
Powered: GREYMatter | GM-RSS