• 0 Posts
  • 24 Comments
Joined 2 years 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.











  • It’s how I intuitively read it too, even after decades of being exposed to tech, software, and licenses.

    There’s the OSI Open Source Definition, which is a free software definition.

    I think the free terminology is clearer because free as in beer vs freedom is more obvious. Either it has a price or it doesn’t. The Libre term is rather common alternative because of the ambiguity. The free as in beer or freedom is a common easy to understand explanation.

    There’s no such things for open source. In my subjective experience at least. “Source available” did not establish like Libre. Open is way more broadly ambiguous than free. And whether a license is open or open needs a full understanding and interpretation rather than only 'does it cost or can I use it for free.

    Free is a dualist ambiguous differentiation. Open is broadly ambiguous and hard to verify.





  • I’ve read about someone’s experience once that less detailed release note releases are more likely to be approved by store moderation without issue.

    It’s probably more laziness / not seeing enough value in it though.

    I see lacking release notes everywhere - in many projects.

    Sucks when you’re trying to asses necessity, risks, and changes of updates of apps, service infrastructure, or libraries.

    Good release notes are not hard if you have a good workflow. At my work project it’s basically automated generated - thanks to a deliberate and conventional commit workflow.

    But few people see the need, the value, or have the initiative and thoroughness that would establish it.




  • It’s not a what-you-see-is-what-you-get editor website builder like OP seems to ask for. You definitely need some editing or at least Markdown markup.

    But I personally can recommend getting into that.

    If it’s mostly about the content and text content Hugo may be a very good option and starting point into website creation/development. Because it generates static webpages it can be hosted for free too - e.g. on GitHub pages.

    If they want to play around, move and modify the layout and positioning though they’ll have to dive at least a little bit into HTML and CSS, or use a different tool.