Lol, I'm not, I just don't much like animals

Sounds pretty nifty, I'll definitely check it out

8 phone cores are not 8 laptop cores which are not 8 desktop cores but if it meets your use case that's cool. I need more compute then that myself

I'll be honest, I don't get the point of this feature. It's nice for beginners or for writing small, quick, programs...but for the overwhelming majority of all java code I don't see it being useful

I actually had a similar problem with artists with my project. We did eventually find one interested in doing a rev share but it took us quite a while

Wallpaper link?

Lol, yeah but React isn't Linux based so doesn't quite end up so cursed. Last time I played with it it was still really squirrelly.

Because it's fun. As someone who is writing a hobbyist kernel(slowly) it isn't about making a functional OS, it's about learning how systems work and suffering while you do it =D.

I wouldn't classify React as a hobby project per-say. I suppose it is but I put hobby OSes in a category of not having a goal to ever be production ready for anyone outside the developers. Tbh react would have way better compat if they focused on win32 over Linux as opposed to developing NT from scratch but the project is also old enough(1998) to be from a time where Linux wasn't what it is today in terms of wide spread hardware support.

IPvFoo, that extension is installed on every system I have including my phone.

Huh, yeah I suppose that's true. Qubes is an interesting project but I'm not sure it's for me. I selectively isolate apps I worry about using containers, I actually should give flatpak a try as it basically does that for me but I haven't seriously tried it yet.

I replied to lazy guru below but basically I feel as though his argument about stifling innovation is a sorta win some lose some reason and allowing instances to go proprietary isn't conducive to an open ecosystem. Basically the only way as a user to ensure you're not inadvertently running proprietary code you might not want to run would be to host your own instance. Additionally to piggy back on that hosting your own instance might not be as feature complete due to wide spread use of proprietary or custom extensions used by other instances. A Lemmy extension betters the entire Lemmy ecosystem, a sublinks extension only betters the sublinks instance that developed it(unless they decide to contribute it back and hopefully they will)

I would argue that by sharing code it makes everyone more productive because you can borrow code from other places and improve on it rather than having to reinvent the wheel because the plugin you want to improve is proprietary. Anyway that aside my problem with this is on the desktop permissive licenses are fine because the user using the software can choose not to install any proprietary addon's. In the case of the web this is now controlled by the person hosting the service. AGPL ensures that the ecosystem remains open. With a permissive license on the web the only way to ensure an open environment is to host your own instance yourself because you can't control what any other instance does. Personally if I were a Lemmy host I'd use sublinks but I'd always ensure any changes were openly shared since I feel as though that's the only way to be fair to your users...but as a Lemmy user I wouldn't touch it with a 10 foot pole unless it was my own instance since there are plenty of AGPL Lemmy instances to chose from. Lastly GPL does not require you to release your code publicly. The only requirement is that your users have access to it. That means it is fully in license to sell software, the only requirement is that the people who bought your software receive code and are able to redistribute that code. Yes, that is a tad purpose defeating but the official upstream never has to be made public and ultimately people redistribute all kinds of software whether open or closed source, whether allowed by the license or not. As far as I'm concerned if the official version requires purchase most users are likely to pick that over other options. RHEL is a good example of this. AGPL obviously makes everyone visiting the site a user so it's less able to facilitate that but I figured I'd clear up that misconception.

Amusing video covering this topic https://www.youtube.com/watch?v=5VGMdLAKQ0c