Skip to content
It’s been a long time sine I’ve written a blog post, and I miss it a lot!
Today, I’ll be talking about an experiment I did 2 months ago when I was trying to optimize Blazor.Diagrams: JS Interop Batching.
Context I’ve been working on my Diagramming Library for Blazor for quite some time now, and it basically takes a model (Diagram) that contains multiple nodes, ports and links (which are also models), renders it and makes it editable on the fly.
Figuring out how technologies are made under the hood is one of the things I love to do. Ever since I started using Blazor and going in-depth into its features, I can’t stop wondering how things are made internally.
This post is the start of a series about, you guess it, Blazor Internals.
How to pass values to all children (multiple levels), both in Blazor and React, and what are the differences between the two
There are times where I needed to do some things dynamically and I typically think of Expression Trees to do it. Don’t get me wrong, Reflection does the job most of the time, but it’s known to be very slow in almost all cases. I happen to have a bit of experience in the former.
I was working these days on my library Blazor.Diagrams and I needed to write some documentation to show all the available/possible options. I could’ve done it manually, but there was quiet a few settings and I didn’t want to have to update the table every time new ones are added.
After working with Spring Boot for a couple of months now, one thing that I find lacking in ASP.NET Core (C#) is Aspect Oriented Programming (AOP).
In computing, aspect-oriented programming (AOP) is a programming paradigm that aims to increase modularity by allowing the separation of cross-cutting concerns. It does so by adding additional behavior to existing code (an advice) without modifying the code itself, instead separately specifying which code is modified via a “pointcut” specification, such as “log all function calls when the function’s name begins with ‘set’”.