Supabase vs. Microsoft Visual Studio

Supabase can be used for strong custom backends for games and full-stack web applications. Self-hosting is not as great of an option just yet, and Supabase is still being developed actively so there are still legitimate problems that can be encountered, but this project seems to be going in a positive direction and has been useful for us.

Incentivized

It's useful for app development, debugging, and testing. I've been using it for two years and have seen it grow into a fantastic tool. All of the features, NuGet packages, and settings that enable different types of projects are fantastic. It also has a connection to Azure DevOps and Git. It's a fantastic product that's simple to use.

• Getting up and running quickly and cheaply
• Edge functions
• Flexibility with login options
• Data GUI
• Settings GUI

Incentivized

• Rock solid intellisense. For C# and VB.Net code, the intellisense provided by Visual Studio is hands down the best. If you find that you have a hard time remembering parameters of functions, or what object names were, the intellisense will rescue you and help me be an efficient developer.
• Super fast and simple to use debugger for C# and VB. Everything in the debugger is handed to you on a silver platter. When you stop on a break point, it immediately shows you the local variables, the call stack, and even your current memory usage. Setting up watch variables is super simple and you can even make breakpoints conditional so it will only stop on certain conditions.
• Hides the tedious tasks. There are quite a few things like publishing, creating click once deployments, and adding/removing settings in the project files that can be really time consuming when trying to do it by hand (such as if you don't have access to Visual Studio and you need to make changes). Visual Studio hides all the tedium from you by making nice point and click interfaces to get things done quickly.

Incentivized

• The policies preventing turning off a server are nonsense
• On a lower pricing tier, reaching a usage limit can prevent setting modification to go back under that usage limit
• It's still in beta, so use in production can be problematic at times

Incentivized

• Certain settings and features can sometimes be challenging to locate. The interface isn't always intuitive.
• Sometimes there are too many ways to do the same thing. For example, users can quickly add a new workspace in Source Control Explorer when a local path shows as "Not Mapped," but it doesn't indicate that the user might want to check the dropdown list of workspaces. The shortcut of creating a new workspace by clicking on the "Not Mapped" link can lead to developers creating too many workspaces and causing workspace management to become unwieldy. If the shortcut link were removed, the user would be forced to use the Workspace dropdown. While it can add an extra step to the process, workspaces would be managed more easily, and this would enforce consistency. At the very least, there should be a high-level administrative setting to hide the shortcut link.

Incentivized

VS is the best and is required for building Microsoft applications. The quality and usefulness of the product far out-weight the licensing costs associated with it.

Incentivized

It still takes some ability to be able to use all the features, but you may not need to use all the features. Even though a lot of Supabase is straightforward, you will still want experienced backend developers working with this tech. I wouldn't recommend having frontend specialists deal with this much.

Incentivized

The thing I like the most is Visual Studio doesn't suffer from Microsoft's over eager marketing department who feel they need to redesign the UI (think Office and windows) which forces users to loose large amounts of productivity having to learn software that they had previously known.

Incentivized

Between online forums like StackOverflow, online documentation, MSDN forums, and the customer support options, I find it very easy to get support for Visual Studio IDE when I need it. If desired, one can also download the MSDN documentation about the IDE and have it readily available for any support needs.

Incentivized

The extent of the options offered by Supabase far exceeded other similar products we've tried in the past. Also, their documentation has been excellent for us. Self-hosting is not what it's cracked up to be, but that's usually the case with these kinds of tools, anyway. I don't know anyone else I've talked to about Supabase who self-hosts, either. For something super micro small, Pocketbase is genuinely self-hostable, but it's been best for prototypes and proofs-of-concept, perhaps not with something expecting a lot of users. That's where Supabase's scalability and flexibility become more valuable.

Incentivized

I personally feel Visual Studio IDE has [a] better interface and [is more] user friendly than other IDEs. It has better code maintainability and intellisense. Its inbuilt team foundation server help coders to check on their code then and go. Better nugget package management, quality testing and gives features to extract TRX file as result of testing which includes all the summary of each test case.

• Gave us a scalable system to reduce a client's backend costs by over 75%
• Allowed us to get a custom backend up for an internal plugin in half the time we originally expected

Incentivized

• Using the integration between Visual Studio and our source control service, the cost of re-work and losing code is drastically reduced.
• Paid versions of Visual Studio enable developers to be so much more productive than hacked-together open source solutions that it's hard to imagine developing in Windows without it.
• When combined with support subscriptions and the vast array of free online help options available, Visual Studio saves our developers time by keeping them coding and testing, not wasting their time trying to guess their way out of problems or spend endless hours online hoping to find answers.

Incentivized