So, welcome to the 19th edition of developer news.
I have a mix of items this week, from tools to open source to production issue analysis, so I hope you find these useful.
1 : href tools
First up is a site for web developers that has been shared a fair bit this week. It’s a site called href tools and it’s a collection of browser based tools to help web developers. It tools like HTML/CSS/JS compression, base64 image encoding and a couple of JSON related tools.
It’s still a work in progress by the look of it, but there are a couple of useful tools there.
If you are looking for other similar tools, then CyberChef is a site that has a much more extensive range of browser based dev tools, useful not just for web development.
2 : Browser based .NET apps with Blazor
This item is an experimental project from Microsoft’s ASP.NET team. It’s a web framework based on C#, Razor, and HTML that runs in the browser via WebAssembly.
I’ve done a reasonable amount of .NET development in the past, not so much recently, but it still does come up now and again. It’s interesting to see that there are still innovations by this team, looking to make the most of the continual developments in browser tech.
There is a great write up in their announcement with good details on the tech and also motivations for this project.
3 : Perspective
Next, we have a project that has been recently open sourced named Perspective. It’s from one of the dev teams a JP Morgan Chase, and like the Blazor project mentioned above, also makes use of WebAssembly in the browser.
This project is a streaming data visualisation tool designed to enable real time user configurable visualisations in the browser.
These are something that are notoriously hard to great right in a way that can actually perform with any significant data sets, so I’m looking forward to giving this a go on some test data.
4 : Epic fail?
Finally for this week, a post mortem of an issue that Epic Games encountered.
The encountered a service outage when one of their games hit an issue with 3.4 million concurrent players.
That’s a big number, but their article goes into a great level of technical details as to what the issues were, how they manifested and also what was required in order to address any scaling and performance issues.
As I have said before, I think there is a lot be learned from any situation like this, even if you aren’t operating at that kind of scale.
So, that’s it for this week.
If you have any articles, announcements, tutorials, or anything else you think should be included next week, then just drop me an email.