Jonkman Microblog
  • Login
Show Navigation
  • Public

    • Public
    • Network
    • Groups
    • Popular
    • People

Conversation

Notices

  1. :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: (kaniini@pleroma.site)'s status on Thursday, 04-Jul-2019 08:40:28 EDT :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy:
    @grainloom

    a disturbing thing is that my utility, pkgconf, is basically in most modern unix systems at this point. it is also included in many commercial toolchains. toolchains benefit greatly from pkgconf as a tool. but guess how much pkgconf brings in? $0

    not a single commercial vendor who has included pkgconf in their product has ever bothered to pay for maintenance of pkgconf.

    the only time I have ever been paid to work on pkgconf is when I was working for a startup, who recognized that pkgconf was a key part of their build system and decided to allow me to use some of my hours to work on pkgconf and other Alpine toolchain issues. but that's indirectly. that's not a company saying "hey pkgconf is a key part of our product, here's $$$ to maintain it."

    if pkgconf maintenance were properly funded, that alone, would cover all of my expenses. instead us free software developers all have to set up patreons and stuff because the invention of docker ate all the systems development jobs.
    In conversation Thursday, 04-Jul-2019 08:40:28 EDT from pleroma.site permalink
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

Jonkman Microblog is a social network, courtesy of SOBAC Microcomputer Services. It runs on GNU social, version 1.2.0-beta5, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All Jonkman Microblog content and data are available under the Creative Commons Attribution 3.0 license.

Switch to desktop site layout.