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.

deleted by creator

I can’t say anything about it’s quality, but Wikibooks has German.

Looks like it may be worthwhile as a or an additional starting resource, but maybe not more.

I actually implemented super tic tac toe in Blazor a while ago. It’s interesting to play.

Why do I not win with a row on the outer field?

It counts won fields instead?

Krita doesn’t have an Android app version though, does it?

yt-dlp supports various sites and authentication options (may have to take over from webbrowser). I don’t see an explicit extractor in the source, but it may work anyway. It’s what I’d try first.

(Aside from the other issues) A DVD may not even retain it for 15 years

https://en.wikipedia.org/wiki/DVD#Longevity

Hardly something to bet on for continued availability.

I’d suspect your VPN is slow before suspecting ISP throttling.

you --> ISP --> target
you --> ISP --> VPN --> target

You’re introducing VPN, with different network routing, and a routing middle-man, and suspect ISP before VPN?

First huzu now suzu. Are we gonna be able to fill the alphabet?

The link offers a download instead of serving an HTML? I’m on mobile Firefox (I doubt it matters).

I don’t think it should be a client feature. It should be federated, like the posts are.

I feel like cross-posts should share comment threads…

Now comment threads are split across 6 communities.

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.

Or Modified Viable/Valuable Product

I don’t have experience with that in particular. I’ll share my more general, tangential thoughts.

MVP is minimal. Extending the scope like that makes me very skeptical (towards scoping and the processes).

Everything you are concerned with would be important topics for retrospectives, or even meetings with management. But of course those don’t exist or are open in all environments. In my team I could openly raise such concerns.

If you’re always rushing to a deadline, or feel like that, think of what you can do and influence to improve that. Retrospectives? Team disuscussions? Partly tuning out of management given focus and doing what you deem important and right? Look for a different team or employer?

https://en.wikipedia.org/wiki/International_Fixed_Calendar

Some sometimes open up for a time.

Remember, when we do that, we are getting a binary file. But in my imaginary example, we are getting a ‘video description’ in form of PostScript.

The example is a reference/link with handling instructions.

When I think of video metadata, we already have and use formats for that, in a more general and versatile manner.

Maybe I’m missing the point, but sending instructions is a very different and restricted approach.

I like that we describe data and how it shall render. That way, the data is accessible for various interpretations and uses.