Just because PHP/MySQL has a lot of books out in the wild, doesn't
mean that you must spit out a lot of books to counter it.
If people want to use PHP/MySQL, so be it. If people want
Perl/MySQL, or Perl/PostgreSQL, fine too. I couldn't care less. All
I care about is for the PHP community to drop the annoying
php prefix in every project (except for
phpMyAss)
Then again, it makes it easier to ignore certain projects ;-)
I don't think focussing on a niche is going to gain a lot of 'mortal
souls' though, quite the opposite. You hope that people -who have
never seen anything but PHP and MySQL- take the huge step in
changing not only the database type, but also the programming
language. I doubt if it's ever going to happen. Especially because
most PHP 'programmers' seem quite happy with what they have.
Changing two things at once is probably raising a huge threshold.
Imagine the Python community telling you to drop Perl and PostgreSQL
and join them with Python and, let's say, Oracle (and yeah, I know
very, very little about both). I'd tell them: "Why? I'm perfectly
happy with Perl and PostgreSQL/MySQL/SQLite!". And I predict the PHP
people out there will react the same.
Instead of creating your niche, why not write books about "Web
Development with Perl and (Class::)DBI" and let people see that you can use
MySQL and PostgreSQL. In there you could -of course- point out why
PostgreSQL would be better according to you. That way, you don't raise the suggestion that Perl is only suitable for PostgreSQL and thus not for person X, who only knows MySQL.
--
b10m
All code is usually tested, but rarely trusted.
|