This problem is now solved for me. I didn’t do anything. Either a Firefox (current version 137.0.2 on mobile) or a Lemmy update (current version BE: 0.19.11) seems to have solved it.

I would stay away from YAML (almost at all costs).

For us to be able to help you, I think you need to give us some more details about the organization of your work. If each chapter is a separate text file, then you don’t really need to do any branching at all (assuming people will only make changes on their own files and not touch others’ work). If it is a single text file, branching (or anything else, to be honest) will not help much.

I assume chapters will have their separate files. As long as you can control who touches which file, everybody can work on the same branch (also referred to as “trunk based”). But if you fear that people may interfere with each other’s work (willingly or by accident), then it makes sense to create a branch per chapter to keep contributors at a distance from each other. But working on a single repository requires some sort of an agreement on the workflow.

I have the same problem on mobile Firefox on Android. I’m using the default frontend as well. This was not happening a week ago (or maybe 10 days). Started recently.

This is an acknowledgement from Uncle Bob that the book didn’t stand the test of time. We won’t know before the new edition is out, but I suspect those pointless refactorings will not be in it any longer.

Don’t they already have the names Leap and Tumbleweed? Changing the name to Leap would make sense since it’s the name of the “official LTS” version. At this point it sounds like “openSUSE” is the name of the project and not the distro. But I haven’t been following them closely, so perhaps I’m wrong.

Not sure but that sounds like you have a problem with your Git installation (or a dependency of Git). Maybe a reinstallation can solve that.

I understand the “why would I pay for this” reaction. I think crowdsourcing is a better approach for these kinds of content. Once you reach certain level of financial commitment from the crowd, you can give away the PDF and sell the print copy.

git branches are just homeomorphic endofunctors mapping submanifolds of a Hilbert space

Yeah, once you realize that everything falls into place.

Here is the link to the original website (an NGO that monitors blocked websites in Turkey): https://ifade.org.tr/engelliweb/distrowatch-erisime-engelledi/

And here is the Google translation of the text on that page:

The IP address of the DistroWatch platform, which provides news, reviews, rankings and general information about Linux distributions, was blocked by the National Cyber ​​Incident Response Center (USOM) on the grounds of “IP hosting/spreading malware”.

I think you are highlighting an important point that are missed by other commenters emphasizing the developer. I prefer GPL over MIT license. But this is a possible fallback if Redis decides to change its licensing (like several others did).

I think these kind of products have strategic significance for MS for their Azure offering. They are probably preparing to offer this there (in addition to and as an alternative to Redis). So, it makes sense for Microsoft to release this with an OSS license (otherwise no one will adopt it).

I don’t think I read that one. I created a separate link-post for that one. Thanks.

I mainly develop in C#, and I agree that having to write so much boiler plate for type safety is really boring. C# is not perfect either (it doesn’t have discriminated unions, etc.) but at least it gives type safety out of the box.

However, in general, I think enums are widely misused. I see a lot of cases where they should have been classes with a factory, but ended up being enums with a lot of static functions and switch statements.

Who is this particular developer

As far as I understand from the discussions about the topic, Maxim Dounin was one of the few core developers of nginx. Looks like Wikipedia has already been updated.

The URL seems to have a typo. Correct URL is https://github.com/presslabs/gitfs

https://www.docs.bsky.app/blog/feature-bridgyfed

When I joined some years ago, it automatically created a private, invite-only room named “Echo Chamber” with me being the single member. If it didn’t happen to you automatically, you can create one yourself.

Sounds like a good plan, thanks!

I would be interested in this, but I’m on this side of the pond. So good luck! Would be good if you made the recordings available afterwards.

deleted by creator