Early Twitter was an adventure. Every day was an open question: would you be able to log in or did the next big story crash the platform? It was taking off and crashing and flying and crashing again. All in real time. It was an exciting time for the internet, and while everything has changed since then it got us thinking: why did we used to tolerate stuff just not working? And why do we still tolerate stuff not working?
If you’ve spent any amount of time in the.NET / Microsoft developer ecosystem, you’ve probably heard the term “NuGet” in reference to code packages, package managers, software libraries, and even software installers. Understandably, this can cause a lot of confusion around what NuGet actually is.
This is one of a series of blogs in which we introduce AppScope 1.0 with stories that demonstrate how AppScope changes the game for SREs and developers, as well as Infosec, DevSecOps, and ITOps practitioners. In the coming weeks, Part 2 of this post will tackle another Infosec use case. If you’re in Infosec, at some point you’ve doubtless had to vet an application before it’s allowed to run in an enterprise environment.
Have you found yourself asking this question when seeing website monitoring solutions flash up on Google? Has your dev team been trying to convince you to get a monitoring tool but you’re not sure what the benefits are? Don’t worry, I’ve compiled a list of the top reasons why website monitoring is so important to you and your website. But you don’t have to take my word for it, read on and find out.
There are multiple reasons why Java and the Java Virtual Machine-based languages are very popular among developers. A rich ecosystem with lots of open-source frameworks that can be easily incorporated and used is only one of them. The second, in my opinion, is the automatic memory management with a powerful garbage collector. The Java garbage collector, or in short, the GC, takes care of cleaning up the unused bits and pieces.