7 ms·
One step closer to Linting as a Service. That'll be next, along with Compilation/Build Systems as a Service. Or more likely part of the whole IDE moving to the
by jameslk 6y ago
One step closer to Linting as a Service. That'll be next, along with Compilation/Build Systems as a Service. Or more likely part of the whole IDE moving to the cloud.
The pain being solved here is that setting up the right development environment is hard, especially for those still learning to program. Many would be much more productive if we skip this step.
Another prediction: Once the development environment moves to the cloud, it will be tied directly to the deployment to a specific platform, such as Azure if this is offered by GitHub. Then Amazon and Google will have to build their own IDEs in the cloud to compete. We'll no longer be developing locally but in the browser, and it will cost a lot more.
- throwaway43234 6y agoGitHub Codespaces was announced at Satellite and it's basically what you say - a way for developers to skip the "setting up" step (often the most annoying step and single biggest blocker for OSS contributions) in a new repo. https://github.com/features/codespaces https://github.com/features/codespaces Disclaimer, I helped make these :)
- jameslk 6y agoInteresting. Yes this is definitely in the direction I was thinking. I'd also say Repl.it is very similar too. Maybe they'll be acquired.
- rckoepke 6y ago> I'd also say Repl.it is very similar too. Indeed. It's interesting that GitHub Classroom uses Repl.it (and another MS web IDE) rather than Github Codespaces: https://github.blog/2020-05-26-code-in-the-browser-with-github-classroom/ https://github.blog/2020-05-26-code-in-the-browser-with-gith... https://classroom.github.com/help/online-ide-integrations https://classroom.github.com/help/online-ide-integrations Seems like a friendly ecosystem for the moment.
- oefrha 6y agoAutomated code review SaaS'es (using off-the-shelf linters, and more) have been around for what, a decade, or longer? So this is not "one step closer" to linting as a service.
- deleted 6y ago[deleted]
- jtwaleson 6y agoI fully agree. The "I" in IDE (Integrated) has not aged well, just look at how many parts of the software development cycle are outside of the IDE. It's time to really integrate/bundle everything in a way that makes sense. Things I want in my IDE: - monitoring/alerting (how many times is this method executed, how long does it take, how many errors, etc) - discussions as in Google Docs on code fragments, rather than "comments" that are part of the git history (comments are an orthogonal concern from checked in code) - visual representation of my code base - ultra fast automated test that cover only what I recently changed - a documentation system that makes sense
- jameslk 6y ago> The "I" in IDE (Integrated) has not aged well This such a good observation. I will be using this quote in the future. I've seen what integration of the development environment looks like inside a big company (Facebook) and it's just amazing how seamless everything can be when all your tools are built with an awareness of each other. I think we'll see that soon outside these big companies.