XCSoar VS tasks

> Would you consider adding a kqueue implementation?

Can't do, I don't have Apple or BSD anywhere. But if code for it were submitted to me, I would gladly merge it (and try to keep the CI happy).

The MPD version of the event loop is portable and runs on macOS/BSD/Windows, but no kqueue, only poll() (and select() on Windows). This old-school API has its scalability problems, of course, but that matters not so much for MPD.

The event loop can already do Coroutines on all supported targets; here's another open source project where I use this library: https://github.com/XCSoar/XCSoar/tree/master/src/event/ - it's a flight computer (yes, for real airplanes) which also runs on Windows and macOS and iOS, and runs libcurl (and other stuff) as coroutine.

If you want to use my library and need help with integrating it or with adding kqueue support, get in touch with me.

In the unpowered flight world the most common foss navigation app is xcsoar: https://xcsoar.org/

It's probably because of some changes to the way application data in Android works now. There is an issue written up on the XCSoar GitHub here that describes the problem.

XCSoar 7.11: Tactical glide computer and maps

I'm curious, did you mean https://tasks.org/ or something else?

Kalender mit CalDav und der App "Tasks" auf Android

Tasks.org: Open-source To-Do Lists & Reminders (version 13.6): Fork of Astrid Tasks & To-Do List

tasks for Tasks.org mobile

I thought it was a great idea to find out how certain features are implemented in other people’s projects. I know two open-source apps that are similar to what I want to build: uhabits and tasks.org.

I think it really depends on what your definition of "productive" is.

Let me try and quantify it. I looked through my apps that I installed from F-Droid, then looked at their GitHub issues and picked one [0]. I bet I could implement that in less than a week with 0 Android development experience.

> Every Android version is basically a reboot in many parts of the framework, the device fragmentation is hardly any better than J2ME days, several features are only documented via samples or Google IO talks, Gradle plugins require rewrites between upgrades, and each Android Studio release is a box of surprises what quirks it has.

Does any of that really matter if you're hiring someone into an existing org? Doesn't Android have amazing backwards compatibility? I'm sure I have some dice app from 2012 that still runs. The company is probably targeting some version of Android and isn't changing to the latest one every time a new version is released.

[0] https://github.com/tasks/tasks/issues/2435

Edit: and neither do some other features such as 'Filters'. I was aware that some of the features would not sync since that was mentioned in the tasks.org website. But I did not expect this to happen since the website specifically says that tags are synced with DecSync CC.

I just kept bringing up replacing Synology with Nextcloud because of the reminder sync issue and the superior web app. If you don't rely heavily on reminders then its not a huge deal. You can read more about this at https://github.com/tasks/tasks/issues/1802

I've been trying out a TON of GTD-related apps over the years and recently settled on tasks.org to complement Google Tasks. Honestly, this is an amazing app, but it lacks features that I really want: A Web interface and integration with other applications. Then a week ago, I moved to Todoist, and while it worked great and provided much of what I wanted, its free account limitations were apparent. Bummer, as I didn't want to pay what they ask for a premium account.