matcha_addict @ matcha_addict @lemy.lol

Posts

59

Comments

680

Joined

2 yr. ago

Currently, I am storing entities in a JSON array / list. every element in this list corresponds to one instance of that entity.

I could express a many-to-many relationship as just another field in that entity that happens to be a list / array, or I can imitate a SQL join table by creating a separate JSON list to log an instance of that relation.

Are there any benefits to the second approach?

Gitea claims to be working on federation too, which puzzles me that forgejo presents it as a differentiator.

Lemmy is kinda close to forums and groups. But I do agree I prefer that format over the Reddit-like format.

I wish algorithms were opt-in, transparent, and allowed choice (whether by choosing an algorithm over another, or customizing parameters).

If this were the case, I'd have no issue with algos.

Pulling in mainline gitea changes, I did see. But I didn't see any notable differences from gitea. Do you know of any?

Not very clear to me that this is any more valuable than OG NixOS.

This sounds a lot like the forgejo vs gitea fork. I love the forgejo people but I am yet to see a sufficient differentiator.

I like fuzzle as a rofi alternative for wayland. It's made by the same developer as Foot terminal.

Wow this app is amazing! It doesn't have dependent tasks, but it does have sub tasks, which I guess is close. Thanks for the suggestion! :)

Does it sync to an open format so I can manage tasks from Linux too?

Not having the choice is slightly worse I'd say.

Does orgmode have sub tasks and dependent tasks?

Edit: looks like it does. Now figuring out if existing apps support this feature.

Any interesting findings or tl;dr?

You're right, thanks for pointing that out. It does seem that almost no one read to the end, and that's on me.

As long as the keyboard is constrained by your screen size, the ergonomics in typing speed and error rate are far worse than desktop terminal. If the keyboard is not constrained by screen size, like a sufficiently large physical keyboard, by definition that is no longer a smartphone or mobile phone experience.

I addressed the physical keyboard thing one or two comments above, here: https://lemy.lol/comment/9872524

I'm sure it works for you but it's not what I'm looking for

I'm excluding TUI's because you're right, they're pretty different and share some of the ununiformity of GUIs. Still, the command line world remains vast and with that interface you can do a lot, and it is fairly uniform.

there's parameters

That doesn't change the uniformity of the interface. Of course every application will need different parameters. Now do they receive these different parameters via a similar and uniform interface? I say yes. I enter it via keyboard, and for the most part they all use space delimited flags, most of them hyphenated. I'd call that pretty uniform.

To phrase it another way, if all GUIs started using the same names for all parameters, it remains non-uniform interface, and it wouldn't solve 1% of the issue with GUIs.

Out of curiosity, if you don't see the CLI world as more uniform, why do you use it and for what benefit do you prefer it?

Then you're constrained by the screen size, so it's incorrect that you can make it as big as you want.

Despite the smartphone touch interface being worse for these tasks, the convenience of having a phone always with you and within a couple seconds of reach is a big benefit. It would be really nice if the interface could be made easier

Edit: sounds like you meant software keyboard. That is constrained by screen size and hence cannot be as big as I want.

Below is my original comment which assumed you meant a physical keyboard of sufficient size.

If you're carrying around a big keyboard with your phone, you've officially exited mobile phone territory.

Mobile phone is hand-held and pocket sized by definition.

The medium is a touch screen

That's more like a GUI than a CLI. You have input boxes, buttons, sliders, gestures, scrolling, drag and drop, etc, and their different combinations. Many apps do almost the same thing, except giving you a different interface and a different combination of these steps. You listed some of those variations yourself.

How is that the same as the uniformity of the text only interface? That's far more different than differences in syntax, but still text. Two hyphens instead of one hyphen for a CLI flag is a really small difference.