tasks VS obsidian-releases

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.

The closest editor that follows our first principle is Obsidian editor:

The solution was already installed on both my computer and my phone: Obsidian.

> why does open source need to "win"

Open source does not need to win.

But your ability to be in control of your computer needs to be preserved. A proprietary fridge cannot control your diet, while a proprietary App Store can control what software you install on YOUR phone (unless you live in EU, hello DMA!). The tail wags the dog, so to speak. Proprietary software has also been shown to break user workflows or remove functions in an update while leaving users with no choice whatsoever.

One alternative to having open source win is to ensure software must come with a robust warranty and other assurances you expect from the things you buy. EU's CRA will make software vulnerabilities in WiFi routers covered by warranty, for example.

You can also ensure robust and interoperable data storage options. For example, https://obsidian.md/ stores all notes in Markdown, not holding the data hostage in case users will not like how future versions will work. GDPR actually has a provision for data portability (Art. 20), but it does not seem to have a requisite effect on the industry yet.

And until the above issues are solved, open source remains the best way to ensure that a software tail cannot wag your computer dog.

[2] https://obsidian.md/

So I've had my fair share of personal websites and blogs. I have built them on stacks ranging from the most basic HTML and CSS, to hosted frameworks like Wordpress and Laravel, to the more modern single page applications built in Vue and React. For a simple content blog I think you can't go wrong with a Static Site Generator though. These days I am almost exclusively writing everything in Obsidian. Which is great because its all in standard markdown format. This allows for a really neat and easy content publishing workflow.

Consider making an Obsidian[^1] plugin, or writing to Obsidian-compatible Markdown files :)

[^1]: https://obsidian.md/

Obsidian is a writing application created to allow for offline / private note taking in markdown format, in an interface that looks a lot like our regular programming IDE. It is very flexible, with a good collection of community plugins that you can use to customize Obsidian to your heart contents.

Obsidian support via our Obsidian Plugin

Thank you!

In the beginning, I used kognise'z water.css [1], so most of the smart decisions (background/text color, margins, line spacing I think) probably come from there. Since then it's been some amount of little adjustments. The font is by Jean François Porchez, called Le Monde Livre Classic [2].

I draft in Obsidian [3] and build the site with a couple python scripts and KaTeX.

[1] https://watercss.kognise.dev/

[2] https://typofonderie.com/fr/fonts/le-monde-livre-classic

[3] https://obsidian.md/