• 2 Posts
  • 93 Comments
Joined 3 years ago
cake
Cake day: June 18th, 2023

help-circle
  • A big hurdle with RCS was carrier adoption, at least in Asia.

    I wonder about two things:

    1. Would Graphene team’s implementation be usable on other devices that are less fortunate to be supported by the OS?
    2. Would this be a drop-in replacement or would Graphene team need to work with carriers so that their implementation actually work?

    On a tangential note, I would really like to read an in-depth analysis of how RCS had such a botched up implementation, which it has still to recover from almost a decade later.

    The adoption is nowhere close to what it should have been, and instead it is now more associated with spam than actual communication. The Wikipedia entry does cover a lot of aspects, but it doesn’t explain how it went wrong.




  • A serious answer:

    The “editor wars” are predominantly fought by people who work in IT (system admins, developers, etc.), which requires using the terminal frequently or is often the only tool at their disposal.

    Some folks also use specific editors because of their text editing capabilities. Vim’s modal editing is very intuitive and fast, while Emacs’ Org Mode feature set can be a sole reason to put up with Emacs.

    Tangential

    A case can be made that modern programming does not really require a terminal since IDEs meet its needs. But the debate becomes more subjective and less objective.

    I work in IT, use emacs configured with vim’s modal editing, even though my employer provides expensive IDE licenses for me to use.

    I shifted IDEs to Vim because the former were too slow to open some of the code. Later I shifted to Emacs, trading some of that speed for Org mode.

    Now, I treat Emacs as the sole software to interact with the computer, as much as I can.











  • That may be a good idea. However, people have had around 25 years of familiarity with all things centralised on the internet and the conveniences associated with it. If anything, we are doubling down on the centralised nature of the internet.

    It will take a great amount of time and effort to build a equivalently convenient decentralised alternatives, and to overcome the inertia to migrate to it.

    The latter I believe is only possible when something enormously drastic happens. We had a good number of drastic events happen in the last decade (Twitter poisoning, Meta privacy breaches, Reddit shenanigans), but none enough to convince people to move to alternatives.

    Another possibility is for regulations and/or governments to support the alternatives, but that may have unintended side effects of its own.


  • Call it the network effect, or the momentum of becoming a staple in the tech community, or whatever; GitHub is here to stay for a while, and the leaders in charge of it are well aware of this.

    GitHub has gained enough attention that it is almost impossible to ignore. Projects on GitHub tend to attract a level of engagement (code contributions, issue reports, and feedback) that other code forges do not enjoy.

    One unfortunate consequence of this, which I have experienced recently, is when recruiters ask for links to my past work or open-source contributions but refuse to accept links to relevant repositories on GitLab. The number of companies where this occurred was significant enough for me to set up mirror repositories on GitHub.

    Another frustrating but silly consequence was when I was questioned during one of the interviews why my activity graph on GitHub was empty: I had simply not enabled it.