Are Adobe promoting the alternatives to Database and Server Behaviours

Question

The apparently disastrous depreciation of Database and Server Behaviours in Dreaweaver CC seem to have left a nasty taste in the mouth for many users. I am not a very experienced web developer, to the point where I cringe when describing myself as such, and I assume, possibly naively, that if Adobe have made them optional now, that there is an alternative; if not, the decision seems dimwitted in the extreme, and I did not expect that to be the case with a company who's software I have admired and found useful for so long.
So, assuming there is an alternative method to create dynamic data driven websites in Dreamweaver, can people please suggest what they are, and possibly point me towards the Adobe support and tutorials that encourage and explain their use. It must be in Adobe's interest to to get Dreamweaver's users to adopt the new technologies, and, at the moment, I cannot believe there is no adequate alternative.
I have seen many complaints about the depreciation of the support, but no one seems to be saying "don't use those, this is what you need to do the job". If anyone can do that for me, it would be greatly appreciated, and I imagine others would also benefit.
And if the alternatives are inadequate, then perhaps we could discuss how to get Adobe to repair a broken product.

Answer 1

Rob Hecker2 wrote:
As the web has evolved it makes sense that websites are no longer created by one person using one tool (DreamWeaver).
I agree with you there, depending at what level you are. A large design company will have specialists in all areas whilst a small one man set up will not. These small one-man band businesses usually attract low paying clients who will not have a budget to employ 'specialists' which is where DW server behaviours fitted in perfectly. Although it's benefited me enormously by learning how to manually connect and query databases I still think it was and is pretty lazy on the part of Adobe NOT to update the behaviours which were an important part of the program for many.  3rd party developers have produced extensions at a considerable cost, over and above what it costs to run DW. They quickly rolled out these extensions when it became clear Adobe had decided to upset many of its customers by not including any alternative in CC/CC 2014 - so don't tell me it would have taken many hours development and financial resources which Adobe just could not afford. That's bollocks. This is purely a decision by some wanker at top level in Adobe that is probably smoking crack and don't know their *** from their elbow, or what their customers really want.
Rob Hecker2 wrote:
It always seemed to me that by adding support for PHP/MySQL at all, Adobe was just going to frustrate people.
NO, the frustration is that Adobe introduce components and then doesn't develop them any further preferring to introduce a bag of dog poo into their programs like fluid grids instead of concentrating on what they do best.
Rob Hecker2 wrote:
PHP programmers do not use Dreamweaver for PHP Development. I recall a questionnaire on a website where the question was "What tools do you use for PHP development?" Dreamweaver was not even on the list of choices.
Serious php developers don't  - you're right - but for those who don't program php/mysql on a daily or even weekly basis, but occasionally have the need for it, they do. Most websites can benefit from having a backend database these days and at a time when databases are main stream Adobe decide to ditch what was a premium attraction of the software, completely senseless decision. A few years ago when static sites were main stream Macromedia were ahead of the game an introduced the Server Behaviours. I guess the top brass in charge at the time (Macromedia) weren't smoking crack all day and instead listening to what their customers wanted.