Kogasa

Yes, with Iosevka font

Being suitable for human consumption doesn’t mean it’s not also suitable for playing a role in a more efficient food chain

Stokes’ theorem. Almost the same thing as the high school one. It generalizes the fundamental theorem of calculus to arbitrary smooth manifolds. In the case that M is the interval [a, x] and ω is the differential 1-form f(t)dt on M, one has dω = f’(t)dt and ∂M is the oriented tuple {+x, -a}. Integrating f(t)dt over a finite set of oriented points is the same as evaluating at each point and summing, with negatively-oriented points getting a negative sign. Then Stokes’ theorem as written says that f(x) - f(a) = integral from a to x of f’(t) dt.

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.

Shoutout to my fort myers and cape coral homies

Hom functors exist for locally small categories, which is just to say that the hom classes are sets. The distinction can be ignored often because local smallness is a trivial consequence of how the category is defined, but it’s not generally true

You can get blight free versions of JavaScript too, if you use TypeScript.

In a hypothetical and highly unlikely world where everyone had to pay Oracle to use Java, everyone would switch to something else. It would be guaranteed suicide. Anyway, in that world, they would need to both make this ridiculous decision and win an unwinnable legal battle afterwards. It’s not a realistic concern.

3 billion devices

What’s the lockin? Is it really harder than just swapping the jdk path to switch between Coretto and OpenJDK? I understand Coretto being preferable for performance and security patches but I don’t imagine it’s that big of a deal if one eventually had to switch

Didn’t ask

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 cow, enjoy

Reminds me of 2048 making a slightly worse clone of Threes and then releasing it for free.