There’s the horror of scientific software written by researchers I’ll share here. They are fired The contract expires every 2 years and users keep using the code if it’s successful. Some projects are closed source, even…
There’s the horror of scientific software written by researchers I’ll share here. They are fired The contract expires every 2 years and users keep using the code if it’s successful. Some projects are closed source, even…
I understand. I’ve been like you every now and then.
AFAIK after Getting Things Done appeared in the beginning of the email era, nobody found a definitive alternative for 20 years. And the GTD way of doing time constraints is “put it in the calendar”.
While each person has their own way of doing things, I’d be surprised if there were a revolutionary alternative to this.
I’ve tried a range of apps for recurring TODOs. Just use calendar events and fucking do it now was my conclusion.
That can’t be… reads articles this is really bad.
Yet, aren’t they restricting redistribution of non-GPL parts?
I just trying to understand RH’s argument here because so far it sounds like they are blatantly burning down GPL, and I don’t think even RH would do that.
Are you saying that RH doesn’t sell RHL to people who will redistribute the source code of RHL?
And are you saying that it is against the GPL?
Genuine question.
Well, regarding apps I use, they typically have professional testers who find bugs and who are paid full-time to fix them. Interoperability and protocols are respected differently by different projects by FOSS and non-FOSS alike, and they aren’t needed for many apps.
Something suggests me we’re not going to agree, though. I’d appreciate if you further counter my points, but I’m likely not going to agree with you in that case. So, don’t waste your energy.
So, regarding convenience, sadly my apps are mostly non-FOSS. These non-FOSS devs have the advantage that they can see the source code of their FOSS alternatives. They also have FAR more workforce. So, we’ll probably never reach the point where general FOSS is superior to closed source software.
The area that’s primarily FOSS to me is coding. With ChatGPT it’s got damn easy to build daily productivity tools that meet one’s specific needs.
Security is also generally better with FOSS, but, yeah, I admit that the UI is less convenient than the proprietary ones…
So, regarding convenience, sadly my apps are mostly non-FOSS. These non-FOSS devs have the advantage that they can see the source code of their FOSS alternatives. They also have FAR more workforce. So, we’ll probably never reach the point where general FOSS is superior to closed source software.
The area that’s primarily FOSS to me is coding. With ChatGPT it’s got damn easy to build daily productivity tools that meet one’s specific needs.
Security is also generally better with FOSS, but, yeah, I admit that the UI is less convenient than the proprietary ones…
To license what? Code or text? I don’t think either would have enough impact nor adoption.
To license what? Code or text? I don’t think both aren’t going to have enough impact and adoption.
I received downvotes (only) for just reporting bugs and writing feature requests. Although, top posts were always bug reports and feature requests.
Those people are fanboys with no dev experience. I guess they are so insecure they view their favorite app’s potential improvements as threats.
Checks kbin and kbin app status. Sad, but the burnout part is true at least.