Kogasa
- 0 Posts
- 59 Comments
It’s not correct, and your knowledge of the answers has nothing to do with my explanation.
None of the answers are correct. If the answer were 25%, then it couldn’t be 25% because there’s a 50% chance of picking it at random, which contradicts our supposition. Similarly the answer cannot be 50% because there’s a 25% chance of picking it. The answer isn’t 60% because there isn’t a 60% chance of picking it.
Which is wrong, because you incorrectly assumed there was one correct answer
Being suitable for human consumption doesn’t mean it’s not also suitable for playing a role in a more efficient food chain
Going to almost certainly be less than 1. Moving further up the food chain results in energy losses. Those fish are going to use energy for their own body and such
For sure, which is why I said “another food source would be needed.” I had in mind something like the wild-caught fish being processed into something useful as part of a more efficient food chain, e.g. combined with efficiently-farmed plant material.
Moreover there’s high mortality rates inside of fish farms for fish themselves.
I don’t have any context on the other pros and cons of fish farming, so definitely not arguing whether they’re a net positive or not.
What’s the ROI? If 15% of wild caught fish are used to support fish farms that produce twice as much, it’s not as obviously a bad thing. There’d need to be another food source though.
What you have described is technology beyond the imagination of the men of my time
What century is it
Shoutout to my fort myers and cape coral homies
You don’t need to use the same one. Just don’t expose it publicly in libraries.
It’s a lot better with some notable exceptions. First, .NET Core is multiplatform by design, so it is by default quite portable. The .NET Core CLI is extremely powerful and means a CLI workflow is totally feasible (and also simplifies CI pipelines). The new “multiplatform” application framework, MAUI, runs on Windows, Mac, iOS, and Android, but not Linux/GTK/QT etc. You can maybe attribute this to the design philosophy of abstracting native controls, of which “Linux” itself has none, but either way it’s useless on Linux. Third party frameworks like Avalonia do work very well on Linux.
Despite .NET being relatively friendly with Open Source, Java will probably remain the first choice for FOSS devs for a while, if only due to history and traction. You could write a C# Lemmy alternative, but it wouldn’t necessarily be faster or simpler or better in any particular way than a Java version. I’d certainly rather contribute in Java than start from scratch in C#.
C# isn’t really the go-to for high scale distributed systems. But it’s extremely easy for a small team of developers to set up a really solid service really quickly. I don’t have experience with Go so I can’t really compare, but I find ASP.NET Core very pleasant to work with, and I also appreciate the suitability of C# and .NET libraries for both backend and frontend work.
Nullable reference types are (a completely mandatory) bandaid fix in my opinion as a .net dev. You will encounter lots of edge cases where the compiler is unable to determine the nullability of an object, e.g. when using dependency injection to populate a field, or when using other unusual control flows like MediatR. You can suppress the warnings manually at the slight risk of lying to the analyzer. Objects supplied by external library code may or may not be annotated, and they may or may not be annotated correctly. The lack of compile-time null checking is occasionally an issue. But that said, NRT makes nullability a significantly smaller issue in C# than it used to be
You can also easily write your own option monad or use a tiny library that does.
No but you have 8 boobs like a cat, enjoy
That’s the “naughty” guy from Courage the Cowardly Dog