Some IBM i Bloke
I Prefer VS-Code over RDi
"I stand with both feet firmly in the VS Code for IBM-i camp. I used RDi for a several years, then along came VSCode and upgraded my expectations. Having said that - I had to add a section on RDi to the IDE Course for your reference. Try both and decide which experience fits you better"
Why VS Code Beats RDi for Modern IBM i Development
RDi has served IBM i developers faithfully for years — but times have changed. Modern workflows demand speed, flexibility, and integration with open‑source tools. Enter Visual Studio Code, the lightweight IDE that’s redefining how we build, test, and deploy on IBM i.
RDi still shines for legacy teams and deep Eclipse integration, but VS Code is the future.
Rdi feels clunky while VS-Code is agile, extensible, and developer‑friendly. It’s the IDE that makes modernization fun again.
Core Difference: Architecture VS-Code vs RDi
|
|---|
Developer Experience
VS Code fits naturally into modern DevOps pipelines - GitHub, CI/CD, Docker, and open‑source tooling. RDi, while powerful, is siloed and slow to adapt to collaborative workflows.
Why Developers Are Switching
- Modern Workflow: VS Code integrates seamlessly with GitHub, GitLab, Jenkins, and open‑source libraries.
- Code for IBM i Extension: Compile, upload, and debug directly on your IBM i system with no clunky remote setup.
- TOBi & Source Orbit: Automate builds and manage dependencies intelligently.
- Db2 for IBM i Tools: Edit SQL and browse schemas inline.
- Lightweight & Portable: Works on any OS, ideal for hybrid teams and remote development.
Bottom Line
VS Code wins on speed, flexibility, cost, and community innovation. RDi still has value for legacy teams who rely on its Eclipse‑based tooling, but for modernization, teaching, and agile development, VS Code is the clear future of IBM i programming.
Having said all that... let's look a few RDi components in the next lessons so you can make your own mind up!