Scoopta

Lemmy is rust and it's alternative sublinks is java...your comment has now power here

While this functionality is proprietary to Nvidia ray tracing isn't and since RTX is just nvidia's brand of ray tracing your statement of RTX being proprietary isn't wholly accurate.

As a fan of tabs I see this as an absolute win

I choose option C, eclipse xtext

This post has too many down votes for the quantity of anime in it

Ah, I've only had one guild require it and I told them to fly a kite XD...I thought this was becoming a general thing and I was going to be really annoyed

🤔...is this a new requirement? I have 2 accounts. Neither with phone numbers and it's never asked me for one

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.

I've thought sublinks was really cool, a lot of which because it's Java and I feel like modern Java doesn't get the love it deserves...but I am worried about it not being AGPL. At least for me the fact that Lemmy couldn't have it's codebase closed was a large appeal and this move doesn't sit well since it would allow instances to close source their backeds if they wanted to. I feel like AGPL is a requirement for user freedom with websites as it's the only open source license for the web.

When script kiddies are the new high we've collectively reached a new low

I do this in my code because it looks better and makes more sense...until I decide to declare 2 vars on one line and then I use the very cursed int* a, *b