It was just over six years ago that Anthony and I first released Glimpse. Since then it’s been a wild ride where we’ve learned a lot, seen a lot and met a lot of great people.
Nearly two years ago Anthony and I joined Microsoft. It was a very exciting time to join, particularly where web development is concerned. Since we’ve been here, Microsoft shipped a new and evergreen browser in Edge. ASP.NET has been completely reimagined into a leaner, more modular, cross-platform and cloud optimized framework/runtime. Azure is growing at a breakneck pace while continuing to support and embrace the open source technologies that so much of the web community thrives on. We really couldn’t be more proud of the work that’s happening here.
In addition, web development paradigms have changed and matured a lot since the early days of Glimpse. Front-end engineering is now a full-fledged practice, and systems leveraging microservices built in cross-platform, polyglot environments are the norm.
Amid all these changes, innovation and excitement, we began to ask ourselves “What does Glimpse, and web diagnostics in general, look like in this new world?” Part of the reason you haven’t heard much from us recently is because we’ve purposefully stepped back to explore how we’d answer this question. However, we’re now at a point where we feel ready to begin sharing more about what we’ve been doing.
In our explorations, we’ve see a lot of Node.js usage for “API glue layers”, along with several challenges with server-side diagnostics in those use cases. We believe we can help solve those problems. As such, our first public announcement is the release of an experiment called “Project Glimpse: Node Edition”. In Project Glimpse: Node Edition we’ve tried to maintain the original spirit of Glimpse as you know it, but we’ve reimagined it as something entirely new that more closely aligns with current web development trends and solves the problems we’ve seen.
Project Glimpse: Node Edition is now live on npm. We can’t wait for you to try it and to hear your feedback. We hope that this experiment will quickly become an indispensable tool for you. As is the nature of an experiment, we expect that we still have a lot to learn and will be pivoting quickly and often based on your feedback, which you can submit at the Glimpse/Home repo.
You may be wondering, “What about Glimpse for .NET?” While we don’t have any announcements to make, I am happy to say that we have been making progress on that front as well. Anthony and I have been quite involved with Diagnostic Source and Activity since their inception, and we see them as cornerstones for a future Glimpse for .NET version. We’ve got a way to go with our Glimpse for Node experiment, but you can rest assured that no matter what happens with it, Microsoft will ship world class diagnostics and debugging tooling for .NET Core.
We appreciate all the support you’ve given us over the years, and are looking forward to our next chapters together making functional, reliable and performant web applications easier to build.
Don’t hesitate to reach out with any questions.