
I must admit, I love SE80. I enjoy the familiarity and native integration SE80 provides. That said, there's a growing number of developers who are using VS Code for ABAP development. VS Code is a free source code editor that allows offline editing and most importantly, you do not need access to an SAP system.

## Features of SE80
When it comes to the good stuff, SE80 is like that trusty old Swiss Army knife you can't imagine going camping without. Its seamless integration with SAP systems means you get direct access to all the ABAP-specific tools and nearly all the objects you'll ever need, with a few exceptions like CDS. You've got everything from code completion to debugging features, right at your fingertips. And let's not forget the comfort of working within an environment that's custom-built for SAP—talk about a dream workspace for any ABAP developer!

But it's not all sunshine and rainbows. SE80's design screams "vintage," and not in the cool, retro way. Its user interface could use a facelift, and its functionality, although robust, feels somewhat stuck in the past compared to modern IDEs. While it offers some level of version control, it's not nearly as flexible or user-friendly as what you'll find in newer development environments that leverage Git. So if you're the kind of person who likes their tools to be as cutting-edge as the code you're writing, SE80 might leave you wanting more.

## Features of VS Code with abaplint
While VS Code was initially not focused on ABAP development, the open-source nature of the platform has allowed for the development of extensions tailored to ABAP. This has opened the door for SAP developers to enjoy a more modern development environment with features like Git integration, numerous extensions, and the ability to customize almost every aspect of the editor.


### Leverage extensions
For ABAP development in VS Code, the [ABAP remote filesystem](https://marketplace.visualstudio.com/items?itemName=murbani.vscode-abap-remote-fs) extension allows you to connect to an SAP system, work on ABAP code, and even debug it. The [abaplint](https://marketplace.visualstudio.com/items?itemName=larshp.vscode-abaplint) extension is another gem—it's a linter for ABAP, providing instant feedback and suggestions to improve your code. Both of these extensions significantly enhance the ABAP development experience, offering functionalities that are not readily available in traditional SAP environments like SE80. The availability of such extensions has created an increasingly compelling case for considering VS Code as a viable option for ABAP development.

### Local development with offline access
It's especially handy for open-source development, where developers often don't have access to ABAP systems. Yep, you read that right—you don't need a connection to an SAP system to work on ABAP code. Thanks to abapGit, ABAP development has been decoupled from an SAP system's database. This lets you edit code locally and then push your changes to a Git repo, where it can go through a CI pipeline.

> ### Stay in the loop! Subscribe now for the latest updates. 📩
> <SubscribeForm />

## Comparing costs and setup
SE80 of course requires SAP GUI and an SAP system. This has become more accessible with the re-release of [ABAP Platform 1909](/blog/getting-started-with-the-abap-platform-trial), but the system requirements are still quite high, making it [difficult for everyone to run it](/pricing/personal). In a traditional business setting, the developer doesn't have the burden of costs so it's typically not an issue. Similarly, the setup of SAP GUI is likely to be the responsibility of corporate IT so it's not an effort on the developer.

However, for personal projects or contributing to open source, SE80 may be unavailable. In this case, even with its limitations, VS Code is a suitable option. In fact, the limitations may even be a good thing as it then allows for using abaplint to ensure the syntax is compatible with all versions of SAP BASIS 702 or higher. It does require additional setup on the developer's part but it's a mature enough tool that this can typically be done in a few minutes.

## Key takeaways
SE80 is still the best option for native integration with an SAP system and ideal for developing business features, particularly those that are deeply embedded in standard SAP. However, in some cases, particularly for open source contributions, personal development, or offline access to edit ABAP, VS Code is a great option. 

Ultimately, the key is giving developers the flexibility to choose whatever tools they prefer to optimize the developer experience.

As for me, perhaps it's that old habits die hard but I'll stick with SE80.


Who wins the ABAP showdown?

Comparing SE80 and VS Code for ABAP development, weighing features, costs, and flexibility.

Visual Studio Code vs SE80

Related posts

Smart automation, smarter cost management

SAP #ABAPfails

A modern branching strategy for SAP