1. 30
    Add an electron tag meta

This will probably get paired most with release, but provides a useful filter for people who can’t / won’t use software written using the framework.

  1.  

  2. 11

    I don’t think this would be an appropriate use of an electron tag nor is it a compelling reason to create one. The motivation for adding this tag should be more around tagging submissions related to developing software built on electron and less on release of that software. Are we getting enough (any?) articles of that nature to justify a tag?

    Do we currently, or going forth want to, encourage the pairing of the release tag with the existing tags for any other languages, frameworks, etc.? I don’t think those are overly relevant to a post about the release of some software. An exception might be if the post is an article about the release that also includes content on the technical challenges which were faced during development of the release. This might contain something of interest (or disinterest) to those who pay attention to the tag(s) for that particular technology and would want to block or seek out that content.

    1. 8

      I don’t think this would be an appropriate use of an electron tag nor is it a compelling reason to create one. The motivation for adding this tag should be more around tagging submissions related to developing software built on electron and less on release of that software. Are we getting enough (any?) articles of that nature to justify a tag?

      systemd and node.js are similarly polarizing technologies that are low bandwidth, but gained a tag primarily to filter.

      1. 4

        The systemd tag was added because:

        There’s been a lot of noise about systemd recently, and I would like to filter out that. I’m somewhat interested in linux in general, so I don’t think filtering on the linux tag would be a suitable work-around.

        Doing a “comments and stories” search for “systemd” gives about twice as many hits as searching for “netbsd”, which does have its own tag.

        So, it may be low bandwidth now, it wasn’t when it was added.

        https://lobste.rs/s/a2ccah/can_we_have_systemd_tag

        The nodejs tag is a bit more unclear, but the original proposal argues that posts on topic of nodejs are not necessarily well tagged as javascript.

        https://lobste.rs/s/j2bxnz/meta_nodejs_tag

        None of both arguments apply in this case. This proposal wants presentations and descriptions of applications marked as electron only to filter them out.

        Obviously, yes, most tags are here for filtering, but I don’t believe electron is good enough as a category to merit it’s introduction. It is low volume, and mostly currently a hot topic because of one post.

      2. 4

        Im with you on that. We got web app for the 1,000 ways to do stuff in browsers.

      3. 7

        I am voting for adding that tag. It will allow me to filter non-portable software from my reading list.

        1. 9

          By that argument, we’d have to add many, many tags. Starting with everything that is doesn’t port to Windows.

        2. 4

          Honestly I’m kinda tired of all the rancor over Electron. I use Electron apps and love some of them, but other than that have no skin in that particular game. I think a tag would be a great way for people like me to ignore the endless “Emacs!” “VI!” back and forth.

          1. 3

            Rather than using a dedicated electron tag (which means we’d need a per framework tag), why don’t we have a generic tag for things made with web app technologies in fat apps - a fatweb tag?

            The fatweb tag could cover anything made with fat webapp tech, including cordova/phonegap etc.

            1. 2

              The fatweb tag could cover anything made with fat webapp tech, including cordova/phonegap etc.

              Do those technology ever get posted and are they as controversial as electron is?