Dreamweaver is back for us, coders.
Anselm Hannemann

Won’t try it (far too busy) but looks very similar if not identical to VS code interface, if this is going to be a pay-for-use product why would anyone bother when VS code is opensource? However on to opinions.

Features i would like to see in my ideal code editor:

  • Ubiquitous cross platform experience. With the exception of perhaps hotkeys (mac) i should be able to use the software on any linux distro, windows or mac and it should have exactly the same capabilities. Why is it a big deal?
    It’s pretty obvious that linux has the bigger marketshare when it comes to server side stacks. However if you want to be comprehensive with testing UI/UX it’s actually easier to do that on windows. Run W10 with a virtual machine and you can have simultaneous access to — a previous version of IE (VM) and MS edge, firefox, chrome and safari (native). I should be able to have the same code editor experience regardless which OS it’s using.
  • SSH cert management. OK so you said DW has git integration… with which remote git repo? Github? BitBucket? Beanstalk? What if run a self rolled gitlab? What if i want to git push to 2 repo’s simultaneously? I have yet to see a truly cross platform interface that can efficiently configure this type of stuff (jury’s still out on gitkraken).
  • Integration with package managers (NPM, composer, etc). Speaks for itself. Furthermore this should be performant and favor a distribution model as default implementation. For example by default NPM has to go check remote npmjs repo every 10 seconds unless you explicitly set “ — cache-min 999999”.
  • Easily configurable autocomplete. I like sublime for having superfast perf on searches, etc. But i like fuzzy autocomplete (even for functions i’ve defined) as well as the languages / libraries functions for whatever language im coding in be it ES6 for nodeJS (a sore point right now for sublime) or python. This currently forces me to either go without autocomplete in sublime for great perf or alternate between sublime and Atom (for better autocomplete regarding nodeJS), this is ridiculous.
  • Cloud sync for configs and snippets. The advantage of AdobeCC is that you can almost effortlessly move between machines and still maintain your workspace / plugins with apps such as photoshop for example. In the context of code editors it’s remained pretty complicated until recently. Take sublime users for example, you would have to sync your plugins / configs using a 3rd party cloud service (dropbox being the most efficient using deltasync). This is dumb. For new DW a config file could be stored with your CC creds then when you log into the editor (on any machine) it grabs the file, does a quick diff (compared to the default local one) and implements your changes / grabs whatever packages it needs.

The TL;DR version is i want a performant editor, which i can use on any OS, which is as pain-free to config and use as possible (consistent UX) whether it be on an existing dev machine or a new vanilla one.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.