Well, it is hard to take part in such a discussion. That is right that I know you all by your various interventions on the CAB, but I do not really know what are your cultures and your deep personality. That sometimes makes the comprehension of the humor subversive or not, the self-mockery, or just the simple provocation, not easy to capture for those of us that are not native English spoken. That often makes the deep bottom line sometimes difficult to interpret. Therefore, to make the difference between a direct way of speaking or a gratuitous aggression. Well that said, Having no visibility on the real directives necessary for the average users of DW, nor the orientations of the entrepreneurial strategies concerning the Creative Cloud's audience. It is difficult to position oneself on the good or bad choices, of the successive versions of DW. I remark that we are all just express our own subjectivity, based on our own and personal business. I often read in this thread, "... developer, casual developer, designer (to interpret it by non-developer)... and so on.... ". However, hey, one criteria that is not present is that whatever we consider ourselves in which case we are... One all have to support the company to which we are affiliate. For that, we have to render projects on time to satisfy our clients or partners. We have to render a service beyond their requirement. We have to preserve a value for money that is up to the market. We are often part of a team... and each member of this team generally does not have the same field of action, nor the same approach and vision of the web site construction than us... But, we all have to refer and use the same technologies by tools which at one point somehow DW is part. (at least for us on this forum) Moreover, today, the notion of a website itself can be completely different. Depending on whether one are trying to present a newsletter, or building a one page site full of animation, parallax effects, transitions.... , or having a hard dynamic website 'Ã la papa' ('old fashion look and feel') completely PHP/SQL based, or a web application that meets innovative needs relying on 'modern' conception, or being distributed as a complete integrated mobile consultation... We also must not forget that some of us will take into account the quality of a code, and being more demanding on that point. Unlike others that will not hesitate to copy / paste here and there sections of code (more or less questionable), taking into account only the final rendering being the emerged part of the site and which will make the final reference. We should not forget that the structure is the first major and important point, and that the HTML code quality will arise a strong guarantee of durability, scalability, interpretability and so on. Therefore, whatever the profiles that we do have, by using DW we should at least know and understand basics of robust and well-interpreted HTML, we also must be sensitive to the structure, to the DOM, and to a real content strategy. In such a thinking, must DW be a simple text editor? a complete IDE? a base for receiving extensions? Should DW be more designer oriented than developer, or vice versa, or have to answer as well to the one as to the other? I think that only Adobe can position such answers, and, understand what the real needs of their users is. But, in any case, DW must be able to remain independent of any third technology, or addons. DW must be open to be usable with other crosscutting tools, being part of the Creative Cloud or not. As far as I am concerned, I think that DW should in no way become a complete and autonomous tool. On the contrary, DW must propose tools and features that allows us to not rely, and depend, on any add-ons to produce content based on pure Mozdev and WhatWG standards (becoming later on w3c recommendations). Having a real time editable rendering, having a drag drop components interface to build and reflect the content strategy, integrating in such a way most of the needed technologies is what DW propose since the Macromedia age to gain more pure designers users, and that is a great bridge. However, this should not exclude the minimum coding skills mentioned above. And DW must always be on the gap in terms of novelty and future recommendations then for extra features (features above basic needs), should we use and rely on extensions or not? The main question are, Does the use of extension is time saving for this project, does the extension really meets the goals expectations, does the extension cost remains financially acceptable, does the use of the extension offers real interoperability with the rest of the team or with their own skills.
... View more
AdChoices