1. 56

Free-text search for sqlite reveals nearly 1,000 entries. It tends to be cross-cutting topic, with stories ranging from web development, to systems, to mobile, etc and it might not always be in the title, so a tag would be useful here.

Just a handful of stories within the last two weeks:

There’s always been a lot of interest in sqlite and this seems to be picking up recently. Compare to topics like zig, swift, and kotlin which have a few hundred hits each, an sqlite tag seems to be warranted.

  1.  

  2. 30

    I’m slightly against. databases covers it. mysql or postgres and so on don’t appear to need one.

    The main thing is I haven’t seen anyone at all get annoyed at the amount of material being posted here about sqlite. The nominal main use for tags on lobsters is for filtering out submissions you don’t want to see.

    1. 4

      I am annoyed about all the SQLite, fwiw.

      1. 1

        Being against the tag is one thing (I don’t care personally) but why annoyed about SQLite? It’s an amazing body of code.

        1. 9

          I’m not against the tag, I’m for the tag. I’d like to filter it.

          I’m sure it’s an amazing body of code, but I don’t enjoy the articles talking about how amazing a body of code it is. People talk about how great SQLite is as if thinking SQLite great is a fringe viewpoint, which I find tedious, and the debates about to SQLite or not are frustrating to read.

          I’m sure other people like the articles and the discussions they spawn, and I don’t want to feel tempted to go be grumpy at them there. A tag would just save my having to grump internally.

        2. 1

          huh okay fair enough

        3. 4

          Sure, sqlite falls under the umbrella of databases, but I cannot see how can adding the tag interfere with anyone’s use case. As I am writing, this post has received 24 upvotes, which means having it would benefit at least 24 users.

          From my understanding, you only think this is unnecessary but not harmful, whereas others are finding it necessary. This is not really an argument against the proposal IMO.

          The nominal main use for tags on lobsters is for filtering out submissions you don’t want to see.

          Git is nominally a distributed VCS, but most people have no problem with a central repo. I really want to see the hit statistics of URLs like https://lobste.rs/t/databases. That’s the only way we can know how users are actually using the tag system.

          1. 4

            Right – tags have other uses than filtering submissions out, regardless of the original reason the tag feature was implemented. Not only can one browse stories with a certain tag at tag pages, one can also subscribe to a tag via RSS and search for tagged stories.

            From my understanding, you only think this is unnecessary but not harmful, whereas others are finding it necessary. This is not really an argument against the proposal IMO.

            In general, adding any new tag is harmful in some way, though the benefits may outweigh the harms. The harms of adding a new tag:

            • It makes it harder to find other tags on https://lobste.rs/tags.
              • This interferes slightly with all the use cases for tags listed above, as you must learn of the existence of a tag before you can use it.
              • It makes it harder to understand what stories are acceptable on Lobsters, as submitters see the instruction “If no tags clearly apply to the story you are submitting, chances are it does not belong here.”
            • It makes it harder to tag a new submission with other tags.
              • The new tag will appear in the list of options, distracting some users who are submitting stories for which the tag does not apply.
              • The new tag may replace the tag that was previously autocompleted after typing a partial string like “s”.
            1. 1

              I did quality this with the word “slightly”.

              Git is nominally a…

              I brought it up because “are people itching for a way to filter it out?” is the official criterion here.

          2. 10

            Why is the databases tag insufficient in your opinion?

            1. 1

              I find it to be too generic, similar to the programming tag. Looking at the last 2 weeks of stories, 6 out of 13 stories under databases where about sqlite. Giving sqlite its own specific tag might make it easier to find sqlite related posts and could potentially cut the posts in databases to half, making it easier to find non-sqlite related posts for those looking for them.

              1. 1

                Tags are for filtering out, not for finding stuff.

                1. 11

                  Tags are for both. That’s why you can subscribe to emails for specific tags.

                  1. 5

                    Tags are meant for filtering things out, but they surely can double as a way to filter for something you are interested in. Otherwise, why do we have helpful URLs like https://lobste.rs/t/databases?

                    1. 2

                      Tags also let you know what a story is about. If a story title is “I built a X” but it’s tagged “go” “sqlite” you know how they built it before you click. Without that, you might not care enough to click.

                      1. 1

                        The database posts I care about are related to sqlite. With a sqlite tag, I’d filter out databases and just keep sqlite, which fits your described use case. I’d love to see this tag.

                  2. 8

                    More examples (many outside the past two weeks):

                    And those are just the ones I could find in a few minutes that I’d have tagged with sqlite.

                    1. 2

                      I’m for it.

                      1. 2

                        Oh yes. SQLite runs everywhere, it’s more like a storage format than a DBMS that the apps connect to and we don’t see much stuff with other databases around embedded use cases.