Microsoft Visual Studio Code vs. Red Hat JBoss Enterprise Application Platform

As a general workhorse IDE, Microsoft Visual Studio Codee is unmatched. Building on the early success of applications such as Atom, it has long been the standard for electron based IDEs. It can be outshone using IDEs that are dedicated to particular platforms, such as Microsoft Visual Studio Code for .net and the Jetbrains IDEs for Java, Python and others. For remote collaborative development, something like Zed is ahead of VSCode live share, which can be quite flakey.

Incentivized

JBoss EAP is subscription based/open source platform. It's very reliable and great for deploying high transaction Java based enterprise applications. It integrates well with third party components like mod_cluster and supports popular Java EE web-based frameworks such as Spring, Angular JS, jQuery Mobile, and Google Web Toolkit.

Incentivized

• Integrate with the git repository very well.
• Integrated copilot chat is very helpful to write code snippets and helps beginners to start with coding and development.
• Great library of available extensions is one of the best features in Microsoft Visual Studio Code.
• Dedicated Testing option to configure pytest and others are quite handy to use.

Incentivized

• MOD_CLUSTER integration. JBoss EAP integrates pretty well with mod_cluster. This is an intelligent load balancer especially useful in highly clustered environments.
• Supports enterprise-grade features such as high availability clustering, distributed caching, messaging etc.
• Supports deployment in on-premise, virtual and hybrid cloud environments.

Incentivized

• The customization of key combinations should be more accessible and easier to change
• The auxiliary panels could be minimized or as floating tabs which are displayed when you click on them
• A monitoring panel of resources used by Microsoft Visual Studio Code or plugins and extensions would help a lot to be able to detect any malfunction of these

Incentivized

• Difficult to replicate configuration outside of a container environment
• Still requires quite a bit of knowledge of the CLI
• Integration with deployment tools requires CLI knowledge

Incentivized

Solid tool that provides everything you need to develop most types of applications. The only reason not a 10 is that if you are doing large distributed teams on Enterprise level, Professional does provide more tools to support that and would be worth the cost.

Incentivized

We are planning to migrate away from Jboss to Tomcat as Jboss has shown not interest in supporting OSGi which is heavily used at our shop

Incentivized

Microsoft Visual Studio Code earns a 10 for its exceptional balance of power and simplicity. Its intuitive interface, robust extension ecosystem, and integrated terminal streamline development. With seamless Git integration and highly customizable settings, it adapts perfectly to any workflow, making complex coding tasks feel effortless for beginners and experts alike.

Incentivized

JBoss overall is easy to use. The installation and deployment of applications are quick. Documentations and support are also readily available.

Incentivized

Overall, Microsoft Visual Studio Code is pretty reliable. Every so often, though, the app will experience an unexplained crash. Since it is a stand-alone app, connectivity or service issues don't occur in my experience. Restarting the app seems to always get around the problem, but I do make sure to save and backup current work.

Incentivized

Microsoft Visual Studio Code is pretty snappy in performance terms. It launches quickly, and tasks are performed quickly. I don't have a lot of integrations other than CoPilot, but I suspect that if the integration partner is provisioned appropriately that any performance impact would be pretty minimal. It doesn't have a lot of bells and whistles (unless you start adding plugins left and right).

Incentivized

JBoss EAP is lightweight and doesn't really consumes much physical resources. It's high performing and suites well for high transaction Java enterprise applications. The out of box performance settings are not really great and you will have to configure the settings to suite your environment to leverage it's full benefits.

Incentivized

Active development means filing a bug on the GitHub repo typically gets you a response within 4 days. There are plugins for almost everything you need, whether it be linting, Vim emulation, even language servers (which I use to code in Scala). There is well-maintained official documentation. The only thing missing is forums. The closest thing is GitHub issues, which typically has the answers but is hard to sift through -- there are currently 78k issues.

Incentivized

Fast response.

Incentivized

Visual Studio Code stacks up nicely against Visual Studio because of the price and because it can be installed without admin rights. We don't exclusively use Visual Studio Code, but rather use Visual Studio and Visual Studio code depending on the project and which version of source control the given project is wired up to.

Incentivized

We selected JBoss because of compatibility with EJB's. We currently are trying to reduce our footprint and will highly consider using Tomcat.

Incentivized

It is easily deployed with our Jamf Pro instance. There is actually very little setup involved in getting the app deployed, and it is fairly well self-contained and does not deploy a large amount of associated files. However, it is not particularly conducive to large project, multi-developer/department projects that involve some form of central integration.

Incentivized

• Saves money by replacing suites of tools such as Visual Studio, IntelliJ, etc.
• Speeds development time and developer environment setup time
• Strengthens code quality with integrated autoformatting and linting
• Strengths Git practices by keeping version control tightly connected with the code

Incentivized

• Jboss EAP is easy to deploy and configure. This lead to lower cost and faster delivery.
• Even though we have large number of machines running JBoss, we have only two Jboss Administrators. It doesn't requires too much administration and maintenance on daily basis and reduces number of administrators required for large implementations.

Incentivized