I like Atom because it is simple and not too complicated. Configurable, full-featured, yet remains nimble. You can not beat the cost of Open Source, so this leaves software like BBEdit out in the cold. Atom is not as hardcore as Vim or Emacs. Less complicated than full IDEs …
In beginning stage of project, Atom wins the race against them all. I selected Atom because of its support for many plugins, simplicity, formatting tools, open source control . But for large scale projects, atom is not suitable editor because of its unexpected behaviour in case …
I prefer Vim simply because it's as simple as apps like Notepad, Notepad++, or gedit, but as feature rich as Microsoft Visual Studio. The startup time is quick, the response time is quick, it never freezes. Vim always "just works." Vim can be downloaded in a few seconds (if …
I use Vim for specific use cases and others for their own purposes but all of them are being used at my work every day. Vim has its pros like it's free/open source, has a mouse free interface, is lightweight and fast, and once learned is hard to forget.
Atom is great for simple HTML coding. It's fast, has intuitive shortcuts and several options. I particularly love the "convert spaces to tabs" function that I haven't seen in other editors.
I'm not sure how it would fair in more serious web development today, if there are plugins for live updates of the page you are working on...
But the problem is that it has been discontinued so you know there are no new features or fixes coming through.
SharePoint does not provide, out of the box, a tool to create / update workflows from web. You have to use SharePoint Designer in order to create them. If you need to implement custom workflows for specific business processes, then SharePoint Designer is well suited. SharePoint Designer allows you to create workflows with task approval, email notifications, assign variables and update SharePoint Lists / Documents properties. In our company, we have created specific workflows for : - Purchase order - RH forms validation like annual employee review - Dematerialized existing forms and validation
I would recommend Vim in any scenario where text files have to be viewed, created, or edited on GNU/Linux computers. Regardless if you need to quickly change a few things in a configuration file, or you need to write up a full document, Vim is great. I wouldn't use Vim to view, edit, or create anything that requires "rich-text". In other words, if you need to format the text (bolding, font colours, word-art, etc), then Vim isn't the tool to use.
Atom is highly customizable and allows for various themes and extensions that can make your code easier to read.
Atom has many code hinting features that allow users to write faster and integrate with services likeLINT that can clean up your code once your done to meet your internal teams style choices.
It's very fast and manages projects well - Accessing other files within a related folder(s) is very easy and intuitive.
2013 Workflows - Loops: You can build loops to work while a value (not) equals something, or N number of times. You can insert Parallel Blocks to do multiple things at once, or to watch for multiple things, and when 1 thing finishes, cancels the others and moves to the next step or stage.
2013 Workflows - Stages: Previously all we had were steps, which worked sequentially. With the Concept of Stages, we can create blocks of steps and based on the data collected during those functions, we can tell the workflow to go to a different Stage in the workflow based on a set of 1, or multiple, Conditionals in a transition area after each Stage. Giving you the power to develop multiple entire processes and skipping to the correct part of the workflow, rather than going through 20 conditionals to find out you needed to do action 31.
2013 Workflows - REST API: the "Call HTTP Web Service" is a very powerful tool, but hard to understand if you have never seen it done, or have a guideline. It works very similar to the requirements in PowerShell to connect and get and post data to SharePoint using the Rest API. You can also use this to manage permissions on List Items, Lists, Sites, and Site Collections. Best part is when developed correctly, it is SUPER FAST!
Intentionally Building Infinite Loops: I have built multiple review process from Managing Certifications to Updating Published Documentation, that monitors when an Item, based on provided approved metadata, when the "Author" needs to review the document within the given amount of time. They will get e-mails with links asking if changes are needed. If not, it is routed to the Approving Executive, and the Workflow Automatically updates the Metadata to push out the review dates to the next date, based on metadata provided on how how often the document should be reviews. By using conditionals in the transition of stages, it basically starts over, and goes into a parallel block to allow the monitoring of multiple values of metadata to move to the next stage. Very Powerful when you want to automate these types of process. It truly is a "Set It and Forget It" process.
In the newest version of SharePoint Designer, they have gotten rid of the Design view which makes what used to be quick and easy changes much more code-intensive. This makes it harder for non-IT users and is more risker for all SharePoint Designer users.
SharePoint Designer workflows have a lot of functionality, but there are also some crucial limitations, such as not being able to put lookup fields in email subjects or using parenthesis to separate/group logical conditions.
Although this goes along with the Design view, there really isn't a good user interface anymore for adding conditional formatting and styles in views/pages.
Well Atom is open source so the re-new is a no brainer. The only way I would stop using Atom is if the developers somehow made it not function well. Or, if the project got forked to a commercial version or something. Or, there could be the case that development stops or that it was not updated on this or that platform
I give Atom a 9 because it is one of the most modern text editors built with JavaScript intentionally to allow the editor to be changed and modified with custom functionality that a team may need. I think I would otherwise give atom an 8 due to support, but it gets a 9/10 because of the extensibility/plugin capability.
I don't consider the steep learning curve to be a hinderance on the overall usability. I would rate this a ten, but to be honest a lot of people do get hung up at the beginning and just abandon it. However, for people who have made the moderate effort to get over the hump, nothing can be more usable.
Atom has an active forum and a Slack group where you can ask technical questions. Occasionally, the authors will pop in to answer a few questions here and there, but most of the time, its other helpful users who will assist you. Though they aren't the most knowledgeable, they are at least timely.
As for plugin support, that differs with each plugin, but as I mentioned before, many plugins are no longer maintained.
Support is good from Microsoft. They are quite responsive when we raise a ticket but SP Designer support will be ended by Microsoft in the near future as they have got new techs like PowerApps and Flow to achieve the same functionality SP Designer does and even more than that.
There is no commercial support for Vim. Thus, it will not get a mark beyond 5. However, community support is very good. You can easily find solutions for most of the problems in the community.
Our company likes to keep things open, and we don't want to prevent developers from customizing their environment the way they want. Atom seemed to be a lot more open than our existing tools and has good community support on pretty much any programming language. This can create some confusion since adding too many extensions or customizing can make the tool slower than it is supposed to be.
I haven't used anything else like this. I use different products for workflows and forms, but they aren't listed in the listings for this page. Instead of using it for workflows or forms (deprecated 2 years ago), I use Nintex. For everything else, I have what I need in the Modern version of SharePoint online
Vim's keybindings are a lot more complex than Notepad++. With that, comes a whole bunch of capability that Notepad++ just can't match. Emacs is comparable, in terms of capabilities--because Vim is built into so many unix systems, I chose to learn it instead of Emacs. Knowing both probably isn't a bad idea, but there's enough to learn in either camp to keep you busy
The tool we use when we need quick fixes. Allows fast, reliable scripting to fix urgent problems in our applications.
When applications grow from 5-10 files to 100's, they need to be migrated to a heavier-duty IDE. This can be cumbersome and quite annoying, but is necessary to maintain code integrity on such a large scale (since it cannot be done with the limited default toolset of Atom).
For my needs, I have not found SharePoint Designer useful for my day to day maintenance of SharePoint. It is useful for viewing all the objects that make up the SharePoint site.
It is not as intuitive in regard to setting up Workflows. I have yet to use it to set up workflows in SharePoint. Maybe if I needed more complex workflows, it would be beneficial.
I like to use SharePoint Designer for moving around files within SharePoint sites.
