• 2 Posts
  • 257 Comments
Joined 1 year ago
cake
Cake day: April 19th, 2023

help-circle
  • It is.

    Blazor is a big framework. It gives you a lot, but as a framework, also introduces stack complexity.

    Being able to code on one C# codebase for a web application client and server is great. It’s very fast. You can use modern C# syntax. You have component (CSS) isolation. You can switch and mix between runtime targets (server dom rendering and sending diff-updates or client-side app execution).

    At work, we’re using it for a webportal/webapp and I have not fundamentally regretted us using it. It’s definitely not worse than anything else. For a productive development and product there’s a little bit of framework knowledge you have to learn, but that’s not different than any other framework. And docs are very good.

    I love how fast it feels to use the end product too.


















  • I can’t get what it describes through all the Jedi stuff and jokes.

    One mentor and one apprentice? And everything else remains unspecified and open?

    For FOSS, as it is described, it makes me think it’s a big investment with unclear risk (will they even stay as a contributor?). Which of course can be contextualized - but then what is left here?



  • I sometimes do things (cleanup, refacs) off-ticket / not part of the ticket. It can be a light alternative when other stuff is complicated and demotivating. Depending on your environment and team/contract setup, simply doing it could be more difficult though.

    If it serves your satisfaction and productivity, and is good for the product, then it’s not wasted. Not everything has to be - or even can be - preplanned.