A review of browser IDEs
How well do they stack up against desktop IDEs?
When should you use a browser IDE over a desktop IDE? It really depends on what type of project you’re building and how you plan to build it.
Flexibility and customization
The main advantage of a browser IDE is its flexibility, allowing users to code from virtually any device with an Internet connection. For developers working on collaborative projects, this adaptability can make browser IDEs appear very attractive.
Furthermore, browser IDEs are standardized across all these different devices. This means that every person on a development team will see the same code and output. This prevents issues that may arise when using a local machine or desktop IDE, where users may have configured their environments differently.
However, this uniform set up discourages customization, which is one of the advantages of the desktop IDE. This presents challenges for developers who may prefer modifying their environment with plug-ins, add-ons, themes, user scripts, etc.
On the flip side, the simplicity of browser IDEs is an advantage for beginner programmers who would otherwise feel overwhelmed with so many modification options.
Internet dependence
Of course, the browser IDE’s reliance on an Internet connection can create significant drawbacks as well. In particular, developers using a browser IDE may experience lag or slow speeds while coding, especially if they are using a busy network. In these instances, desktop IDEs are a much better choice.
Yet, using a browser IDE can save space on your device since developers won’t need to install any software that would be required to run a desktop IDE.
Despite these types of benefits, it is clear that browser IDEs cannot match the speed or customization features of a desktop IDE. Compiled with the browser IDE’s offline incompatibility, desktop IDEs are generally the superior development decision.
Still, there are exceptions to this rule and, as browser IDEs continue to improve, their future looks increasingly optimistic.
What’s up with repl.it?
Based on my own hackathon experiences, there has been one select browser IDE that is used very consistently: repl.it.
Personally, I find that repl.it can be an extremely useful tool because of its sheer convenience and collaborative features. Working with repl.it in a group is very straightforward and I find that using the IDE continues to work well for my own purposes.
On the other hand, one of the major downsides I have encountered is repl.it’s downtime issues. Fortunately, repl.it doesn’t regularly have these problems, but in the context of a hackathon — where time so precious — suddenly being unable to access your code is beyond frustrating.
In short, repl.it, and other browser IDEs like it, still have a long way to go to match the power of a desktop IDEs. Nevertheless, there are clear benefits for using either type of environment, and deciding which environment to use truly boils down to a developer’s personal preference.
Buckley, Ian. “The 13 Best Browser IDEs Every Programmer Should Know About.” MUO, MUO, 15 Feb. 2021, www.makeuseof.com/tag/programmer-browser-ides/.
Radcliffe, Tom. “Performance vs. Convenience: Desktop or Browser-Based IDEs?” JAXenter, JAXenter, 29 Aug. 2016, jaxenter.com/performance-vs-convenience-desktop-or-browser-based-ides-128785.html.
