![]() ![]() That's probably ok for your amateur developer BUT if any full-time web-developer is using it as a front-line bit of their kit for automated code writing and its their livlihood at stake then maybe they should seriously think again and at least have a plan B in position. Yes you will have extension developers say DW will work for many years to come, it perhaps will but it no longer receives any future updates, so those who use and depend upon it stagnate quite quickly. In any automated environment you put yourself in the hands of the provider and if that provider decides to change things you are not in control.ĭW unfortunately is an extendable program where many developers rely on extensions, which is all well and good until DW shuts up shop. Others will be working in both v3 and v4 trying to remember which class is native to which version. It really is a wise decision albeit it takes time and effort.īootstrap 3 users have to now familiarise themselves with new Bootstrap 4 technics and classes, which ia always a pain. I've got the message from this discussion and others. If you cut corners and are intending to be in this for the long-run then you could well be setting yourself up for a nasty surprise in the future. ![]() Web-development is a continuously shifting environment and the only safe way to stay afloat is to learn to code, then any html editor will do the job, its that simple. Many, many have sadly fallen by the wayside over the past decade. ![]() Its happened in the past and will happen again with many web-develoment programs, not just ones bought to the market by Adobe. Instead of persisting it often decides there is no more legs in the product and closes it down, without any real consideration for its customers. The problem is Adobe is struggling to keep up with future web-development trends. It may be that I am asking the impossible. My question is, is it worth me investing my time and money in learning to use DW or is that likely to go the same way as Muse? I fully appreciate that Muse code cannot be read by DW (or anything else for that matter) but I am going to have to rebuild from scratch at some point in the future anyway, so why wouldn't I use DW? I appreciate that the learning for DW is in a different league from Muse but I may be prepared to do that if I had confidence that DW was going to be around for what, another 10 years? I have Muse sites and am now looking for an alternative. Pedigree1 me, your answer misses the point - I appreciate you weren't addressing me so no offence intended. With the code base of Muse being so bad to read, especially when plug-ins/widgets have been used, having one place to go may help ex Muse users in the conversion to a code based solution. For Muse users who do wish to try going in the 'convert to Dreameaver' direction, I would ask if the Adobe forums could add a separate forum section just for those people. The main problem with trying to use Dreamweaver, is that the Muse code is almost unreadable, especially if you have used any plug-ins/widgets. It may also be an idea to at least look at the Adobe Spark pre-release builds, as that appears to be Adobes recommended option, though with Adobes record of support for anything web, and given what they have done with Muse, I personally would be very cautious about using Spark. Muse will continue to be available as part of your CC subscription, it will just never be developed further. I would not advise trying to use Dreamweaver to maintain or update a Muse site.Ī better option would be to continue to use Muse until you can convert the sites to normal html, css, javascript. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |