Spyder vs. The Welkin Suite

Spyder is well suited if you're limited on hardware. You have to work with single code file. You need to quickly write some code and test it. Apart from this if you want to have a look at your variables then you can make use of Spyder. If you're working with Anaconda navigator then this can be the best to start with as it can be installed with single click there.

Incentivized

It is well suited to development-oriented projects. I find it faster to use the native Salesforce UI for more configuration projects. There are a number of tools in the suite that I have not used and probably could get more value out of it, but it has served well as my primary IDE for the last few months.

Incentivized

• Debugging of your existing code
• Generates figures very quickly as part of a figures tab which lets users understand results quickly
• Different layouts are available for the software which will give the users freedom to decide what layout works best for them

Incentivized

• Local History - Without having to setup GitHub this has been a time saver!
• AutoComplete
• Saves the entire project at once

Incentivized

• Colors in code format
• Add a broadcast to share the project with friends
• Contains more than one important language such as Python

• It would be nice if IDE feature releases were timed to coincide with Salesforce releases (i.e. make Lightning Web Components available on the day they become available in Salesforce instances).
• The IDE can be a bit buggy especially when you have several windows of the IDE open to different Salesforce instances at the same time on one machine.
• Sometimes, when you click to retrieve your data too soon, before the program has a chance to ask you to connect to the instance, it can cause the IDE to freeze.

Incentivized

It is fairly straightforward to use. Pretty much good to go as soon as you install it. The IDE itself is very user friendly, and it is only limited by whatever limitations Python has as a language. Great for those who want to run their scripts quickly or do some Python programming without fussing.

Incentivized

Most of data scientists or data engineers are either using ec2 on the cloud or Atom or PyCharm locally. It is a bit hard to find people who are still using Spyder and have the sight of the IDE and can help you to answer your question.

Incentivized

In general, when you need support there is someone there to give you an answer. I think there could be an improvement in this area, but it's hard to provide a substantial amount of support for a product that is charging roughly $15 a month. Do I feel I get more than $15 worth of support value when I need to request it? Yes.

Incentivized

I have chosen Spyder because it's free and open-source that comes with properly documented comments in the code. I have been using Spyder for more than 2 years and it always feels good to work with Spyder every time start my work. In Spyder, we have three windows one for man code window, idle window, and the other is for running your code and analyze. So to test a particular code I use the idle window to see what is going to be the result when I use this set of codes. That the main reason, I use Spyder.

I have tried using the Developer Console, Microsoft's Visual Studio Code with the Salesforce plugins and also Mavens Mate along with Sublime. The latter is deprecated. The rest are either options that are not as fully featured as The Welkin Suite or their setup time is much greater.

Incentivized

• Less time spent on employee training.
• Limited integration with Git.
• No tools for repository.

Incentivized

• I have probably saved about three hours, on larger projects.
• It has definitely saved me the overhead of having to work with other IDEs that have heavier setup requirements.

Incentivized