I think that if someone asked me for an IDE for Java programming, I would definitely recommend Eclipse as is one of the most complete solutions for this language out there. If the main programming language of that person is not Java, I don't think Eclipse would suit his needs[.]
PowerApps is well suited for "quick-wins" and fast prototypes of business solutions. It also is beneficial for situations where business partners and developers work together - it allows the business folks to provide a "quick-and-dirty" prototype which is then fleshed-out by developers that are trained experts on the platform. The interactive and easy to understand representation of the solution allows business partners to "see" the solution and add, remove, or correct aspects of it themselves. It provides a common view and understanding of the actual solution across business units and tech teams. PowerApps, being a low-code\no-code platform is not well suited for business processes that require many complex computations or large amounts of custom code - such as solutions that are better architected as Web Site or "full-blown" desktop solutions. There are solutions that are just not easy or quick to accomplish in a low-code\no-code platform. Enterprise Architects should know the difference, however business partners often try to create a solution and only when stuck because it becomes too complex do they engage a tech team for assistance - at which point there are sunk-costs involved and hinderences to re-platforming the solution
Power Apps has formats that are pre-built that don't require any coding which makes it easier to achieve your vision. This does become a challenge if your App needs don't fit into that format.
We deal with a ton of data so the fact that you can connect to any data source in addition to their pre-stablished data connections makes the process a breeze.
The online learning resources and tutorials are helpful as well for those who are tech savvy.
While the DB integration is broad (many connectors) it isn't particularly deep. So if you need to do serious DB work on (for example) SQL Server, it is sometimes necessary to go directly to the SQL Server Studio. But for general access and manipulation, it is ok.
The syntax formatting is sometimes painful to set up and doesn't always support things well. For example, it doesn't effectively support SCSS.
Using it for remote debugging in a VM works pretty well, but it is difficult to set up and there is no documentation I could find to really explain how to do it. When remote debugging, the editor does not necessarily integrate the remote context. So, for example, things like Pylint don't always find the libraries in the VM and display spurious errors.
The debugging console is not the default, and my choice is never remembered, so every time I restart my program, it's a dialog and several clicks to get it back. The debugging console has the same contextual problems with remote debugging that the editor does.
I love this product, what makes it one of the best tool out in the market is its ability to function with a wide range of languages. The online community support is superb, so you are never stuck on an issue. The customization is endless, you can keep adding plugins or jars for more functionalities as per your requirements. It's Free !!!
It has everything that the developer needs to do the job. Few things that I have used in my day-to-day development 1. Console output. 2. Software flash functionality supporting multiple JTAG vendors like J-LINK. 3. Debugging capabilities like having a breakpoint, looking at the assembly, looking at the memory etc. this also applies to Embedded boards. 4. Plug-in like CMake, Doxygen and PlantUML are available.
PowerApps is a great solution and I have spent the last year familiarizing myself with the platform and building custom applications to complete a whole range of tasks such as asset management, custom invoice generation, and item restriction tracking. We as a company have barely begun to scratch the surface of what can be achieved with PowerApps.
I gave this rating because Eclipse is an open-source free IDE therefore no support system is available as far as I know. I have to go through other sources to solve my problem which is very tough and annoying. So if you are using Eclipse then you are on your own, as a student, it is not a big issue for me but for developers it is a need.
The community forums are extremely responsive to questions asked, there is a good body of online documentation and many community posts to draw from. Although the platform has changed, which means some of the posts are out of date and the solutions provided aren't relevant. Of relevance, I read over 400 articles plus documentation to get this first app built in SharePoint, move it to SQL and make it work exactly the way it should.
The installation, adaptability, and ease of usage for Eclipse are pretty high and simple compared to some of the other products. Also, the fact that it is almost a plug and play once the connections are established and once a new user gets the hang of the system comes pretty handy.
Much cheaper, much more customizable, and easier to use. There is not much of a learning curve and the licensing cost is much cheaper. PowerApps does one thing very well, whereas other platforms are mediocre. There is much more customization possible for your in-house workflows that you can build yourself vs using NetSuite engineers to build it for you.
This development environment offers the possibility of improving the productivity time of work teams by supporting the integration of large architectures.
It drives constant change and evolution in work teams thanks to its constant versioning.
It works well enough to develop continuous server client integrations, based on solid or any other programming principle.
It has given us a focal point for development. We now have the possibility of connecting to mobile and the default SharePoint online interface isn't always easy to manipulate. PowerApps has given us an opportunity to improve our user experience.
An improved user experience has given us a better shot at compliance. When users don't fight the environment, they don't gravitate towards workarounds or non-compliance.
As lists and libraries change, the platform scales pretty well.
Having users with the capability to create their own forms and tools has dialed back the app dev need (there is a balance though) and distributed power to the process architects and people who actually need the solutions in the first place—much more efficient model of service delivery: self-service.
